To place the standby database in manual recovery mode

1. Use SQL*Plus to connect to the standby instance and then start the Oracle instance at the standby database. For example, enter:

   STARTUP NOMOUNT pfile=initSTANDBY.ora
   

2. Mount the standby database:

   ALTER DATABASE MOUNT STANDBY DATABASE;
   

3. If log transport services are not archiving logs automatically to the standby site, then manually copy the logs to the desired location on the standby site using an appropriate operating system utility for transferring binary data. For example, enter:

   % cp /oracle/arc_dest/*.arc /standby/arc_dest
   

4. Issue a RECOVER statement to place the standby database in manual recovery mode.

   Note: Specify the FROM 'location' option only if the archived log group is not in the location specified by the LOG_ARCHIVE_DEST_n parameter (where n is an integer from 1 to 10) or the LOG_ARCHIVE_DEST_n parameter in the standby initialization parameter file.

   For example, execute one of the following statements:

   RECOVER STANDBY DATABASE # uses location for logs specified in
                      # initialization parameter file
   RECOVER FROM '/logs' STANDBY DATABASE # specifies nondefault location
   

As the Oracle database server generates archived redo logs, you must continually copy and apply them to the standby database to keep it current.

When Is Manual Recovery Required?

Manual recovery mode is required in a non-Data Guard environment. A non-Data Guard environment is one in which you manually:

• Transfer the archived redo logs from the primary site to the standby site
• Apply the archived redo logs to the standby database

Even if you implement a Data Guard environment, you might occasionally choose to perform. manual recovery on the standby database. For example, you might choose to manually resolve an existing archive gap by using manual recovery mode