Product

Platform

Operating system

Error

Symptoms

Cause

They would like us to help verify that all jobs have been correctly archived before purging while they re-build their confidence in the archiver. If this customer calls in asking us to check their archives, please run a rawtape scan to ensure that the savesets are physically on the tape, corresponding to what is in the database.

Solution

1. Run the below script to find out all the jobs that have archived after a specified date, whatever date the customer want to check.

login into SQL, at dos prompt> type <sqlplus prinergy/araxi>

at SQL prompt>

SQL> set linesize 2000

SQL> alter session set nls_date_format = 'YYYY-Mon-DD';

-- this set the date format for display

SQL> select JCKDNAME, LOGICALARCHIVECREATEDTM, PHYSICALARCHIVEMEDMID, PHYSICALARCHIVESTARTLOC from dbcs_archive where LOGICALARCHIVECREATEDTM > 'YYYY-Mon-DD';

-- specify the date that you want to check for archive in the above query.

- Save the result to a text file.

2. Locate the tape(s) that has/have been used for archive.

Mark down the Physicalarchivemedmid column at the above query result. This is the archivemedmid for the tape that is used to archive.

3. At SQL> select * from dbcs_archivemedium;

--- this will show all the mediums, look at the archivemedmid column, locate the value that match the value of the PhysicalArchiveMedmId from step 2.

-- Or you can do a SQL> select * from dbcs_archivemedium where archivemedmid = 'the value of the physicalarchivemedmid at step 2>';

- Mark down the archivemedmname for the tape(s) to use for the next step.

4. After you have located the medium(s) that used for archive. We need to use rawtape to scan the tape(s).

- insert the tape into the drive

- at dos prompt > type <rawtape \\.\tapex -vam > xxx.txt>

- this will read the tape and list the medium header and archive header to a text file.

5. Repeat step 4 for the mediums that have been archived from the specified date.

6. Once we have the rawtape results of all the tapes and the database result, we have to compare the jobname, physicalstartblockloc in the database with the Abs Block Num (L) value listed in rawtape result for the job. Make sure the block location values on both are the same.

Permanent fix:

See also

Keywords

archiver, archiver FAQs

Technical contact(s)

Amy Chan

Submitted by

Amy Chan

Date submitted

Feb 20, 2002