ORA-17629: 'Cannot connect to the remote database server' with RMAN when related to SQLNET.INBOUND_CONNECT_TIMEOUT parameter
(Doc ID 1056174.1)
Last updated on JULY 30, 2024
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Net Services - Version 10.2.0.2 and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
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 <ORACLE_HOME>/diag/rdbms/<path>/<PATH>/trace/<PATH>_ora_1544224.trc:
ORA-17629: Cannot connect to the remote database server
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |