Stopping the Secondary and Breaking FailSafe

This procedure allows you to shut down the secondary database while maintaining the primary as a standalone database. A clean log switch is executed as part of the procedure.

Procedure

1. Select option 6 on the Miscellaneous menu. A confirmation prompt is displayed — enter y to continue.

2. If Transaction Logging is active, you are asked to specify the clean log to switch to, before performing the save. A menu similar to the following is displayed:

   Switch to :
   1.  Another Clean Log for today (CLOG990731-02)
   2.  Next Day's Clean Log (CLOG990801-01)
   3.  Clean Log for named day or date
   4.  A named Clean Log
   Enter option (1-4) : _

   Select the option  you require:
   1. Automatically creates and switches to a clean log with today's date, named according to the standard naming conventions for clean logs.
   2. Automatically creates and switches to a clean log with tomorrow's date named according to the standard naming conventions for clean logs.
   3. Creates a clean log name using the standard naming conventions for the day of the week (e.g. Mon) or the date (13/06/99) that you specify and switches logging to it. This option prompts you for the day or date.
   4. Creates and switches to a clean log with any name that you specify.

   Note

   It is recommended that you use the standard clean log naming conventions (for example, CLOGyymmdd-nn) when selecting a log name. Refer to the topic Naming Conventions for Clean Logs.

   Having selected the clean log name, you are asked to confirm that you want to switch to the specified clean log. Enter y to continue with the clean log switch.

3. You are then asked:

   Do you want to archive previous Clean Log (y/n/q) ? :

   • Enter y  to archive the previous clean log.
   • If you enter n,  the archive procedure is omitted. Go to step 6.

4. You are then asked:

   Do you want to run the archive on the secondary (y/n/q) ?

   Enter y  to archive the clean log on the secondary or n  to archive it on the primary.

5. A list of tape units configured on the selected database is then displayed and you are prompted to select one to carry out the archive. Enter the number of the required tape device.

6. Logging is switched to the new clean log, the secondary database is shut down and the FailSafe link disconnected.

   Note

   The databases are marked as 'Failed' and synchronisation is therefore lost. To restore normal FailSafe operation you must resynchronise using option 4 on the FailSafe Database Recovery menu. You will need to use Option 3 on this menu first if further clean log switches are carried out on the primary while the secondary is shutdown.

   If you did not request archiving of the previous clean log, the procedure is now complete — press return to return to the Miscellaneous menu.

7. If you requested archiving of the previous clean log, the following prompt is displayed:

   Mount write enabled tape on LOCAL [or REMOTE] tape unit n for Clean Log archive.
   Are you ready to continue (y/n/q) ?

   Note

   If you selected archive on the secondary in step 5, the tape must be mounted on the secondary machine.

   Ensure that the tape is loaded and the tape unit is on-line. Then enter y to continue.

   tlmenu logs on to the selected database and executes tape operations to archive the clean log and verify the archived log.

8. Once the archive tape has been verified, you are asked if you want to remove the clean log from disk:

   Delete Clean Log clog_name from Disk (y/n/q) ? :

   Enter y to delete the clean log, just archived, from both databases.

   Note

   If an error condition occurs during the archiving or verification of the clean log, the following message is displayed:

   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 Miscellaneous menu.

The procedure is now complete and you are returned to the Miscellaneous menu.