APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.
SYMPTOMS
ORA-16191 error in alert log file. Archive shipping and apply at standby site impacted due to this error.
Errors in file /u02/app/oracle/diag/rdbms/ebsprd/EBSPRD1/trace/EBSPRD1_arc0_112725.trc:
ORA-16191: Primary log shipping client not logged on standby
FAL[server, ARC0]: Error 16191 creating remote archivelog file 'ebsodr_s2'
ARC0: FAL archive failed with error 16191. See trace for details
Sat Jul 07 11:00:36 2018
Errors in file /u02/app/oracle/diag/rdbms/ebsprd/EBSPRD1/trace/EBSPRD1_arc0_112725.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Sat Jul 07 11:00:36 2018
CHANGES
SYS password change at primary database.
CAUSE
In Oracle 11g onward passwords are case sensitive. So use ignorecase=Y option while creating password file
If password file created without ignorecase=Y option, then we may face ORA-16191 errors in alert log due to mismatch in SYS password at primary and standby sites.
Also when password for SYS changed Or new password file created at primary side, password file needs to be recreated at standby side with same password (no need to copy the password file to standby, just recreate password file using orapwd in all standby sites.
SOLUTION
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.
REFERENCES
NOTE:2225190.1 - Error 1017 / ORA-16191 In Standby Alertlog
NOTE:1368170.1 - Troubleshooting ORA-16191 and ORA-1017/ORA-1031 in Data Guard Log Transport Services or Data Guard Broker
