Error 1017 / ORA-16191 In Standby Alertlog

刘泽宇

SYMPTOMS
We see Error 1017 / Error 16191 in alertlog of primary:

Wed Dec 07 15:40:36 2016
Media Recovery Waiting for thread 1 sequence 123569
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
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 rmseprod for fetching gap sequence
Wed Dec 07 15:41:12 2016

In this case rmseprod is the FAL_SERVER and points to primary database. A manual sqlplus connection to primary is fine using: sqlplus sys/password@rmseprod as sysdba

Also, we verified that password file is copied from primary and it's checksum matches with the one on primary.

CAUSE
In this particular case, customer had a custom (non-Oracle supplied) login trigger on primary. This was preventing standby to connect to primary to query gap status.

SOLUTION
After disabling the login trigger in primary, the errors were resolved.