A fix is available
APAR status
Closed as program error.
Error description
After cloning a DB2 subsystem, the CATMAINT UPDATE SWITCH SCHEMA was run to switch some userids. During this process, fields in the OBD were overlaid, causing multiple abends later when trying to INSERT or run RUNSTATS. Other actions could also causes these same abends. Some of the abends that could occur are: ABENDS0C4 00000010 PIC10 AT DSNSLD1 DSNSVBK OFFSET0DB0 ABENDS0C4 00000038 PIC38 AT DSNIDM DSNIBABR OFFSET01E2 ABENDS0C4 00000004 PIC04 AT DSNIDM DSNIMOFT OFFSET037C ABENDS0C4 00000038 PIC38 AT DSNBBM DSNV1RTR OFFSET03B6 ABENDS0C4 00000011 PIC11 AT DSNIDM DSNIBNRF OFFSET2C38 Additional symptoms: ABENDS0C4 00000010 PIC10 AT DSNSLD1 DSNSFBK OFFSET15F6 ABEND04E RC00E20005 AT DSNICMT2 DSNSVBK OFFSET0994 ABENDS0C4 00000004 PIC04 DSNSLD1 DSNSVBK OFFSET19B6 ABEND04E RC00C90101 DSNISMRS ERQUAL5001 ABEND04E RC00C90101 DSNICLOS ERQUAL5007 ABEND04E RC00E40600 DSNUT910 DSNUEXDB OFFSET7DF2 ABENDS0C4 00000004 PIC04 AT DSNUTILA DSNUGXMA OFFSET03C0 DB2OVRLAY/K
Local fix
You can run REPAIR DBD REBUILD to rebuild the corrupt DBD. To identify all affected DBDs, run this select: SELECT DISTINCT DBNAME FROM SYSIBM.SYSTABLES WHERE CREATOR='BBBBBB' assuming the following was ran prior: CATMAINT UPDATE SCHEMA SWITCH (AAAAAA,BBBBBB)
Problem summary
**************************************************************** * USERS AFFECTED: All V9 DB2 Users using CATMAINT UPDATE * * SCHEMA SWITCH utility. * **************************************************************** * PROBLEM DESCRIPTION: After running CATMAINT UPDATE SCHEMA * * SWITCH utility, some objects' DBD * * were corrupted causing various * * abends when using the object. Some of * * the abends are: * * * * ABEND0C4-10 AT DSNSLD1.DSNSVBK +0DB0 * * ABEND0C4-38 AT DSNIDM.DSNIBABR +01E2 * * ABEND0C4-04 AT DSNIDM.DSNIMOFT +037C * * ABEND0C4-38 DSNBBM.DSNV1RTR +03B6 * * ABEND0C4-11 DSNIDM.DSNIBNRF +2C38 * **************************************************************** * RECOMMENDATION: * **************************************************************** After running CATMAINT UPDATE SCHEMA SWITCH utility, some objects' DBD were corrupted causing various abends. Some of the abends are: ABEND0C4-10 AT DSNSLD1.DSNSVBK +0DB0 ABEND0C4-38 AT DSNIDM.DSNIBABR +01E2 ABEND0C4-04 AT DSNIDM.DSNIMOFT +037C ABEND0C4-38 DSNBBM.DSNV1RTR +03B6 ABEND0C4-11 DSNIDM.DSNIBNRF +2C38 The corruption of the DBD was due to incorrect usage of interface within internal DB2 modules.
Problem conclusion
DB2 code has been fixed to make sure the usage of the interface within internal DB2 modules is correct. Application of this PTF does not correct the corrupted DBDs due to the error, please refer to the ++HOLD for the action you need to take. Here is a copy of the ++HOLD: This APAR/PTF fixes an error in CATMAINT UPDATE SCHEMA SWITCH that caused corruption in DBDs. Application of the PTF will not fix the DBDs that were corrupted prior to this PTF. You can run REPAIR DBD utility to correct the corrupted DBDs. If REPAIR DBD TEST/DIAGNOSE reports error message DSNU920I on field OBDRULN, OBDRUDCO, and OBDRUNUM like the following, then REPAIR DBD REBUILD can be run to fix the problem. DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000146' OBDRULN DSNU904I DSNUEDRT - EXISTING VALUE X'0021' DSNU905I DSNUEDRT - REBUILT VALUE X'001D' DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'0000014C' OBDRUDCO DSNU904I DSNUEDRT - EXISTING VALUE X'001C' DSNU905I DSNUEDRT - REBUILT VALUE X'0018' DSNU920I DSNUEDRT - OBDS DIFFER AT OFFSET X'00000150' OBDRUNUM DSNU904I DSNUEDRT - EXISTING VALUE X'0002' DSNU905I DSNUEDRT - REBUILT VALUE X'0001' If you have run the following CATMAINT utility previously: CATMAINT UPDATE SCHEMA SWITCH (AAAAAA,BBBBBB) then here is the query you can use to locate the database name of the DBDs that are possibly affected: SELECT DISTINCT DBNAME FROM SYSIBM.SYSTABLES WHERE CREATOR='BBBBBB'
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK90557
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-03
Closed date
2009-08-31
Last modified date
2011-02-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK49713
Modules/Macros
DSNUESCM
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
R910 PSY UK49713
UP09/09/15 P F909
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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
17 February 2011