Error 12170 Received Logging On To The Standby
Contents |
not send to the standby [message error 12154 received logging on to the standby #543497] Wed, 15 February 2012 01:12 andy huang error 12154 received logging on to the standby 11g Messages: 498Registered: July 2011 Senior Member Dear all, The archive log can not error 12154 received logging on to the standby rac send to the standby database, how to do? primary database spfile: *.db_name=oracl *.db_unique_name=oracl *.log_archive_config='dg_config=(oracl,oraclbak)' *.log_archive_dest_1= 'location=/u01/app/oracle/duplicate/ valid_for=(all_logfiles,all_roles) db_unique_name=oracl' *.log_archive_dest_2= 'service=oraclbak
Error 1031 Received Logging On To The Standby
async valid_for=(online_logfiles,primary_role) db_unique_name=oraclbak' *.log_archive_dest_state_1=enable *.log_archive_dest_state_2=enable *.remote_login_passwordfile=exclusive *.log_archive_format=%t_%s_%r.arc *.log_archive_max_processes=30 *.fal_server=dup_oracl *.standby_file_management=auto standby database spfile: *.db_name=oracl *.db_unique_name=oraclbak *.log_archive_config='dg_config=(oracl,oraclbak)' *.log_archive_format=log%t_%s_%r.arc *.log_archive_dest_1= 'location=/u01/app/oracle/duplicate/ valid_for=(all_logfiles,all_roles) db_unique_name=oraclbak' *.log_archive_dest_2= 'service=oracl async valid_for=(online_logfiles,primary_role) db_unique_name=oracl' *.log_archive_dest_state_1=enable *.log_archive_dest_state_2=enable *.remote_login_passwordfile=exclusive *.standby_file_management=auto *.fal_server=tar_oracl primary database and standby database using the same tnsnames.ora # error 1031 received logging on to the standby ora-01031 insufficient privileges tnsnames.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora # Generated by Oracle configuration tools. TAR_ORACL = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.30.43)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = oracl) ) ) DUP_ORACL = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.30.37)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = oraclbak) ) ) error message: *** 2012-02-15 08:01:24.611 60679 kcrr.c Error 12170 received logging on to the standby Error 12170 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'oraclbak' Error 12170 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'oraclbak' ORA-12170: TNS:Connect timeout occurred *** 2012-02-15 08:01:24.625 58941 kcrr.c kcrrfail: dest:2 err:12170 force:0 blast:1 kcrrwkx: unknown error:12170 ORA-16055: FAL request rejected ARCH: Connecting to console port... ARCH: Connecting to console port... kcrrwkx
Error 12170 received logging on to the standby Error 12170 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'oraclbak' Error 12170 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'oraclbak' ORA-12170: TNS:Connect timeout occurred *** error 1033 received logging on to the standby 2012-02-15 08:31:50.678 60679 kcrr.c PING[ARCq]: Heartbeat failed to connect to standby 'oraclbak'. Error is
Error 12514 Received Logging On To The Standby
12170. *** 2012-02-15 08:31:50.680 58941 kcrr.c kcrrfail: dest:2 err:12170 force:0 blast:1 kcrrwkx: nothing to do (end) View 6 Replies Similar
Error 12514 Received Logging On To The Standby Oracle
Messages: Data Guard :: How To Delete Archive Log On Standby Data Guard :: Archive Not Applied On Standby Data Guard :: Transfer Of Archive Log On Standby Database Data Guard :: Difficulty In http://www.orafaq.com/forum/t/178882/ Detecting Archive Gap On Physical Standby Data Guard :: Archive To Complete Recovery On Standby Database Data Guard :: Applying Incremental Backup On Standby To Resolve Archive Log Gap? Data Guard :: Apply Standby Redo Log To Physical Standby Database Data Guard :: Possible To Convert Logical Standby To Physical Standby Data Guard :: How To Know Current Active Guard Settings In Standby Database Data Guard :: Standby http://oracledba.bigresource.com/Data-Guard-archive-log-cannot-send-to-Standby-fLkChsFxu.html Redo Log On Standby Data Guard :: Archive Gap Script Data Guard :: Archive Log Deletion Data Guard :: Detecting Archive Log Gaps? Data Guard :: Archive Copied Onto DR But Not Applied? Data Guard :: Confirm Particular Archive Log File Applied Or Not? Data Guard :: App Archive Logs Which Come From Primary Database? Data Guard :: Setup/ Archive Destination Configuration Data Guard :: Redo Archive Logs Missing Data Guard :: Archive Logs Are Being Shipped But Not Applied Data Guard :: Find Archive Log Gap From Primary Database Site? Data Guard :: Unable To Get Data Of Primary In Standby Database (dataguard) Data Guard :: RMAN Archive Log Backup With Delete Input Command Data Guard :: Unable To Get Data Of Primary In Standby Database Data Guard :: Can't Connect To Standby DB Data Guard :: Physical Standby With Same SID Data Guard :: How To Apply Archives In Standby Data Guard :: How To Get SQL Plan In Standby Database Data Guard :: Recreating Physical Standby Data Guard :: Oracle 9i Logical Standby ADVERTISEMENT Data Guard :: How To Delete Archive Log On Standby Jun 18, 2011 We are planning to setup a data guard (Maximum performance configuration ) bet
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not https://community.oracle.com/thread/3962260 work correctly without it enabled. Please turn JavaScript back http://arup.blogspot.com/2009/12/resolving-gaps-in-data-guard-apply.html on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Data Guard All PlacesDatabasePerformance & AvailabilityData Guard 3 Replies received logging Latest reply on Aug 21, 2016 5:57 AM by Ibrahim Malek Error 12170. Ibrahim Malek Aug 17, 2016 7:21 AM Dear Friendshere is my Prodi'm receiving Error 12170 while the TNSPING is working?everything was working fine but i've rebuild the DR after the Audit please received logging on advice the Bdump"alert_PROD.log" 158585 lines, 7928685 charactersWed Aug 17 09:51:38 2016Errors in file /oracle/prod/d01/db/tech_st/10.2.0/admin/PROD_srvhqon16/bdump/prod_arc4_28219.trc:ORA-12170: TNS:Connect timeout occurredPING[ARC4]: Heartbeat failed to connect to standby 'DR'. Error is 12170.Wed Aug 17 09:59:49 2016Error 12170 received logging on to the standbyWed Aug 17 09:59:49 2016Errors in file /oracle/prod/d01/db/tech_st/10.2.0/admin/PROD_srvhqon16/bdump/prod_arc4_28219.trc:ORA-12170: TNS:Connect timeout occurredPING[ARC4]: Heartbeat failed to connect to standby 'DR'. Error is 12170.Wed Aug 17 10:08:00 2016Error 12170 received logging on to the standbyWed Aug 17 10:08:00 2016Errors in file /oracle/prod/d01/db/tech_st/10.2.0/admin/PROD_srvhqon16/bdump/prod_arc4_28219.trc:ORA-12170: TNS:Connect timeout occurredPING[ARC4]: Heartbeat failed to connect to standby 'DR'. Error is 12170.TNSbash-3.2$ tnsping DRTNS Ping Utility for Solaris: Version 10.2.0.3.0 - Production on 17-AUG-2016 10:19:06Copyright (c) 1997, 2006, Oracle. All rights reserved.Used parameter files:/oracle/prod/d01/db/tech_st/10.2.0/network/admin/PROD_srvhqon16/sqlnet_ifile.oraUsed TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.2.18)(PORT=1526)) (CONNECT_DATA= (SID=PROD)))OK (0 msec) 152Views Tags: none (add) This content has bee
by the reviewers are theirs alone and may not reflect my opinion whether implied or not. None of the advice is warranted to be free of errors and ommision. Please use at your own risk and after thorough testing in your environment. Pages Home Collection of Some of My Very Popular Published Web Articles Friday, December 18, 2009 Resolving Gaps in Data Guard Apply Using Incremental RMAN BAckup Recently, we had a glitch on a Data Guard (physical standby database) on infrastructure. This is not a critical database; so the monitoring was relatively lax. And that being done by an outsourcer does not help it either. In any case, the laxness resulted in a failure remaining undetected for quite some time and it was eventually discovered only when the customer complained. This standby database is usually opened for read only access from time to time.This time, however, the customer saw that the data was significantly out of sync with primary and raised a red flag. Unfortunately, at this time it had become a rather political issue.Since the DBA in charge couldn't resolve the problem, I was called in. In this post, I will describe the issue and how it was resolved. In summary, there are two parts of the problem:(1) What happened(2) How to fix itWhat HappenedLet's look at the first question - what caused the standby to lag behind. First, I looked for the current SCN numbers of the primary and standby databases. On the primary:SQL> select current_scn from v$database;CURRENT_SCN----------- 1447102On the standby:SQL> select current_scn from v$database;CURRENT_SCN----------- 1301571Clearly there is a difference. But this by itself does not indicate a problem; since the standby is expected to lag behind the primary (this is an asynchronous non-real time apply setup). The real question is how much it is lagging in the terms of wall clock. To know that I used the scn_to_timestamp function to translate the SCN to a timestamp:SQL> select scn_to_timestamp(1447102) from dual;SC