Tags

, , , , , , , , , , , , , ,

COPY PENDING

– If you load with LOG NO and do not take an inline copy, LOAD places a table space in the COPY-pending status.
– The copy pending status will appear when image copies job fails while copying the data to Tape or DASD.
– A state in which, an Image Copy on a table needs to be taken
– In COPYPEND status, you cannot edit a table. Only you can run queries on that table

CHECK PENDING

– When a table is Loaded with ENFORCE NO option, then the table is left in CHECK PENDING status. It means that the LOAD utility did not perform constraint checking.
– The check pending status will appear when Referential Integrity(RI) violation between data in parent table with child table. During the program access, when RI violation encounters the database it immediately put in CHKP status
– while in Check pending status. you can edit or load table by giving ENFORCE NO option

 
Remove the Statuses

Copy Pending status
1. Run Repair Utility
//STEP01 EXEC DSNUPROC
REPAIR SET TABLESPACE dbname.tsname NOCOPYPEND

2. Run the Dummy image copy job and the Tablespace status changes from copy pending to RW
3. Execute following db2 command to bring the status of tablespace to RW
-START DATABASE(dbname) SPACE(tablespace-name) ACESS(FORCE)

Check Pending status
1. Run Repair Utility
//STEP01 EXEC DSNUPROC
REPAIR SET TABLESPACE dbname.tsname NOCHECKPEND

2. Run the Check data for those tablespace and the Tablespace status changes from CHKP to RW.
3. You can execute the following query (This command will restart the tablespace and reset all the pending states on the tablespace and the table will be back in RW (read write mode).
-START DATABASE(dbname) SPACE(tablespace-name) ACESS(FORCE)

Note: The Status RW (READ/WRITE) means that the database is ready to do database processing.

Advertisements