A fix is available
APAR status
Closed as program error.
Error description
The DB2 Administration Tool for z/OS' Catalog Copy function builds JCL which does not honor the 'Catalog Copy Method' field 'L=LOAD from Cursor' option on panel ADB2CCJ 'Create Catalog Copy and Bind Batch Jobs' for all of the tablespaces i.e. some will use the INCURSOR method some will use an UNLOAD/LOAD method instead.
Local fix
Manually correct the JCL.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Administration Tool for * * z/OS who use the Catalog Copy function. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS * * Catalog Copy function builds JCL which * * does not honor the 'Catalog Copy * * Method' field 'L=LOAD from Cursor' * * option on panel ADB2CCJ 'Create * * Catalog Copy and Bind Batch Jobs' * * for all of the tablespaces. For * * tables that do not contain LOB * * columns, Catalog Copy will use the * * LOAD INCURSOR method. For tables * * that contain LOB columns Catalog * * Copy will use an UNLOAD/LOAD * * method. For table spaces that * * have LOB columns, using the * * UNLOAD/LOAD method may not work * * when the maximum number of PDSE * * members is less than the number * * of rows which contain LOB columns. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 Administration Tool for z/OS catalog copy should use the UNLOAD/LOAD method on catalog tables which contain LOB columns even when the customer chooses 'L=LOAD from Cursor' as the Catalog Copy method on panel ADB2CCJ 'Create Catalog Copy and Bind Batch Jobs'. Catalog Copy should UNLOAD LOB columns from DB2 catalog tables (except SYSIBM.SYSJAVA) to VBS data set when using DB2 10 New Function Mode (NFM). SYSIBM.SYSJAVA contains more than one table, and Catalog Copy unloads data at the tablespace level, which means unloading all the tables in SYSIBM.SYSJAVA, as a result the LOB column will not be at the end of the unload record, which will cause the unload to VBS PS data set to fail with the following error: DSNU1233I #SSID- 261 DSNUULVA - DATA IS TOO LONG FOR FIELD JAR_DATA, TABLE SYSIBM.SYSJAROBJECTS DSNU1219I #SSID- THE NUMBER OF RECORDS IN ERROR REACHED THE LIMIT 1
Problem conclusion
The initially reported symptom still occurs, which means Catalog Copy still chooses UNLOAD/LOAD method to copy data from the DB2 system catalog tables to the User catalog tables, and during the UNLOAD phase, if DB2 Administration Tool is running on DB2 10 New Function Mode (NFM), Catalog Copy takes advantage of DB2 10 NFM to UNLOAD LOB data (except LOB columns in SYSIBM.SYSJAVA) to a VBS dataset, then the original PDSE data set member limitation goes away. The ADBHCCJ 'Create Catalog Copy and Bind Batch Jobs' help panel and the DB2 Administration Tool for z/OS User's Guide and Reference, Version 10, Release 1 (SC19-3033-05) and Version 10, Release 2 (SC19-3774-00) have been updated to describe why Catalog Copy uses UNLOAD/LOAD method for system tables that have LOB columns. ADBHCCJ help panel before the change: U - Produce the catalog copy by using the DB2 UNLOAD utility as one set of steps and the LOAD utility as another set. Note: Templates with default data set names are used for output and work data sets. Note: HPU is unavailable as an unload method. ADBHCCJ help panel after the change: U - Produce the catalog copy by using the DB2 UNLOAD utility as one set of steps and the LOAD utility as another set. Note: Templates with default data set names are used for output and work data sets. Note: HPU is unavailable as an unload method. Note: For DB2 V10 NFM, Catalog Copy will UNLOAD LOB columns to VBS data sets for performance issue. DB2 Administration Tool for z/OS, Version 10, Release 1, (SC19-3033-05) and Version 10, Release 2 (SC19-3774-00) User's Guide and Reference before the change: 5. Specify the name of an existing PDS where the generated jobs are to be stored. For type C (copies of a local DB2 system catalog), also specify: The database and the storage group name to be used for the table space that will contain the like tables of the DB2 catalog tables. The name of the table space created to contain the like tables is the same as the qualifier of the copy. The method to used to copy the DB2 catalog to the like tables. The default is LOAD from cursor method. The other method, UNLOAD/LOAD, allows you to unload into data sets as one process and to load as a second process. For the UNLOAD/LOAD method, the CPYRUNxx job will use TEMPLATE statements to define output and work data sets. Modify those TEMPLATE statements as necessary. (This function does not use any user-specified templates.) Recommendation: Use the LOAD from cursor method if the catalog data is not needed outside of the process, for example, for the movement or modification of data. The LOAD from cursor method reduces the I/O load of the entire process and requires no work data sets. DB2 Administration Tool for z/OS, Version 10, Release 1, (SC19-3033-05) and Version 10, Release 2 (SC19-3774-00) User's Guide and Reference after the change: 5. Specify the name of an existing PDS where the generated jobs are to be stored. For type C (copies of a local DB2 system catalog), also specify: The database and the storage group name to be used for the table space that will contain the like tables of the DB2 catalog tables. The name of the table space created to contain the like tables is the same as the qualifier of the copy. The method to be used to copy the DB2 catalog to the like tables The default is the LOAD from cursor method. Note: When you choose this option, the DB2 Administration Tool still uses the UNLOAD/LOAD method on catalog tables that contain LOB columns. This is because when a catalog table contains LOB columns, the catalog table also contains columns that are defined as GENERATED ALWAYS. DB2 does not allow GENERATED ALWAYS columns in the specification list when the LOAD from cursor method is used. The other method, UNLOAD/LOAD, allows you to unload into data sets as one process and to load as a second process. For the UNLOAD/LOAD method, the CPYRUNxx job will use TEMPLATE statements to define output and work data sets. Modify those TEMPLATE statements as necessary. (This function does not use any user-specified templates.) Recommendation: Use the LOAD from cursor method if the catalog data is not needed outside of the process, for example, for the movement or modification of data. The LOAD from cursor method reduces the I/O load of the entire process and requires no work data sets.
Temporary fix
Comments
APAR Information
APAR number
PM68245
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-05
Closed date
2012-10-24
Last modified date
2012-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK82915 UK82916
Modules/Macros
ADBHCCJ
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
02 November 2012