Error 12560 Received Logging On To The Standby
Contents |
to friend Error with shipping redo log from primary to standby [message #601350] Tue, 19 November 2013 20:56 trantuananh24hg Messages: 666Registered: January 2007 Location: Ha Noi, Viet Nam error 12154 received logging on to the standby Senior Member Good morning! I've got error yesterday. Let me describe: I error 12154 received logging on to the standby 11g configure DG successfully at 15/10/2013, both of them are Oracle 11gr2, ASM, RHEL 5 (single), they are fine till error 12154 received logging on to the standby rac 19/11/2013 when system administrator change the IP of primary. So, I got error shipping redo log from primary to standby. P/S: Because of long brief, so I device into 2 post. I'm error 1031 received logging on to the standby sorry for inconvenience Primary (RHEL 5.5, Oracle 11gr2 Grid Infrastructure, Enterprise) Error: Log Transport Services Error 2 1066 12504 YES 20-NOV-13 PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504. Log Transport Services Error 0 1067 12504 YES 20-NOV-13 Error 12504 received logging on to the standby Log Transport Services Error 2 1068 12504 YES 20-NOV-13 PING[ARC1]: Heartbeat failed to connect
Error 1031 Received Logging On To The Standby Ora-01031 Insufficient Privileges
to standby 'wbstdby'. Error is 12504. Log Transport Services Error 0 1069 12504 YES 20-NOV-13 Error 12504 received logging on to the standby Log Transport Services Error 2 1070 12504 YES 20-NOV-13 PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504. - error log file * alert log file: Fatal NI connect error 12541, connecting to: (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=)(CID=(PROGRAM=oracle)(HOST=webcharge)(USER=oracle)))(ADDRESS=(PROTOCOL=TCP)(HOST=10.54.5. 177)(PORT=1521))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.1.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production Time: 19-NOV-2013 01:16:44 Tracing not turned on. Tns error struct: ns main err code: 12541 TNS-12541: TNS:no listener ns secondary err code: 12560 nt main err code: 511 TNS-12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 TNS-00511: No listener nt secondary err code: 111 nt OS err code: 0 Error 12541 received logging on to the standby Check whether the listener is up and running. Errors in file /webcharge/app/oracle/diag/rdbms/webcharge/webcharge/trace/webcharge_arc1_4980.trc: ORA-12541: TNS:no listener PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12541. * dump file [oracle@webcharge trace]$ more /webcharge/app/oracle/diag/rdbms/webcharge/webcharge/trace/webcharge_arc1_4980.trc Trace file /webcharge/app/or
machine primary and standby have below
Error 1033 Received Logging On To The Standby
issuesoracle 11g (both primary and standby on same windows machine error 12514 received logging on to the standby different drives)I followed steps as1)installed 2 oracle on same machine different drives2)for instance to error 12514 received logging on to the standby oracle be used as standby (drop database)3)from primary sent datafiles,standby controlfile,init file to standby location/directoriesmodified init file for standby,rename datafiles4)at primary modified init file5)modified listener http://www.orafaq.com/forum/t/190397/ and tnsnames.ora files for both primary and seconday6)created password file and copied same to oracle_home/database both primary and secondary7 open primary andfor standby:startup nomount alter database mount standby database;alter database recover managed standby database disconnect from session;8 it work without any issue but recovery not taking place below error http://dbaforums.org/oracle/lofiversion/index.php?t19731.html in alert of primaryORA-01031: insufficient privilegesPING[ARC1]: Heartbeat failed to connect to standby 'FC_LOCALTES'. Error is 1031.1)on standby v$instance showing output database role as primary for standby database(is it ok or v$instance on standby database should show database role as standby)please let me know where i am going wrongalert log primary:Starting ORACLE instance (normal)LICENSE_MAX_SESSION = 0LICENSE_SESSIONS_WARNING = 0Picked latch-free SCN scheme 2Autotune of undo retention is turned on. IMODE=BRILAT =18LICENSE_MAX_USERS = 0SYS auditing is disabledStarting up ORACLE RDBMS Version: 11.1.0.6.0.Using parameter settings in server-side spfile D:\APP\mydir\PRODUCT\11.1.0\DB_1\DATABASE\SPFILELOCALTES.ORASystem parameters with non-default values:processes = 150memory_target = 756Mcontrol_files = "D:\APP\mydir\ORADATA\LOCALTES\CONTROL01.CTL"control_files = "D:\APP\mydir\ORADATA\LOCALTES\CONTROL02.CTL"control_files = "D:\APP\mydir\ORADATA\LOCALTES\CONTROL03.CTL"db_block_size = 8192compatible = "11.1.0.0.0"_log_archive_callout = "LOCAL_FIRST=true"log_archive_dest_1 = "LOCATION=USE_DB_RECOVERY_FILE_DEST ARCH MANDATORY REOPEN=5 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)"log_archive_dest_2 = "SERVICE=FC_LOCALTES reopen=60 ARCH NOAFFIRM"log_archive_dest_state_1 = "ENABLE"log_archive_dest_state_2 = "ENABLE"standby_archive_dest = "c:\standby_arch"fal_client = "FC_LOCALTES"fal_server = "FS_LOCALTES"archive_lag_target = 1800db_recovery_file_dest = "D:\app\mydir\flash_recovery_area"db_recovery_file_dest_size= 2Gstandby_file_management = "AUTO"undo_tablespace = "UNDOTBS1"remote_login_passwordfile= "EXCLUSIVE"db_domain = ""dispatchers = "(PROTOCOL=TCP) (SERVICE=localtesXDB)"audit_file_dest = "D:\APP\mydir\ADMIN\LOCALTEST\A
standby 'STBYKOL'. Error is 1034) Hi Guys, Here is an Interesting case and I was stuck with the problem since https://viewssharings.blogspot.com/2014/03/troubleshooting-error-1017-received.html last 2 days and a half. In fact I was almost done https://davidalejomarcos.wordpress.com/2011/01/18/removing-fatal-ni-connect-error-xxxx-from-your-alert-log/ with everything to resolve the mentioned problem but I could not able to solve almost. Then I left it as I became exhausted, But I kept on thinking Where could be the problem, at last I got it. Here was my case: -------------------- I received logging have 2 node rac as primary and a standby was intended to create on single node. I changed parameter file, created passwords, tns entries accordingly. Then I did duplicate target and restored database as standby. After doing everything I saw, RAC node1 was able to send archive logs to dest_2 which is my standby but received logging on unfortunately node2 was unable to enter into standy database. Here are Problem Statement: ---------------------------- Standby was receiving node1's log files but node2 was unable to send logfiles due to the below error 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. Steps for diagnosing ---------------------------- step-1 when I checked query on node 2 sql>select DEST_ID,DEST_NAME,STATUS,BINDING,ERROR from v$ARCHIVE_DEST where status<>'INACTIVE'; all log file location were valid Sql> SELECT DESTINATION, STATUS, ERROR FROM V$ARCHIVE_DEST WHERE DEST_ID=2; dest2 for archive log dest is valid sql> select error_code,message from v$dataguard_status; Error 1034 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'STBYDB'. Error is 1034. Then I have done the below steps to resolve the problem 1.) alter system set log_archive_dest_state_2=defer scope=both sid='*'; (on primary RAC any node ) Sql>recover managed standby database cancel; (o
have a script to monitor the alert.log file for any ORA-xxxx errors. With 11g we found out many entries in regards of: Fatal NI connect error The problem: alert.log file has many entries for Fatal NI connect error. Examples: *********************************************************************** Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=xxxx)(PORT=nnn))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=sss)(CID=(PROGRAM=oracle)(HOST=xxx)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 17-JAN-2011 10:20:45 Tracing not turned on. Tns error struct: ns main err code: 12564 TNS-12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Error 12514 received logging on to the standby Mon Jan 17 10:21:45 2011 *********************************************************************** or *********************************************************************** Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version 11.2.0.2.0 - Production Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production Time: 18-JAN-2011 15:13:08 Tracing not turned on. Tns error struct: ns main err code: 12535 TNS-12535: TNS:operation timed out ns secondary err code: 12560 nt main err code: 505 TNS-00505: Operation timed out nt secondary err code: 110 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=xx.xx.x.xx)(PORT=nnnn)) Tue Jan 18 15:40:20 2011 The solution: We will have an entry on the alert.log file every time a client connection of any kind fails to complete or is aborted. One way to minimize the impact is by using the parameter SQLNET.INBOUND_CONNECT_TIMEOUT (default to 60 seconds on 10gR2 and 11g) but, sometimes, this value is not adequate. Oracle also mentions the occurrence of this error if you use DB Console or Enterprise Manager to monitor your databases and the emagent will try to connect to the target database repeatedly and, statistically, some will fail (frequency will depend on how busy your system is). Most of the time (certainly for DB Console and Enterprise Manager Agent) the application will try to connect again and it will succeed. To fix the problem you could increase the v