All of these prerequsites must be fulfilled before creating and using Dbvisit StandbyMP Configuration for Oracle database
...
If there was any database existing on standby server (you’re for example re-creating standby database), then cleanup is necessary. You must delete all old standby database files from standby server.
Before creating standby database, you must ensure that the standby server doesn’t contain any old database files.
...
If there are old database files on standby server, but database can’t be started, you will have to cleanup all locations manually
| Note |
|---|
Take special care to cleanup all files in db_recovery_file_dest. This is especially important for standby servers with ASM storage. |
7. Verify Standby Server Memory Limits
...
| Info |
|---|
You can consider removing archivelog deletion step from your own backups and enabling Dbvisit AMM on your primary to purge archivelogs: https://dbvisit.atlassian.net/wiki/spaces/DSMP/pages/3349217327/Archivelog+Management+Module#5.1-Primary-Archive-Management-Settings |
9. Sqlnet.ora authentication services
By default, Dbvisit uses bequeath “sqlplus / as sysdba” connection to interact with ASM and Oracle Database Instance on the porimary and standby servers. You must ensure following:
On Windows, sqlnet.ora in $ORACLE_HOME\network\admin contains:
| Code Block |
|---|
SQLNET.AUTHENTICATION_SERVICES = (NTS) |
On Linux sqlnet.ora in $ORACLE_HOME/network/admin contains:
| Code Block |
|---|
SQLNET.AUTHENTICATION_SERVICES=ALL |
Note that if you’re using Read-Only Oracle home, the path to your sqlnet.ora will be different.
| Note |
|---|
It is impossible to create DDC configuration if you’re enforcing SYS password requirement (your setting is SQLNET.AUTHENTICATION_SERVICES=NONE) In this case, you must disable the SYS password requirement by modifying SQLNET.AUTHENTICATION_SERVICES to NONE or (NTS). After DDC is created, you can modify DDC file with SYS password as per: And then you can set your SQLNET.AUTHENTICATION_SERVICES back. |