Restored Databases needing re-org?
This for DB2 running on OS390.....
During a recent disaster recovery test, we encountered several ‘DSNT500I' resource unavailable messages while doing inserts to certain TABLESPACES. The Reason Code was 00C200C1 and the type was 00000302. This was followed by a DSNT004I saying the resource had been stopped with the type pointing to TABLESPACE(00000200).
We had the ZPARM set for RECOVERYSITE and used tapes created with RECOVERYDDN parm for offsite recovery. To recover the databases we used RECOVER utility with the TOCOPY option, rebuilding the indexes with the REBUILD utility. All the RECOVER and REBUILD jobs ran successfully
To get past the error we had to re-org the effected tablespace and then we proceeded with our testing. Is this a normal situation during a disaster recovery? We have two theories for the cause of the resource unavailability. One is that we are out of space on the volumes, but, our storage pools are set up to span volumes and there seems to be space available on some of the volumes in the storage pool. The other is that their might be some page corruption (type 00000302), but, we recovered several databases and this only happened to a select few. We have recovered all of these databases, in our Production Environment and did not run into this problem. Any help or pointers would be greatly appreciated.
Thanks in advance.
Chris Prosperi
Chicago Transit Authority
1.312.664.7200 x4769
This for DB2 running on OS390.....
During a recent disaster recovery test, we encountered several ‘DSNT500I' resource unavailable messages while doing inserts to certain TABLESPACES. The Reason Code was 00C200C1 and the type was 00000302. This was followed by a DSNT004I saying the resource had been stopped with the type pointing to TABLESPACE(00000200).
We had the ZPARM set for RECOVERYSITE and used tapes created with RECOVERYDDN parm for offsite recovery. To recover the databases we used RECOVER utility with the TOCOPY option, rebuilding the indexes with the REBUILD utility. All the RECOVER and REBUILD jobs ran successfully
To get past the error we had to re-org the effected tablespace and then we proceeded with our testing. Is this a normal situation during a disaster recovery? We have two theories for the cause of the resource unavailability. One is that we are out of space on the volumes, but, our storage pools are set up to span volumes and there seems to be space available on some of the volumes in the storage pool. The other is that their might be some page corruption (type 00000302), but, we recovered several databases and this only happened to a select few. We have recovered all of these databases, in our Production Environment and did not run into this problem. Any help or pointers would be greatly appreciated.
Thanks in advance.
Chris Prosperi
Chicago Transit Authority
1.312.664.7200 x4769