Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OS390 DB2 - Reorg after Restore, is it needed???....

Status
Not open for further replies.

ctaman

MIS
Feb 1, 2002
5
US
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
 
Dear Sir,
Actually you don't have to run reorg after you have done your recovery especially
if recover using TOCOPY. Because TOCOPY is the point where your tablespace is in a
good state.
REORG is run just to cleanup your tablespace like reorder your data, pre-allocate
again the free space and resize your tablespace if it is already almost full.
Normally REORG is done to improve the performance of the tablespace so that access
to the database is improved.
If you having mass insertion, please calculate first whether the tablespace size
is enough to hold the data. Normally by providing bigger secondary size will help
minimise the insufficient space problem for OS390.

Brgds from
CHOT
DBA for Malaysia Airlines.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top