A fix is available
APAR status
Closed as program error.
Error description
WHEN COMPARING DDL FILE WITH A DB2 CATALOG, USING OPTION 4 - TARGET IS FROM THE DB2 CATALOG AND THE OBJECTS ARE AUTOMATICALLY SELECTED BASED ON THE SELECTED SOURCE OBJECTS AS TARGET, WE GET FOLLOWING ERROR AT COMPARE TIME : COMPARE TABLE SOURCE(S01D.DOCDATA_TBL) AND TARGET(S01D.DOCDATA_TBL) COLUMN ROW_ID_DOCDATA ROWID GENERATED BY DEFAULT REQUIRES UNIQUE INDEX AUXILIARY TABLE S01D.DOCDAT$1_AUX PROCESSED GOCC024E - UNEXPECTED CATALOG ROW ON TARGET FILE. EXPECTED:AR FOUND:TB ROWTYPES FROM SOURCE FILE : TB TS CO CO CO CO CO CO CO TC KU TB AR ROWTYPES FROM TARGET FILE : TB TS CO CO CO CO CO CO CO TC KU TB TB TS TS AR AR TA TA TA TA TA TA GOCC024E - UNEXPECTED CATALOG ROW ON TARGET FILE. GOCC002E - SEVERE ERROR. COMPARE TERMINATES
Local fix
No Work Around
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 Administration Tool * * or DB2 Object Comparison Tool * * for z/OS who use Change * * Management or the GEN/DDL * * commands to generate DDL, a * * version record for a LOB table * * space, or an auxiliary table that * * was defined on DB2 v7 or earlier. * **************************************************************** * PROBLEM DESCRIPTION: During change management the object * * compare program issues an error message * * about an unexpected catalog row on * * target file. * * * * GOCC024E - UNEXPECTED CATALOG ROW ON * * TARGET FILE. * * EXPECTED:AR FOUND:TB * * ROWTYPES FROM SOURCE FILE : * * TB TS CO CO CO CO CO CO CO * * TC KU TB AR * * ROWTYPES FROM TARGET FILE : * * TB TS CO CO CO CO CO CO CO * * TC KU TB TB TS TS AR AR TA * * TA TA TA TA TA * * GOCC024E - UNEXPECTED CATALOG ROW ON * * TARGET FILE. * * * * GOCC002E - SEVERE ERROR. * * COMPARE TERMINATES * **************************************************************** * RECOMMENDATION: Apply The PTF. * **************************************************************** The problem involves generating a LOB table space or auxiliary table that was created on DB2 v7. This problem can occur on DB2 v7, or a DB2 sub-system that was converted from DB2 v7 to DB2 v8 new function mode or later.
Problem conclusion
The problem has been resolved.
Temporary fix
Comments
APAR Information
APAR number
PK89537
Reported component name
DB2 OBJECT COMP
Reported component ID
5697G6400
Reported release
720
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-06-22
Closed date
2010-03-18
Last modified date
2010-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADB2RE ADB2REC ADB2REE ADB2REM ADB2REU ADB2REZ
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
R720 PSY UK55333
UP10/03/24 P F003
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"720"}]
Document Information
Modified date:
31 March 2021