Connection Timeout Between The Database & Connection Pooling (Doc ID 2295884.1)

Last updated on AUGUST 15, 2017

Applies to:

Oracle Argus Safety - Version 8.0.1 and later
Information in this document applies to any platform.

Goal

Question (s)

Oracle Argus Safety Version 8.0.1.
Occasionally users are unable to connect to the database and get error messages while logging into Argus.

For example:

Fatal NI connect error 12547, connecting to:
(LOCAL=NO)

 VERSION INFORMATION:
  TNS for Linux: Version 12.1.0.2.0 - Production
  Oracle Bequeath NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production
  TCP/IP NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production
 Time: 13-JUL-2017 01:52:34
 Tracing not turned on.
 Tns error struct:
  ns main err code: 12547

TNS-12547: TNS:lost contact
  ns secondary err code: 12560
  nt main err code: 0
  nt secondary err code: 0
  nt OS err code: 0
Thu Jul 13 01:52:35 2017
opiodr aborting process unknown ospid (1272) as a result of ORA-609


This is a generic error, it will occur when client fails to establish connection to database with in the default time due to network latency or some other issue.

Default time is 60 Seconds. We can increase this time by setting INBOUND_CONNECT_TIMEOUT parameter in sqlnet.ora and listener.ora files.

sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT =

listener.ora: INBOUND_CONNECT_TIMEOUT_ =


Would like to know if the above suggested change can be implemented to overcome the timeout issue.

Also we would like to know the concept of connection pooling in argus and are there any logs for it.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms