Data Guard Administration
Common Creation Tasks
- Primary Database Changes
- Network Changes
- RMAN Backup and File Copy
- Standby Database Changes:
- Configure Broker
- Enable Flashback Database
Specs used in examples:
IP Hostname Role db_name db_unique_name ORACLE_SID (Env Var)
-------------- --------- ------- -------- --------------- --------------------
192.168.56.101 lnx01 Primary oradb oradb oradb
192.168.56.102 lnx02 Standby oradb oradb_sb oradb_sb
For RAC examples lnx03 (192.168.56.103) is used for the SB host while lnx01 & lnx02 are the nodes.
Some names\passwords are now case sensitive so you may need to consider:
alter system set sec_case_sensitive_logon=false scope=both;
- Creating the password file on Primary using ignorecase.
orapwd file=$ORACLE_HOME/dbs/orapwMyDB password=mypw entries=10 force=y ignorecase=y
- Check case and ownership of password file.
ls -l $ORACLE_HOME/dbs/orapw*
- Using lower case for all listener and tnsnames.ora entries.
- For 12.2\18c add sqlnet.ora entry:
See Case-Insensitive Passwords
- If Flashback Database is not enabled, you will have to manually recreate your Primary as a Standby in a failover event to reinstate it.
With multi-terabyte databases common and depending on the network connectivity between your primary and standby sites, this could end up being quite a lengthy process.
- For RAC & Oracle-Restart the listener.ora static service entries must be the DATABASE ORACLE_HOME. Not GRID_HOME.
- Password File (12c and earlier)
- If a SYSDBA account password is changed (SYS) you have to recopy the password file to the Standby. It is not replicated.
- Because of encryption changes, you might need to copy the password file from Primary rather than recreating it on the Standby.
The PROFILE for SYS\SYSDBA may need to be less restrictive.
ALTER PROFILE default LIMIT PASSWORD_LIFE_TIME UNLIMITED;
ALTER PROFILE default LIMIT PASSWORD_REUSE_TIME UNLIMITED;
- For 18c and later the Primary and SB OS must have at least 8gb RAM or more.