I think you have to go for REPAIR or CHECK DATA utitlity which depends upon the importance of data. ![]() I'm not sure, if the STOP DATABASE command can bring the tablspace back into normal state. If the tablespace is in CHKPND status it will not allow any DML issued against it. What the heck happened?!?Ĭan't you just issue "stop database" command before the image copy and restart them after you have finished the imagecopy?ĬHECK PENDING is a restricted state. Inside every older man is a young boy asking this question. Is there a way to continue to use the code provided above and still have the utility continue to the next tablespace without terminating? In a test database environment there could be many tablespaces with this status with no way of knowing which tablespace is in check pending status without displaying each one before executing the image copy utility! The manual states that the only resolution is to fix the table with a check pending status and rerun the utility. The problem with this way of creating image copies is that if one tablespace has a check pending status against it, it fails with the following messages:ĭSNU321I -DB2P DSNUGDTC - CHECK PENDING ON TABLESPACE FDBMD.FTSPRSS PROHIBITS PROCESSINGįrom this point on no other tablespaces are backed up as the utility terminates with a return code 8. TEMPLATE PCSYTMPL DSN 'PC.SY.BKDISK.IC.&TS.(+1)'ĬOPY LIST PCSYLIST COPYDDN PCSYTMPL FULL NO LISTDEF PCSYLIST INCLUDE TABLESPACE FDBEL.* We have a production backup job that uses a LISTDEF parm to include all tablespaces in a database that need to have an image copy created. Posted: Fri 11:12 am Post subject: image copy failing on check pending status ![]() Image copy failing on check pending status ![]() Profile Log in to check your private messages Log in :: View topic - image copy failing on check pending status
0 Comments
Leave a Reply. |