Parameter OUTBOUND_CONNECT_TIMEOUT in SQLNET.ORA
(Doc ID 519391.1)
Last updated on APRIL 18, 2025
Applies to:
Siebel System Software - Version 7.8.2.3 [19221] and laterz*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221]
Database: Oracle 10.2.0.1
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 10
This document was previously published as Siebel SR 38-3364749281.
Symptoms
Our Production System Database Server is hitting Oracle Bug # 5578157.
When there is a network interruption and the Database cannot ship redo logs to the Standby Servers, after a few retries it consumes the message queue and crashes with ORA-600 error message.
The Bug will be fixed in Oracle 10.2.0.4 Patch Set, which is not yet available.
We did request for a Backport Interim Patch for Oracle 10.2.0.3 Patch Set on Sun Solaris platform, but it was rejected by Oracle Development due to some architectural considerations.
Oracle has suggested us to set the following parameter as a workaround.
Please kindly check whether it is safe to set this parameter.
Parameter: OUTBOUND_CONNECT_TIMEOUT (in SQLNET.ORA)
Value: 20
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 |