Entering content frame

 Starting the Standby Instance as an Active Instance 

If you experience problems with your original instance, then you can stop it, and switch the operational state of the standby instance to ONLINE. The standby instance can then take over the role of the active instance immediately.

Loss of Data

Remember that in this procedure, after you start the standby instance, it does not contain any data changes that have not yet been imported in log backups from the original instance.

If you want to start the standby instance without losing any data, or you want to start it in a state from the past, you have the following options, depending on the configuration and state of your original instance:

·        Importing Log Backups up to a Specific Time

·        Importing Another Manual Log Backup

·        Copying the Log Volumes of the Original Instance

Prerequisites

·        You have set up a standby instance.

·        The standby instance has not been in the operational state ONLINE since it was last initialized.

Procedure

Use the Database Manager for the following steps:

...

       1.      Make sure that the original instance is in the operational state OFFLINE.

       2.      Start the standby instance in the operational state ONLINE.

       3.      In this standby instance, restore any indexes that are no longer up-to-date ( BAD INDEXES).

In the Database Manager GUI, proceed as described in Restoring the Indexes After a Database Restore.

In the Database Manager CLI, use the command sql_recreateindex to recreate a damaged index.

       4.      Make a complete data backup of the standby instance.

Result

You can now operate the former standby instance as an active database instance. The original instance can become the standby instance. To do this, initialize the original instance, and proceed as described in Setting Up a Standby Instance.

 

Leaving content frame