ORA-17629: 'Cannot connect to the remote database server' with RMAN

最新推荐文章于 2024-05-25 13:29:40 发布

cuhongyang4157

最新推荐文章于 2024-05-25 13:29:40 发布

阅读量852

点赞数

文章标签：数据库

[ID 1056174.1

修改时间: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

- 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 --&gt

INBOUND_CONNECT_TIMEOUT_ = 120

sqlnet.ora --&gt

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