Home » Server Options » Data Guard » archive log can not send to the standby (10.2.0.1)
archive log can not send to the standby [message #543497] Wed, 15 February 2012 01:12 Go to next message
andy huang
Messages: 498
Registered: July 2011
Senior Member
Dear all,
The archive log can not 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 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
# 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: nothing to do (end)
*** 2012-02-15 08:03:14.537
kcrrwkx: nothing to do (start)
*** 2012-02-15 08:08:14.554
kcrrwkx: nothing to do (start)


kcrrwkx: nothing to do (start)
*** 2012-02-15 08:28:41.386
Redo shipping client performing standby login
*** 2012-02-15 08:31:50.650
OCIServerAttach failed -1
.. Detailed OCI error val is 12170 and errmsg is 'ORA-12170: TNS:Connect timeout occurred
'
*** 2012-02-15 08:31:50.663 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:31:50.678 60679 kcrr.c
PING[ARCq]: Heartbeat failed to connect to standby 'oraclbak'. Error is 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)

[Updated on: Wed, 15 February 2012 01:18] by Moderator

Report message to a moderator

Re: archive log can not send to the standby [message #543498 is a reply to message #543497] Wed, 15 February 2012 01:18 Go to previous messageGo to next message
Michel Cadot
Messages: 59291
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-12170: TNS:Connect timeout occurred
 *Cause:  The server shut down because connection establishment or
 communication with a client failed to complete within the allotted time
 interval. This may be a result of network or system delays; or this may
 indicate that a malicious client is trying to cause a Denial of Service
 attack on the server.
 *Action: If the error occurred because of a slow network or system,
 reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT,
 SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.
 If a malicious client is suspected, use the address in sqlnet.log to
 identify the source and restrict access. Note that logged addresses may
 not be reliable as they can be forged (e.g. in TCP/IP).

Regards
Michel
Re: archive log can not send to the standby [message #543499 is a reply to message #543498] Wed, 15 February 2012 01:27 Go to previous messageGo to next message
andy huang
Messages: 498
Registered: July 2011
Senior Member
Thanks,
Michel,the sqlnet.ora is nothing in the standby database.

[oracle@hxl01 admin]$ more sqlnet.ora
# sqlnet.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.

#SQLNET.AUTHENTICATION_SERVICES = (none)

Re: archive log can not send to the standby [message #543501 is a reply to message #543499] Wed, 15 February 2012 01:29 Go to previous messageGo to next message
andy huang
Messages: 498
Registered: July 2011
Senior Member
hi,
Michel,tnsing the standby database in the primary,there is no any problem.
[oracle@hxl admin]$ tnsping dup_oracl

TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 15-FEB-2012 09:16:39

Copyright (c) 1997, 2005, Oracle.  All rights reserved.

Used parameter files:


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.30.37)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = oraclbak)))
OK (80 msec)

Re: archive log can not send to the standby [message #543505 is a reply to message #543501] Wed, 15 February 2012 01:37 Go to previous messageGo to next message
John Watson
Messages: 4611
Registered: January 2010
Location: Global Village
Senior Member
You need to use the TNS service name in your log_archive_dest_2 parameter, not the database service name. It is all described in the Data Guard docs.
Re: archive log can not send to the standby [message #543506 is a reply to message #543501] Wed, 15 February 2012 01:42 Go to previous messageGo to next message
Michel Cadot
Messages: 59291
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
tnsping dup_oracl

Quote:
DUP_ORACL = ...(HOST = 192.168.30.37)...

Quote:
log_archive_dest_2= 'service=oraclbak

Quote:
Error 12170 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'oraclbak'


Regards
Michel
Re: archive log can not send to the standby [message #543509 is a reply to message #543505] Wed, 15 February 2012 01:46 Go to previous message
andy huang
Messages: 498
Registered: July 2011
Senior Member
Thanks John and Michel,
Just as your guide,the archive can send to the standby database.Thanks a lot!

alter system set log_archive_dest_2=
'service=dup_oracl async
valid_for=(online_logfiles,primary_role)
db_unique_name=oraclbak' scope=both;
Previous Topic: Copy BFILE
Next Topic: archive logs app issue
Goto Forum:
  


Current Time: Wed Oct 01 22:02:40 CDT 2014

Total time taken to generate the page: 0.10564 seconds