Dbvisit Standby Knowledge Base
Disaster recovery made easy!
- Using an on Premise Primary Database Backup to Create a Standby after Activating your Standby in the Cloud
- Exception in main: resolve: Service not found
- Best Practice: Graceful Switchover Process
- Running standby on same host as primary (Testing/Education purpose only) - Standby version 8
- Move Dbvserver to a new host.
- Applying License after Dbvisit Standby Upgrade from Version 7 to Version 8 Fails
- File Not Found - Return code = 187, Return code = 5051
- Manually restore and rename a single datafile from Primary to Standby prior to 6.0.34
- Archivelogs are not being transferred from primary to standby after an outage
- Use a different Network Interface to send Archivelogs to Standby
- Keeping Cascade Standby up to date after running Graceful Switchover
- Using a Recovery Catalog to Sync Standby and Primary Databases
- Dbvisit Standby and Resetlogs
- Standby Archive apply reports error ORA-00354
- Dbvisit Standby : Graceful Switchover Oracle Cloud to Oracle Cloud
- Dbvisit Standby Daemon Variables
- Preliminary steps for Standby Database in Oracle Cloud TDE Wallet(12.1 and 12.2)
- RAC to RAC switchover for Standby v6
- Copy ASM password file from Primary to Standby
- Configure Cascading Standby Database (Version 8.0)
- Switchover issues in Version 7.0 standby with database 11.1.0.7 in ASM
- Standby Datafile Corrupted During Create Standby Database(CSD) Process
- Standby FAQ's - Version 8.0
- Remove DDC from the GUI console with Broken Links
- Problems with opening standby database read only
- Troubleshooting Dbvisit Standby Network Components
- Renaming / Moving Datafiles in Dbvisit Standby Environment
- Auto start/stop using systemd for standby v8
- Recreate standby database
- Recover Standby Fails using SQLPLUS when performing Graceful Switchover