WARNING: inbound connection timed out (ORA-3136)
                                                 Last update (2012-06-19 10:15:03)
                                                                                                                   Date added (2012-06-19 10:00:28)

Summary
In the alert log of an Oracle10g database i get errors like:
WARNING: inbound connection timed out (ORA-3136)
Tue Jun 19 07:56:46 2012
WARNING: inbound connection timed out (ORA-3136)
Tue Jun 19 08:02:14 2012
WARNING: inbound connection timed out (ORA-3136)
Tue Jun 19 08:03:51 2012
WARNING: inbound connection timed out (ORA-3136)
The most common root cause of "WARNING: inbound connection timed out (ORA-3136)" is
ORA-01017 invalid username /password

Some users from their client (sqlplus, toad, etc) are trying to connect to the database but after wrong username/password, they leave the client application open.

After x seconds (set at parameter INBOUND_CONNECT_TIMEOUT at listener.ora or
SQLNET.INBOUND_CONNECT_TIMEOUT at sqlnet.ora) the message:
WARNING: inbound connection timed out (ORA-3136) appears in the alert.log

Workaround: Set at sqlnet.ora SQLNET.INBOUND_CONNECT_TIMEOUT=0
This means it will wait indefinite to alert the warning.
Reviews
Categories
Oracle DBA-> (147)
  Alertlog (3)
  Archivelog (5)
  Auditing (1)
  Backup - Recovery (19)
  Database files (6)
  Database options (2)
  DB links (2)
  Dependencies (1)
  Dictionary (2)
  Exp-Imp Datapump (6)
  Jobs (2)
  Mview (2)
  Networking (3)
  Objects (7)
  Parameters (2)
  Redologs (6)
  Roles - Grants (2)
  Rollback - Undo (8)
  Segments (3)
  Sequences (2)
  Sessions (14)
  SGA (14)
  Tables (10)
  Tablespaces (10)
  Temp (4)
  Toad (5)
  Transactions (1)
  Upgrade (2)
  Users (3)
Oracle APPS DBA-> (66)
Exadata (1)
Performance Tuning-> (59)
Oracle Real Cases (24)
Oracle Errors (23)
Oracle SQL tricks (32)
Oracle RAC (3)
Oracle Security (8)
Filters
Search