ORA-16191: Primary log shipping client not logged on standby

I got ” ORA-16191: Primary log shipping client not logged on standby ” error in Oracle dataguard.

ORA-16191: Primary log shipping client not logged on standby

Details of error are as follows in the Alertlog of Standby database.

ORA-16191: Primary log shipping client not logged on standby
Mon Apr 19 02:45:33 2021
Error 1017 received logging on to the standby
------------------------------------------------------------
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE, 
and that the SYS password is same in the password files.
returning error ORA-16191
------------------------------------------------------------
FAL[client, USER]: Error 16191 connecting to MSDB for fetching gap sequence
Mon Apr 19 02:45:33 2021
Errors in file /u01/app/oracle/diag/rdbms/MSDBdg/MSDB/trace/MSDB_pr00_8188.trc:
ORA-16191: Primary log shipping client not logged on standby

ORA-16191

This error is related with the missing of password file on both production and standby side. Sometimes password files may be corrupted or removed accidentally.

To solve this problem, perform the following steps.

1. Stop media recovery at standby side

2. Recreate password file with ignorecase=Y option (both in primary and standby sites with same password)

orapwd file=orapwtestdb password=sys entries=100 ignorecase=Y     ---> change password file name accordingly

3. Initiate media recovery at standby side

4. Monitor alert log and make sure archive logs are applying fine at standby side.

If the password file is missing, then create it  with ignorecase=Y option as follows.

orapwd file=orapwd$ORACLE_SID password=welcome1 entries=5 FORCE=Y ignorecase=Y 

Then copy this password file to Standby. If your database is Oracle RAC, then copy this file to all node.

Mostly DBAs are changing the sys password of Production database but they forget to copy it to Dataguard database.

To solve this error, check your sys password and password file.

You can check and test the Production and Standby Side connections as follows.

Primary Side:

run sqlplus as follows.

sqlplus /nolog

Then run the following code, type your sys password and TNS Alias correctly.

connect sys/welcome@PROD_ALIAS as sysdba
Connected.
SQL> connect sys/welcome1@STANDBY_ALIAS as sysdba
Connected.

Standby Side:

run sqlplus as follows.

sqlplus /nolog

Then run the following code, type your sys password and TNS Alias correctly.

connect sys/welcome1@PROD_ALIAS as sysdba
Connected.
SQL> connect sys/welcome1@STANDBY_ALIAS as sysdba
Connected.

If the above connection test is not worked fine, then fix your password file or create it again.

Or you can copy it from the correct Primary Node to Other Primary nodes and Standby Side.

Do you want to learn Oracle dataguard, then read the following articles.

Oracle DataGuard Physical Standby Installation Step by Step Using RMAN -1