修改时间:2011-10-1类型:PROBLEM状态:PUBLISHED优先级:3

注释 (0)

In this Document

  Symptoms

  Cause

  Solution

  References

Applies to:

Oracle Net Services - Version: 10.2.0.1.0 to 11.2.0.3 - Release: 10.2 to 11.2

Information in this document applies to any platform.

Symptoms

- You may be using RMAN for duplication, etc. and receive the following error in the alert log or RMAN screen or log:

ORA-17629: Cannot connect to the remote database server

The full RMAN error may look like this:

Starting backup at 25-JAN-10

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=377 device type=DISK

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 01/25/2010 16:02:45

RMAN-03015: error occurred in stored script. Memory Script

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/25/2010 16:02:45

ORA-17629: Cannot connect to the remote database server

ORA-17629: Cannot connect to the remote database server

- The following would be the matching entry in the alert log:

Mon Jan 25 16:02:44 2010

Errors in file /ORCL/LIVE/livedb/11.1.0/admin/LIVE_orcl/diag/rdbms/live/LIVE/trace/LIVE_ora_1544224.trc:

ORA-17629: Cannot connect to the remote database server

Cause

With 10.2 and higher, the default or incorrect INBOUND_CONNECT_TIMEOUT (ICTO) settings can cause abnormal terminations of programs and tools, such as RMAN, prior to completing the authentication to the remote (target) Database.

This is supported by the engineer notes referencing ORA-12535, ORA-12170, and ORA-3136 errors that can occur with the incorrect ICTO values.

Solution

To ensure the error is not being generated by an incorrect ICTO value, add or edit the following lines in the respective files (do this on both sides, origin and target so the two communications are set the same):

listener.ora -->

INBOUND_CONNECT_TIMEOUT_ = 120

sqlnet.ora -->

SQLNET.INBOUND_CONNECT_TIMEOUT = 120

The listener(s) will need to be restarted after these changes as will RMAN scripts.

This will eliminate any premature inbound timeouts when RMAN is attempting to connect and run the script.

However, if the error continues, then SQL*Net tracing will be recommended to see where the abnormal connection failure is occurring.

References

 

相关内容

 

 

产品

 

Oracle Database Products > Oracle Database > Net Services > Oracle Net Services > SQL*Net > Generic networking issues or questions

 

错误

 

ORA-3136;ORA-17629;ORA-12535;ORA-12170;RMAN-3015;RMAN-3002;RMAN-3009;RMAN-569;RMAN-571

返回页首

Duplicate From Active Database Errors : ORA-17629 and ORA-17627: ORA-12154: Tns:Could Not Resolve The C [ID 1144273.1] 转到底部

修改时间:2011-10-11类型:PROBLEM状态:PUBLISHED优先级:3

注释 (0)

In this Document

  Symptoms

  Cause

  Solution

Applies to:

Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later   [Release: 11.2 and later ]

Information in this document applies to any platform.

Symptoms

The duplicate database from active failed with the following errors : 

ORA-17629: Cannot connect to the remote database server

ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified

ORA-17629: Cannot connect to the remote database server

Cause

For Active Duplication you need to connect to the target and Auxiliary DB using net service name ,even if you are running RMAN at the Auxiliary DB.

The net service name to connect to the Auxiliary DB should also be configured at the target Database.

In the tnsnames.ora on the machine of the TARGET database, there are 2 services created to connect to auxiliary database that have the same "service name" but different configuration.

Solution

1. To be sure that the tnsnames.ora file of each machine (machine where is the source database and machine where is the auxiliary database) has the service name to connect to auxiliary database.

2. Verify that there are not duplicate service_name with different configuration in the tnsnames.ora file.

As per the Step 2 of the below RMAN doc :

http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmdupdb.htm#i1008564

When duplicating from an active database, you must first have connected as SYSDBA to the auxiliary instance by means of a net service name. This net service name must also be available on the source database instance.

The source database instance, to which RMAN is connected as TARGET, uses this net service name to connect directly to the auxiliary database instance.

Double check using the following commands on the TARGET and AUXILIARY

% tnsping

% tnsping

Once this is executed for the TARGET and AUXILIARY, it should return the same 'connect' information.

 

相关内容

 

 

产品

 

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition > Recovery Manager > Duplicating existing databases

 

关键字

 

12154;AUXILIARY;DUPLICATE DATABASE;SERVICE_NAME;TNSNAMES.ORA

 

错误

 

ORA-17627;ORA-12154;ORA-17629

返回页首