...
Second standby database:
Copy the DDC file (dbv_w112g2.env) from the second standby server to the new primary server and edit the DDC file so that SOURCE= the new primary server
Schedule Dbvisit Standby on the new primary server with command:
dbvisit w112g2
Third standby database:
Copy the DDC file (dbv_w112g3.env) from the third standby server to the new primary server and edit the DDC file so that SOURCE= the new primary server.
Schedule Dbvisit Standby on the new primary server with command:
dbvisit w112g3
Dbvisit Standby will now keep all 3 standby databases in synch with the new primary database.
Multiple standby databases: setup guidance
Please follow these guide lines to ensure optimal performance of Dbvisit in a multiple standby databases scenarios:
- Set separate locations for ARCHTMP for multiple DDC files (RAC and ASM primary)
If multiple standby databases reside on the same DESTINATION server, use separate ARCHDEST locations
If using compression, set COMPRESS to dbvisit or gzip (the latest on UNIX only) and leave KEEP_ORIG_FILE_BEFORE_COMPRESS at default value Y
Use the same Dbvisit repository (same DBUSER in all DDC files) for all standby databases related to a given primary. Setting separate repositories for multiple standby databases will disable Dbvisit functionality to obtain information about Dbvisit processes that transfer logs from the same primary database but use different DDC files