ORA-16191 and ORA-1017 reported for Log Transport to Standby when using "redo_transport_user"
(Doc ID 2848435.1)
Last updated on APRIL 29, 2022
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Database name : ORCL
Primary db db_unique_name : ORCL
Standby db db_unique_name : ORCLDR
ORA-16191 and ORA-1017 reported for Log Transport when using "redo_transport_user"
Following checks were done and passed
1. Check where the Password File is located :
a. If within '$ORACLE_HOME/dbs", then File naming should be as "orapw$ORACLE_SID" (example : orapwORCL)
For RAC, need to ensure that correct ORACLE_SID/INSTANCE_NAME is reflecting in the Password File Name of each instance (orapw$ORACLE_SID => example : orapwORCL1, orapwORCL2)
b. Password File within ASM Disk Group and registered in OCR
Check the output of "$ srvctl config database -d <db_unique_name>" to see if Password File field is populated
2. Checksum of Password Files at Primary and Standby should match
Check the output of "md5sum orapwORCL" at each Node of Primary and Standby
If set to TRUE, then ensure that password file is created with option IGNORECASE=N
If set to FALSE, then ensure that password file is created with option IGNORECASE=Y
Redo transport configured to use 'redo_transport_user=REDO_USER'
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document