A fix is available
APAR status
Closed as program error.
Error description
DB2 Object Comparison Tool for z/OS issues message ADB7163W for the LOB of the dependent table which is misleading and confusing when the only difference is DSSIZE
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Object Comparison Tool for * * z/OS who include tables with LOB columns * * and LOB objects in the Compare process. * **************************************************************** * PROBLEM DESCRIPTION: When comparing tables with LOB columns * * that use implicit LOB objects, a * * misleading warning message ADB7162W / * * msgadb7162W or ADB7163W / msgadb7163w * * is displayed when the source version * * file is generated from the DDL file. * * * * An example of the warning message: * * * * ADB7163W * * The number of auxiliary tables * * associated with the source * * table is not consistent with the * * number of LOB columns in the * * source table and with the number * * of partitions in the table space. * * Implicit LOB objects will be used * * if re-created. Ensure that one * * auxiliary table exists for each LOB * * column in each partition after the * * changes are applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** When comparing tables with LOB columns which use implicit LOB objects, a misleading warning message ADB7162W / msgadb7162w or ADB7163W / msgadb7163w is displayed when the source version file is generated from the DDL file. An example of the warning message: ADB7163W The number of auxiliary tables associated with the source table is not consistent with the number of LOB columns in the source table and with the number of partitions in the table space. Implicit LOB objects will be used if re-created. Ensure that one auxiliary table exists for each LOB column in each partition after the changes are applied.
Problem conclusion
The problem has been fixed with ADB7162W and ADB7163W updated: ADB7162W The number of auxiliary tables associated with the source table might not be consistent with the number of LOB columns in the source table. Implicit LOB objects are used when auxiliary tables are re-created. After changes are applied, ensure that one auxiliary table exists for each LOB column. Explanation: For tables that contain LOB columns, DB2 requires that LOB table spaces and auxiliary tables be created to hold the LOB data. When the base table is non-partitioned, DB2 requires one LOB table space and one auxiliary table be created for each LOB column. Object Comparison Tool checks whether the LOB objects definitions on the source agree with DB2 rules. This message is displayed when an inconsistency is found. Object Comparison Tool will re-create the LOB objects implicitly if the table is re-created. When the source comes from DDL file and implicit LOB objects are used, the version file generated from the DDL file might not contain enough information for Object Compare to determine the correctness of the LOB objects definitions. This message informs the user to check and ensure the correctness of the source DDL file. System action: Processing continues. User response: After processing completes, assess whether auxiliary table definitions are missing or if implicit LOB objects have been created. If table definitions are missing, fix the problem and try again. ADB7163W The number of auxiliary tables associated with the source table might not be consistent with the number of LOB columns in the source table and with the number of partitions in the table space. Implicit LOB objects are used when auxiliary tables are re-created. After changes are applied, ensure that one auxiliary table exists for each LOB column in each partition. Explanation: For tables that contain LOB columns, DB2 requires that LOB table spaces and auxiliary tables be created to hold the LOB data. When the base table is partitioned, DB2 requires one LOB table space and one auxiliary table be created for each LOB column in each partition. Object Comparison Tool checks whether the LOB objects definitions on the source agree with DB2 rules. This message is displayed when an inconsistency is found. Object Comparison Tool will re-create the LOB objects implicitly if the table is re-created. When the source comes from DDL file and implicit LOB objects are used, the version file generated from the DDL file might not contain enough information for Object Compare to determine the correctness of the LOB objects definitions. This message informs the user to check and ensure the correctness of the source DDL file. System action: Processing continues. User response: After processing completes, assess whether auxiliary table definitions are missing or if implicit LOB objects have been created. If table definitions are missing, fix the problem and try again.
Temporary fix
Comments
APAR Information
APAR number
PM91327
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
A20
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-06-18
Closed date
2013-09-26
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADB7000
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.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 October 2013