RE: Streams archived_log downstream capture - ORA-16191

From: John Hallas <>
Date: Tue, 8 Apr 2008 16:55:00 +0100
Message-ID: <>

Well I have solved this problem now but I am not sure exactly how.

I amended my source database spfile to have the following entries

LOG_ARCHIVE_DEST_2='SERVICE=DBS2.NET ASYNC NOREGISTER VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) TEMPLATE=/usr/oracle/log_for_dbs1/dbs1_arch_%t_%s_%r.log DB_UNIQUE_NAME=dbs2' -- this line was new

LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbs1,dbs2)' -- new entry, using the DB_UNIQUE_NAME of both databases

The target database had an spfle entry added

LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbs1,dbs2)' -- new entry, using the DB_UNIQUE_NAME of both databases

I still got the ORA-1031 error so I rebuilt the remote password file again and bounced the databases and everything sprung into life.

Thanks for your assistance April

I will add more notes on this to my blog at

-----Original Message-----

[] On Behalf Of John Hallas Sent: 07 April 2008 16:01
To: April Sims;
Subject: RE: Streams archived_log downstream capture - ORA-16191

Thanks April but no success so far

I have followed all those steps but the only difference is that I see an 1031 rather than a 16191 error now

ORA-01031: insufficient privileges
PING[ARC0]: Heartbeat failed to connect to standby 'PERF03'. Error is 1031.

I have changed the password at both ends and recreated the password file and I can connect back and forth using sqplus as sysdba

I can see a forum message problem that was identical but that was resolved by doing an oradim (Windows) whereas I am on Linux.  

-----Original Message-----

From: April Sims []
Sent: 07 April 2008 14:19
To: John Hallas;
Subject: Re: Streams archived_log downstream capture - ORA-16191


I have encountered this in a DATA GUARD environment as well, see fix below. This also fixed problems with Grid Control in 11g.

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

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed, to persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS’ relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS do not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW

Received on Tue Apr 08 2008 - 10:55:00 CDT

Original text of this message