ORA-16191 & Error 1017 – Password File and Log Shipping

The Problem

When creating a new DB as the downstream DB for a CDC configuration which is version 11g and the source DB is 10g, there are many occurrences in the alert log which states that the source DB cannot authenticate with the downstream database in order to successfully ship the archived redo log file.

The below is what is displayed in the alert log:

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

Wed Mar 30 15:00:03 2011
Errors in file d:\oradata\test\bdump\test_arc1_4704.trc:
ORA-16191: Message 16191 not found; No message file for product=RDBMS, facility=ORA

PING[ARC1]: Heartbeat failed to connect to standby ‘TEST2’. Error is 16191.

There are a few sanity checks that you should check first of all, including:

  • Check TNSPings work between the source and destination DBs
  • Ensure TNSNames entries for both homes are correct
  • Confirm that you are using the same SYS password on both DBs
  • Verify the init.ora parameter remote_login_passwordfile is SHARED or EXCLUSIVE

The Cause

The cause was as stated above – the source DB could not connect to the downstream DB in order to register and ship the log file across.

The Solution

I had run through all of the checks above and all of them worked. I really had no idea what else could be causing the authentication issues that the error was showing. As a last resort, I decided to create the password file for the 11g DB with the 10g orapwd utility….And guess what? It worked! Very strange but it did the trick so I’m now happy.

If you have managed to overcome this problem, you next encounter the “Waiting for Dictionary Redo” wait event when registering the archived redo logs and checking the V$STREAMS_CAPTURE view.

Like it, share it...

Category: Change Data Capture

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *