Abstract:
Both DB2 9 for z/OS potential data corruption and DB2 crash after using the CATMAINT UPDATE SCHEMA SWITCH utility, which is new in DB2 9.
Description:
After running the CATMAINT UPDATE SCHEMA SWITCH utility, object's DBDs were corrupted causing various overlay type ABENDs when accessing the row. This problem only affects databases that contain tables that have columns with user defined default values. Some of the potential ABENDs are:
ABENDS0C4 00000010 PIC10 AT DSNSLD1 DSNSVBK
ABENDS0C4 00000038 PIC38 AT DSNIDM DSNIBABR
ABENDS0C4 00000004 PIC04 AT DSNIDM DSNIMOFT
ABENDS0C4 00000038 PIC38 AT DSNBBM DSNV1RTR
ABENDS0C4 00000011 PIC11 AT DSNIDM DSNIBNRF
ABENDS0C4 00000010 PIC10 AT DSNSLD1 DSNSFBK
ABEND04E RC00E20005 AT DSNICMT2 DSNSVBK
ABENDS0C4 00000004 PIC04 DSNSLD1 DSNSVBK
ABEND04E RC00C90101 DSNISMRS ERQUAL5001
ABEND04E RC00C90101 DSNICLOS ERQUAL5007
ABEND04E RC00E40600 DSNUT910 DSNUEXDB
During CATMAINT UPDATE SWITCH SCHEMA execution, some OBDU fields (the OBD user defined default section) in the DBD were corrupted.
Recommended Actions:
As a preventative action, install the PTF for PK90557.
The REPAIR DBD utility with the TEST or DIAGNOSE options can be used to determine whether this inconsistency exists, and then REPAIR DBD REBUILD can be used to correct the DBD issue.
As per APAR PK90557/UK49713, the following SQL can be issued to find all the databases which may have corrupted OBDU fields:
If you have run the following CATMAINT UPDATE utility statement previously:
CATMAINT UPDATE SCHEMA SWITCH (AAAAAA,BBBBBB)then the below query can be used to locate the database name of the DBDs that are possibly affected:
SELECT DISTINCT DBNAME FROM SYSIBM.SYSTABLES WHEREA REPAIR DBD REBUILD for each DBD identified with the corruption is then required to correct the problem.
CREATOR='BBBBBB'
If you want to have en overview of all past Red Alerts, then take a look over here. You can also subscribe on the same page so you'll be notified by mail of any future Red Alert.
No comments:
Post a Comment