Init parameterData Guard

LOG_ARCHIVE_CONFIG

What it controls

The DB_UNIQUE_NAMEs of every database in the Data Guard configuration.

Know this before you change it

Must list the same names on every member.

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'log_archive_config';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'log_archive_config' AND isspecified = 'TRUE';8 9-- Dynamic: takes effect now and is kept after a restart10ALTER SYSTEM SET log_archive_config = 'DG_CONFIG=(ORCL,ORCLSTBY)' SCOPE = BOTH SID = '*';11 12-- Remove it from the spfile to go back to the default at the next restart13ALTER SYSTEM RESET log_archive_config SCOPE = SPFILE SID = '*';

Related scripts

• Redo destinations and transport errorsEvery active archive destination with its status, gap state and last error. Any text in the ERROR column means redo isn't reaching that standby.

Open in the parameter referenceOracle's reference

More in Data Guard

• DG_BROKER_STARTStarts the Data Guard broker process (DMON).
• FAL_SERVERNet service names a standby asks for missing archived logs.
• STANDBY_FILE_MANAGEMENTWhether datafiles added on the primary are created automatically on the standby.
• DB_UNIQUE_NAMEA name that's unique to each database in a Data Guard configuration, used by the broker, services and file naming.