SQLNET.INBOUND_CONNECT_TIMEOUT Causes DG4ODBC To Fail With ORA-28511 Or ORA-600 [opidsa-2]
(Doc ID 549095.1)
Last updated on AUGUST 02, 2024
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
When using the SQLNET INBOUND_CONNECT_TIMEOUT parameter (in the listener.ora and sqlnet.ora), the established connection with an HS-Agent (HSODBC in version 10 and Database Gateway for ODBC (DG4ODBC) in version 11) is broken by SQL*Net after this time has expired.
The session in which the database link to the gateway has been opened will get an ORA-28511 when trying to run the next SQL-statement:
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 |