Tag Archives: ORA-16191

Use of log_archive_config parameter in Oracle Dataguard

Use of log_archive_config parameter in Oracle Dataguard

Log archive config is used to send/accept the redo logs to remote location and receipt of remote redo logs. It used as value DB_UNIQUE_NAME value defined in both init file. It allows me to managed Primary & Standby because it lists the DB_UNIQUE_NAME values for all databases within the configuration.

In my case primary or standby have only two Servers:
ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRIM,PRIM_STBY)';

Note: DB_NAME parameter has same name.

Values of Parameter:

SEND: Enable the sending of redo log to Remote location.
NOSEND: Disable the sending of redo log to remote location.
RECEIVE: Enable the receipt of remotely archived redo logs.
NORECEIVE: Disable the receipt of remotely archived redo logs.
DB_CONFIG: list of 9 services provider name in data-guard configuration.
NODB_CONFIG:Eliminates the list of service provider names

Note: DB_UNIQUE_NAME values of the primary and standby database should be used in the DG_CONFIG setting of the LOG_ARCHIVE_CONFIG parameter.

Example
The standby database will have the value as :

ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRIM,PRIM_STBY)';

Error
ORA-16191: Primary log shipping client not logged on standby
Solution
Error may fixed with by setting following parameters as follows:

LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRIM,PRIM_STBY)' — new entry, using the DB_UNIQUE_NAME of both databases

Advertisements