The LOAD utility places a tablespace in DB2 CHECK PENDING (CHKP) status if its referential integrity is in doubt or its check constraints are violated. DB2 enforces constraints when:
//STEP01 EXEC DSNUPROC
REPAIR SET TABLESPACE dbname.tsname NOCHECKPEND
Note: The Status RW (READ/WRITE) means that the database is ready to do database processing.
//STEPO1 EXEC PGM=DSNUTILB,REGIONM, // PARM='DB2X,MIGRDAN, ' //STEPLIB DD DSN=XXX.XXXXX.SDSNLOAD,DISP=SHR //SYSIN DD * REPAIR SET TABLESPACE XXXXX.XXXXX NOCOPYPEND REPAIR SET TABLESPACE XXXXX.XXXXX NORCVRPEND REPAIR SET INDEX XXXXX.XXXXX NOCOPYPEND REPAIR SET INDEX XXXXX.XXXXX NORCVRPEND REPAIR SET INDEX XXXXX.XXXXX NORBDPEND /* //SYSPRINT DD SYSOUT=* //UTPRINT DD SYSOUT=*
The CHECK DATA utility checks tablespaces for violations of referential and table check constraints and reports information about violations that it detects. CHECK DATA checks for consistency between a base table space and the corresponding LOB or XML tablespaces. CHECK DATA does not check LOB tablespaces. The utility does not check informational referential constraints.
Run CHECK DATA after a conditional restart or a point-in-time recovery on all tablespaces where parent and dependent tables might not be synchronized or where base tables and auxiliary tables might not be synchronized.
Restriction: Do not run CHECK DATA on encrypted data. Because CHECK DATA does not decrypt the data, the utility might produce unpredictable results.
The CHECK INDEX online utility tests whether indexes are consistent with the data that they index, and issues warning messages when it finds an inconsistency.
Run the CHECK INDEX utility after a conditional restart or a point-in-time recovery on all tablespaces whose indexes might not be consistent with the data. Also run CHECK INDEX before running CHECK DATA, especially if you specify DELETE YES. Running CHECK INDEX before CHECK DATA ensures that the indexes that CHECK DATA uses are valid. When checking an auxiliary table index, CHECK INDEX verifies that each LOB is represented by an index entry and that an index entry exists for every LOB.
Important: Inaccurate statistics for tables, tablespaces, or indexes can result in a sort failure during CHECK INDEX.
Optimize Outer Join queries is a powerful tool for retrieving data from multiple tables. However,…
OUTER JOIN Queries are a valuable tool in SQL, allowing you to retrieve data from…
Mastering impediments is crucial to the Scrum Master's role in fostering a high-performing Scrum Team.…
A Sprint Goal is a short, clear, and motivating target the Scrum Team aims to…
Context switching refers to changing focus or shifting attention from one task or activity to…
Embracing change is never easy, especially when it involves a shift in work methodology. Motivate…