Error 1017 Ora-16191
Contents |
+ Solutions etc. Saturday, August 23, 2014 ORA-16191: Primary log shipping client not logged on standby After Dataguard (Physical Standby) Configuration ora-16191 primary log shipping client not logged on standby rac (RAC/Non-RAC), Many time I've faced issue that, initially archives are error 16191 connecting to for fetching gap sequence not getting transferred from Primary to Standby Database through RFS even though everything is set properly. So error 1017 received logging on to the standby returning error ora-16191 I thought, I should write about it this time. One of the Cause is : "ORA-16191: Primary log shipping client not logged on standby" You can
Ora-16191 Dataguard
check the same in with the below query as well as in the alert log, SQL> select error from v$archive_dest_Status where dest_id=2; ERROR ----------------------------------------------------------------- ORA-16191: Primary log shipping client not logged on standby ================ Alert Log Portion (Primary) ================ Suppressing further error logging of LOG_ARCHIVE_DEST_2. Sat Aug 23 17:43:09 2014 Error 1017 received logging error 1017 received logging on to the standby 11g 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 Reason: Check for Password File and verify the same using "sqlplus sys/xxxx@TNS as sysdba" from all Database Instances (in case of RAC) of Primary & Standby and it should get connected. In my case though, password file was exist on all locations and even it was able to connect with sqlplus from primary to standby and vice versa, but was still getting "ORA-16191: Primary log shipping client not logged on standby" Workaround/Solution: 1) Disablelog_archive_dest_state_2 for whichlog_archive_dest_2is Standby Location. SQL> show parameter log_archive_dest_2 NAME TYPE VALUE ----------------------------------- ----------- ------------------------------ log_archive_dest_2 string SERVICE=EDQPRDBLR LG
File and Log Shipping By Robert Jackson | 2 Comments The Problem When creating a new DB as the downstream DB for a CDC configuration which is version 11g and the source error 1017 received logging on to the standby 12c DB is 10g, there are many occurrences in the alert log which states that
Error 1017 Received Logging On To The Standby Ora 16191
the source DB cannot authenticate with the downstream database in order to successfully ship the archived redo log file. The below is
Ora-16191 Heartbeat Failed To Connect To Standby
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 http://manishnashikkar.blogspot.com/2014/08/ora-16191-primary-log-shipping-client.html 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 http://www.ora00600.com/wordpress/scripts/changedatacapture/ora-16191/ 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 MISSING Streams multi-version data dictionary ORA-31538 Change Set Disabled Error 604 received logging on to the standby ORA-31403: change table already contains a column Comments (2) Trackback URL | Comments RSS Feed Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Most Popular Posts ORA-04021: timeout occurred while waiting
trace and issue and rendered our Data Guard physical standby database unusable. I added an AFTER LOGON https://oraganism.wordpress.com/tag/ora-16191/ ON DATABASE trigger which collected information about a session and wrote it to a table. You can see the problem already: standby databases are not writable and so this is not going to work. Very soon users connecting to the standby were complaining: ORA-00604: error occurred at recursive SQL level 1
ORA-16000: error 1017 database open for read-only access
ORA-06512: at line 2
ORA-02063: preceding 3 lines from SERVER_RO
00604. 00000 -"error occurred at recursive SQL level %s"
*Cause:An error occurred while processing a recursive SQL statement
(a statement applying to internal dictionary tables).
*Action: If the situation described in the error 1017 received next error on the stack
can be corrected, do so; otherwise contact Oracle Support. Realising my mistake I dropped the trigger but this didn't make the problem go away on the standby. A quick look in the alert log on the primary and there was a logon failure related to Data Guard: 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
------------------------------------------------------------
PING[ARCl]: Heartbeat failed to connect to standby 'SERVER2'. Error is 16191. The secondary's alert log didn't have anything interesting in it. I checked the SYS passwords on both nodes in case an underlying problem had suddenly occurred but all was ok. MOS to the rescue! I checked REDO_TRANSPORT_USER (we don't use it) and SEC_CASE_SENSIT