Activate standby

If your product is not connected, and is only registered, your warranty coverage will be 5 years. Proof-of-purchase in the event of an insurance loss such as fire, flood or theft Easy access to Generac's full online support features. Oracle uses the information from the controlfile to determine where to create the redo log files. In the example below the redo log is renamed to an invalid filename to emulate what happens when the standby database is activated:. The database is still a standby database as the activation failed.

We cannot manually create the redo logs, as this is an Oracle internal operation. The only thing we can do is to give the correct location for the redo log files. Rename the redo log to the correct location:. The standby database has been activated and is now a primary database. Oracle has created the redo logs at the location specified. Note: all previous backups of this database are now invalid and cannot be used to restore this database.

The SCN number of the database is not reset. Dbvisit Standby will prompt before activating the standby database. If the --force an option is provided then Dbvisit Standby will no longer prompt before activating the standby database this option can be used in batch mode.

Before you activate the standby database, running a quick test by ensuring the standby database is in a consistent state datafile headers and controlfile are in sync and ready to be activated. This can be done by opening the standby database read-only. As we can see in the example above, the standby database can be opened read-only without any errors. Now that we know we can open the standby read-only, let's start it back into recovery mode mount state , by running: ".

Now that we know the standby database can be opened read-only and that it is in a consistent state that it can be opened, we can execute the "Activation". This task, while not required, is a recommended safety measure because you cannot recover changes made after activation without a backup. In case of disaster strikes, you will want to activate failover to the standby database. The standby database is then converted to a primary database and cannot be used as a standby database anymore.

In the version 10 of Dbvisit Standby, a number of new options have been introduced in this section. First select "Disaster Recovery Actions" from the main menu [1]. Once you select a DDC on which the operation is to be performed, there are 3 options are now provided as listed below:. Select this option if you want to activate the standby database now - this is usually in the case when the disaster happened and you need to activate failover to the standby database.

It is always recommended that sites perform DR testing, activating a standby database and making use if a disaster did happen everything work as expected. This option will allow you to perform a backup of the standby database prior to activating it. In case of disaster with Primary Database site, or not available for production for any reason then we can activated standby database as a primary production database.

Note: If you are trying to activate standby database for production use, please get permission from senior authority to do so. Copy archive logs from primary database, those yet to apply on standby database before activate it. Standby database successfully activated as Primary database.