Dbvisit Standby Versions
v8, v9, v10 and v11
Option 1:
1. Change Oracle registry entry ORA_SID_AUTOSTART to FALSE. This will start Windows Oracle Service automatically on startup, but the Oracle instance will remain down
2. Create a new Windows scheduler task to run the Dbvisit start database command to start the Standby database in recovery mode. It's best to start with a delay of 1 min to be extra sure that the startup DB task will be triggered after Oracle Service is running.
dbvctl.exe -d <DDC> -o start
Please note the location of dbvctl executable is different in v8,v9 &v10 version i.e "C\Program Files\Dbvisit\standby\dbvctl"
3. Dbvisit services startup set to "automatic delayed".
Option 2:
This is the simplest way to start the Standby database in recovery mode. By setting the below DDC parameter the Dbvisit automatic standby update(daemon process in v8,v9,v10) ensure that the Standby database is started in the correct mode when applying the archive log.
The only disadvantage of this option is you cannot use the standby database for read-only reporting purposes
1) Retain the default database startup setting which starts the Standby database in read-only mode. Set the Oracle database service to autostart and ORA_SID_AUTOSTART to TRUE.
2) Set the below parameter in the Dbvisit DDC file
APPLY_READ_ONLY =Y
APPLY_READ_ONLY
This parameter only apply to the standby database.
If the standby database is in READ ONLY mode, the recovery of the standby database will not continue as recovery cannot happen if the standby database is open read only.
If this parameter is set to Y, the standby database will be restarted into recovery mode if it was in read only mode.
Default value:
APPLY_READ_ONLY = N
Note: be careful when setting this parameter to Y, you might want the database to stay in read only mode and not to be started in recovery mode if dbvisit standby is run on the standby to apply logs.
3. Dbvisit services startup set to "automatic delayed".
Comments