ORA-16191- Applicable to Streams, DATA GUARD Errors in 11g

This feature is apparently still true in version….just verified it.
Couldn’t add the database using OEM just produced errors that don’t show up when searching MOS. I then used Data Guard Manager command-line utility as it tends to produce an error I can do something with. This is the symptom shown below:

DGMGRL> add database PPRDBY as connect identifier is ‘PPRDBY’
>  maintained as physical;
Error: ORA-01017: invalid username/password; logon denied

Recreated password file, ignorecase=Y.

See MOS Document : DATA GURAD LOG SHIPPING FAILS WITH ERROR ORA-16191 IN 11G [ID 462219.1] (this GURAD misspelling is how it displays in MOS)

Errors when trying to add a physical standby in a mixed environment (Windows and Linux in 11g).  This also fixed problems with adding a database to Grid Control (when logging onto as sysdba).  Streams errors in v$archive_dest were also resolved by turing OFF the case sensitive featues in
Note: Any database will have to be bounced to use a new password file.

Data Collected


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

Support Update


The issue seems to be because of password mismatch between primary and standby.

The password file has to have identical authentication info for both primary and standby

If you change or create the password file using orapwd for SYS,it will not work in 11G.

Action Plan


Turn off the case sensitivity option by changing init.ora parameter SEC_CASE_SENSITIVE_LOGON=FALSE.

Create password files on both servers using the same password and pass ignorecase=Y to orapwd utility.

Make sure you use identical options during password file creation for both primary and standby


About April C Sims

Oracle DBA for over a decade...enough said.
This entry was posted in DATA GUARD, Physical Standby and tagged , , . Bookmark the permalink.

2 Responses to ORA-16191- Applicable to Streams, DATA GUARD Errors in 11g

  1. John Hallas says:

    One way to test password and orapw files settings is to sqlplus sys/password@remotedb as sysdba from both nodes

  2. aprilcsims says:


    Thanks. It my case (hetergeneous environment) testing with sqlplus sys/password@remotedb as sysdba didn’t produce any errors. The error was seen by querying v$archive_dest and observing an ORA-16191 for the standby site.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s