DB2 - Problem description
Problem IT16334 | Status: Closed |
IBM SPECTRUM PROTECT SNAPSHOT OFFLOAD FUNCTION MAY RETURN ERROR MESSAGE FMM6283E IN COMBINATION WITH SQL0104N | |
product: | |
FLSHCPY DB2 AGE / 5608AC6DB / 41A - DB2 | |
Problem description: | |
If profile variable DB2_OPTIONS is set in the OFFLOAD section of the IBM Spectrum Protect Snapshot profile, IBM Spectrum Protect Snapshot for UNIX may return the following error when sending a backup to an IBM Snapshot Protect server : FMM6283E offloaded tape backup unsuccessful. ... SQL0104N An unexpected token "DEDUP_DEVICE" was found following "". Expected tokens may include: "INCLUDE". SQLSTATE=42601 Under certain circumstances, parameters in the DB2 backup command used internally to offload a backup to an IBM Snapshot Protect server are passed to DB2 in an incorrect order if "DB2_OPTIONS" is set. This was seen specifically if the OFFLOAD sections contains " DB2_OPTIONS DEDUP_DEVICE" and any of "NUM_BUFFERS", "BUFFER_SIZE", and "PARALLELISM". If "DB2_OPTIONS" is not used the backup to an IBM Snapshot Protect server works. Also, specifying "DB2_OPTIONS DEDUP_DEVICE" while leaving buffers and parallelism to be determined automatically works. Customer/L2 Diagnostics: If parameter DB2_OPTIONS is used in the OFFLOAD section of the IBM Spectrum Protect Snapshot profile the combination of the following two messages indicate that this defect was hit: FMM6283E offloaded tape backup unsuccessful. - and - SQL0104N An unexpected token "" was found following "". Expected tokens may include: "". SQLSTATE=42601 IBM Spectrum Protect Versions Affected: All IBM Spectrum Protect Snapshot for UNIX v4.1.x Initial Impact: Low Additional Keywords: IBM Spectrum Protect Snapshot DB2 DEDUP_DEVICE SQL0104N BUFFER NUM_BUFFERS BUFFER_SIZE PARALLELISM offload DB2_OPTIONS | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of IBM Spectrum Protect Snapshot when running * * offloaded backups of DB2 * **************************************************************** * PROBLEM DESCRIPTION: * * If you use DB2_OPTIONS in combination with NUM_BUFFERS, * * BUFFER_SIZE, or PARALLELISM, errors that relate to incorrect * * order of options are sent for the DB2 backup operation. * **************************************************************** * RECOMMENDATION: * * Add a note to the documentation: * * * * If you use DB2_OPTIONS in combination with NUM_BUFFERS, * * BUFFER_SIZE, or PARALLELISM, errors that relate to incorrect * * order of options are sent for the DB2 backup operation. * * Resolve the errors by avoiding using the NUM_BUFFERS, * * BUFFER_SIZE, and PARALLELISM parameters with the * * DEDUP_DEVICE option in the DB2_OPTIONS string. If this * * cannot be avoided then specify the corresponding DB2 options * * WITHnum-buffersBUFFERS, BUFFERbuffer-size, and PARALLELISMn * * with the DB2_OPTIONS parameter and the DEDUP_DEVICE option. * * Ensure to use the correct order of options that are defined * * in the DB2 documentation for the DB2 BACKUP command. * **************************************************************** | |
Local Fix: | |
The following work-arounds are available: - In the OFFLOAD section of the IBM Spectrum Protect Snapshot profile, do not specify any parameter of "NUM_BUFFERS", "BUFFER_SIZE", and "PARALLELISM" if "DB2_OPTIONS DEDUP_DEVICE" is specified. - If specific settings are required for these parameters use the corresponding parameters of the DB2 backup command and add them in the required order to "DB2_OPTIONS": "NUM_BUFFERS" is translated to "WITH ... BUFFERS"; "BUFFER_SIZE" is translated to "BUFFER"; "PARALLELISM" is translated to "PARALLELISM". For example if both ?DEDUP_DEVICE? and ?BUFFER? are needed, add the following line in the OFFLOAD section of the profile: DB2_OPTIONS "DEDUP_DEVICE BUFFER 16348" Please note that the value of DB2_OPTIONS must be quoted if it contains blanks. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.07.2016 26.09.2016 26.09.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |