home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.seagate.com
/
2014.07.ftp.seagate.com.tar
/
ftp.seagate.com
/
pub
/
palindrome
/
technote
/
tn9301.asc
< prev
next >
Wrap
Text File
|
1995-03-21
|
2KB
|
54 lines
Tech Note #: 9301
Date: January 20, 1993
Subject: 2032 Errors
Keywords: File history database, 2032 error, TNARECOV.
Network Archivist Version: 2.0f
Symptom
A 2032 error occurs when an attempt is made to delete a record
that has already been deleted. This scenario is rare, but if for
some reason TNARECOV thinks a rule record and its corresponding
key should be deleted, it will delete the record and the key.
The key is never completely deleted however, so the next time
TNARECOV is run, the same action is attempted, thus generating a
2032 error. In such cases, the database will always fail to
verify and will generate a 2032 error after attempting to delete
a rule from the database. After asking for a tape from which to
restore history, an infinite loop results if the history on that
tape has the same corruption.
Cause
This situation is caused by TNARECOV version 2.0f reacting
incorrectly when TNARECOV attempts to delete a partially deleted
rule from the index.
Solution
Palindrome has developed RCV2032, a special TNARECOV
utility designed to repair this corruption. Use this utility by
tagging the appropriate volume and selecting "Verify File History
Database" in the operation menu. There are three important
points to remember when using this utility:
STEP 1:
The RCV2032 utility is NOT a replacement for TNARECOV. The
utility is intended to be executed ONCE to repair the problem.
Only the rules verification section of TNARECOV is included in
this version of TNARECOV, so it will execute quickly, but it will
not perform the other database verification procedures.
STEP 2:
When the RCV2032 utility is executed, a 2032 error will occur,
causing the utility to ask for a tape to restore the databases.
At this point, the 2032 error has been repaired, so escape (DON'T
RESTORE HISTORIES) and run the original TNARECOV and verify the
databases again. TNARECOV should then complete without errors.
STEP 3:
This utility is for 2032 errors that occur while running
TNARECOV/VERIFY. If TNA2TAPE aborts with a 2032 error, check to
see if TNARECOV will also abort. If it does, this utility may
fix the problem. If not, restore older histories from tape.
The RCV2032 utility is on the BBS as 2032FIX.ZIP, the password is
"RULES."