This procedure is used to archive a clean log which was not archived previously when it was switched (Refer to the procedure Switching a Clean Log). It archives the clean log to tape and optionally removes it from disk.
Caution
tlmenu does not support archiving of multiple clean logs. The clean log archive procedure only dumps one clean log per tape. A separate tape must be used to archive each log file.
y
to continue.On a FailSafe primary database, you are asked:
Do you want to run the archive on the Secondary (y/n/q)? :
Answer y
to archive the clean log on the secondary
and or n
to archive it on the primary.
A list of clean logs currently in the database's clean log sub-directory is displayed. Enter the name of the clean log you want to archive.
Note: Clean log
names are case sensitive. For example, CLOG
must be entered as upper-case.
You are then prompted:
Mount write enabled tape on LOCAL tape unit n for Clean Log archive. Are you ready to continue (y/n/q):
Note: If a secondary archive in a FailSafe configuration has been selected, the second message reads:
Mount write enabled tape on REMOTE tape unit n for Clean Log archive.
The tape should then be mounted on the secondary machine.
Ensure that the tape is loaded and the tape device is on-line. Then enter
y
to
archive the clean log to tape and verify the archived log.
Note: Any error condition occurring during the archiving or verification of the clean log will display the message:
Warning : Clean Log archive / verify failed. Do you want to retry (y/n/q)?:
Enter y
to retry the archive/verify procedure or n
to return to the Routine Maintenance menu.
Once the archive tape has been verified you are prompted to remove the clean log from disk:
Delete Clean Log clog_name from Disk (y/n/q) ? :
Enter y
to remove the now archived clean log from disk. You are then returned to the
Routine Maintenance menu.
Note: If you are using Reality Disaster Recovery to backup your database, the clean log will not be deleted until it has been copied to the slave system and restored onto the slave database.