This document is intended for a technical audience. Experience with the Oracle,SQLServer database and standby databases is necessary to install Dbvisit Standby.
Experience with Linux is necessary to install Dbvisit Standby on Linux.
Experience with UNIX is necessary to install Dbvisit Standby on UNIX.
Experience with Microsoft Windows is necessary to install Dbvisit Standby on Microsoft Windows.
Some features described in this manual will only apply to the latest version of Dbvisit Standby MultiPlatform.
2. Contact Information
Dbvisit Standby Support Service desk: http://support.dbvisit.com
Please include Dbvisit Standby trace files to ensure a fast turnaround on support issues.
Please see the Dbvisit website: www.dbvisit.com for other up to date contact information.
3. Copyright Notice
Copyright © 2000-2021 Dbvisit Software Limited. Except as specifically set out the Dbvisit license agreement, nothing in this Documentation constitutes a warranty as to the operation of the Dbvisit Standby software.
All rights reserved. Specifications are subject to change without notification.
This document is the property of Dbvisit Software Limited. Dbvisit Standby is a product of Dbvisit Software Limited.
This software product is licensed, not sold.
Dbvisit is a registered trademark.
Oracle is a registered trademark of Oracle Corporation.
SQL Server is a registered trademark of Microsoft Corporation.
Windows is a registered trademark of Microsoft Corporation.
All other brand names and trademarks are the property of their respective owners.
4. Disclaimer, Terms and Conditions
By installing, using and running this software, you agree that Dbvisit Software Limited and their associated companies and partners will not be held responsible for anything related to installing or running Dbvisit Standby.
By installing, using and running this software, you agree with the terms and conditions displayed during the installation process of Dbvisit Standby.
For the complete Dbvisit Standby license agreement (LA), see:
Some of the features described in this document only apply to the latest version of Dbvisit Standby.
Specifications are subject to change without notice.
5. Important Notice
Oracle strongly recommends that all NOLOGGING operations are avoided in the primary database.
Oracle will not be able to keep the standby database consistent with the primary database during nologging operations.
To ensure this does not happen, Oracle introduced the command (version 9i and above):
SQL> ALTER DATABASE FORCE LOGGING;
This ensures that all database write operations are logged, and the standby database will be consistent.
Enable Force Logging in PDB
SQL> alter session set container=MYPDB1; Session altered. SQL> select pdb_name, logging, force_logging from cdb_pdbs; PDB_NAME LOGGING FORCE_LOGG -------------------- --------- ---------- MYPDB1 LOGGING NO SQL> ALTER PLUGGABLE DATABASE MYPDB1 OPEN READ WRITE RESTRICTED FORCE; Pluggable database altered. SQL> ALTER PLUGGABLE DATABASE MYPDB1 ENABLE FORCE LOGGING; Pluggable database altered. SQL> ALTER PLUGGABLE DATABASE MYPDB1 OPEN READ WRITE FORCE; Pluggable database altered. SQL> select pdb_name, logging, force_logging from cdb_pdbs; PDB_NAME LOGGING FORCE_LOGG -------------------- --------- ---------- MYPDB1 LOGGING YES
For SQL Server, the user databases which are part of Dbvisit, the recovery model must be set to FULL. In the below example for databases NEW and AdventureWorks, the recovery model has been set to FULL as pointed out in below figure.
You can also refer to the below Microsoft documentation link on how to view the recovery model and change the recovery model from SIMPLE to FULL.