Dbvisit Standby reversal of configuration file (DDC)

[Arjen Visser]

We have primary DB and stand by DB in different locations. Primary server affected due to the disaster.
How to activate standby database as the primary?

Normally we used the below command to activate standby database.

dbv_orastartstop activate $ORACLE_SID

During the activation it reversal environment files in both servers. We can not able to do the reversal during the primary server down. May I know how to reversal the parameter when the primary server will not be there?
Please advice how to activate standby database as primary in this situation?

[Arjen Visser]

The command:
dbv_orastartstop activate $ORACLE_SID
Is also used to activate the standby database when the primary server is not there.

This command only reverses the environment file on the standby server. When Dbvisit is run on the newly activated primary database on the standby server, the environment file is copied to the old primary server and replaces the old environment file. That is why it appears that the file is reversed on both the primary and standby servers.

Note:
To manually reverse the environment file the following command can be used:
dbv_orastartstop update_ddc_file $ORACLE_SID