Scribd
Upload
47 views1 page

Activating The Standby Database

To activate a standby database in the event of a failure of the primary production database, follow these steps: cancel recovery mode, manually apply any remaining logs, cancel recovery, activate the standby to convert it to a production database, shut it down, backup the new production database before starting it, and redirect users to the new database. The activated standby now becomes the new full production database.

Uploaded by

Joe Somebody
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
47 views1 page

Activating The Standby Database

To activate a standby database in the event of a failure of the primary production database, follow these steps: cancel recovery mode, manually apply any remaining logs, cancel recovery, activate the standby to convert it to a production database, shut it down, backup the new production database before starting it, and redirect users to the new database. The activated standby now becomes the new full production database.

Uploaded by

Joe Somebody
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Activating the Standby Database

You now have an operational, automatically updated standby database that you may activate in the event of a catastrophic production failure. Once activated, the standby database becomes a production-like instance that cannot be converted back to its previous form. If the standby database is already in ASD mode when a failure occurs, follow these steps to activate the standby database: 1. If possible, archive your current production database logs by issuing ALTER SYSTEM ARCHIVE LOG CURRENT on the production database. Copy the current online redo logalong with any other remaining archived logs that have not yet been transportedto the standby database server. 2. If your standby database has not timed out from your recovery, simply open a new SQL session into the standby database, by using a DBA account, and issue
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

3. Locate the end of the standby database's alert.log, and identify the last archived log that was applied. 4. Manually apply any remaining logs to the standby database:
SQL> ALTER DATABASE RECOVER [FROM 'pathname'] STANDBY DATABASE;

5. When you have applied the remaining logs to the standby database, stop the recovery by issuing
SQL> ALTER DATABASE RECOVER CANCEL;

6. Convert the standby database to a production environment:


SQL> ALTER DATABASE ACTIVATE STANDBY DATABASE;

7. Shut down the standby database. The standby is now a full-fledged production database. Assuming that the standby database is the only working database at this point, it is highly advisable that you immediately perform a backup before starting the database for production use in the event of another emergency. 8. Start the new production database as you would start any other database. 9. Initiate any and all necessary processes that will redirect users smoothly to the new production database. Now that your database users have safely migrated to the standby database, you can begin the process of recovering your production database.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy