My Oracle Support Banner

Windows: SQLNET.OUTBOUND_CONNECT_TIMEOUT Setting in SQLNET.ORA File Affects Database Service Start (Doc ID 2357153.1)

Last updated on OCTOBER 04, 2020

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Microsoft Windows x64 (64-bit)

Symptoms

On Windows platform, setting sqlnet.ora parameter SQLNET.OUTBOUND_CONNECT_TIMEOUT to a value larger than 0 may cause the database instance startup to hang when the instance is started from Windows Service.

Changes

Specifying sqlnet.ora parameter SQLNET.OUTBOUND_CONNECT_TIMEOUT to a non-zero value. 

eg.
SQLNET.OUTBOUND_CONNECT_TIMEOUT=3

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.