Extproc User Session Disconnects at SQLNET.INBOUND_CONNECT_TIMEOUT Value
(Doc ID 1356971.1)
Last updated on FEBRUARY 22, 2021
Applies to:
Oracle Net Services - Version 10.2.0.5 to 12.1.0.2 [Release 10.2 to 12.1]PL/SQL - Version 10.2.0.4 to 12.1.0.2 [Release 10.2 to 12.1]
Information in this document applies to any platform.
This issue occurs in environments where external procedure calls or extproc is running and the sqlnet.ora file contains a non-zero
value for SQLNET.INBOUND_CONNECT_TIMEOUT.
Symptoms
11g Specific Symptoms
Using legacy configuration for external procedure calls and a non-zero setting for SQLNET.INBOUND_CONNECT_TIMEOUT in the same environment , you may experience the following errors when the user session is idle for the value of the timeout:
HS: RPC error reported on server, SendExecCallout: ncrowht_what; NCR code 1004
ORA-28579: network error during callback from external procedure agent
Or:
ORA-6512: at "SYS.SHELL", line 1
ORA-6512: at line 1
10gR2 Specific Symptoms
Using typical configuration for external procedure calls and running a procedure at intervals that exceed the value for SQLNET.INBOUND_CONNECT_TIMEOUT and the procedure will crash intermittently with ORA-28576 error.
Changes
The following parameter may have been added recently to the sqlnet.ora file in the extproc environment:
SQLNET.INBOUND_CONNECT_TIMEOUT=n Where n is a non-zero value.
It is reproducible behavior that the user session will disconnect at the value of n.
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 |
Changes |
Cause |
Solution |
References |