Best Practices

Article Description

This is a collection of Best Practice guidelines for working with Dbvisit Standby, notes which may or may not exist in the User Guide, and which will be added to over time.

Initial Configuration

We recommend setting FORCE LOGGING on your primary database to prevent NOLOGGING transactions flowing through and potentially causing issues on your standby database. For more detail please read here:

Failover/Graceful Switchover

Scheduled database jobs should be DISABLED before initiating these processes. During GS, for example, tempfiles are dropped. If scheduled jobs attempt to run before new tempfiles have been created then they will fail with errors like:

ORA-25153: Temporary Tablespace is Empty.

Once GS has been completed then you can reschedule the database jobs.

Mike Donovan August 06, 2014 12:30

Have more questions? Submit a request