Wednesday, October 11, 2006

INBOUND_CONNECT_TIMEOUT

Untuk yang menggunakan Oracle 10g R2, mungkin pernah mengalami hal dimana kita dapat dengan sukses connect menggunakan SQL*Plus, namun pada saat mencoba menjalankan aplikasi, kita kadang bisa connect kedatabase atau sama sekali tidak bisa terhubung dengan database.

Berikut ini mungkin bisa membantu mengatasi masalah anda.
  1. Set INBOUND_CONNECT_TIMEOUT_listener_name = 0 pada listener.ora
  2. Set SQLNET.INBOUND_CONNECT_TIMEOUT = 0 pada sqlnet.ora pada server
  3. Stop dan start database beserta dengan listernernya
  4. Test kembali aplikasi anda, apakah sudah berhasil connect ke database
Untuk melihat apakah nilai INBOUND_CONNECT_TIMEOUT pada listernet sudah berubah bisa dengan menggunakan:

LSNRCTL> show inbound_connect_timeout
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.9.11)(PORT=1521)))
LISTENER parameter "inbound_connect_timeout" set to 0
The command completed successfully

Berikut ada potongan dari keterangan error yang berhasil di kumpulkan.

-- alert.log pada database server
Wed Oct 11 16:42:35 2006
WARNING: inbound connection timed out (ORA-3136)
Wed Oct 11 16:43:25 2006
WARNING: inbound connection timed out (ORA-3136)
Wed Oct 11 16:48:32 2006
WARNING: inbound connection timed out (ORA-3136)
Wed Oct 11 16:54:20 2006
WARNING: inbound connection timed out (ORA-3136)


-- sqlnet.log pada aplikasi yg dijalankan
Fatal OSN connect error 12637, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=
(COMMUNITY=tcp.dbprod)(PROTOCOL=TCP)
(Host=server01)(Port=1521))(ADDRESS=
(COMMUNITY=tcp.dbprod)(PROTOCOL=TCP)
(Host=server01)(Port=1526)))(CONNECT_DATA=(SID=dbprod)
(CID=(PROGRAM=NETERP.exe)(HOST=WINXP_PC01)(USER=dede))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 2.3.4.0.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows:
Version 2.3.4.0.0 - Production
Time: 11-OCT-06 16:52:58
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: TNS:received a TNS error during navigation
ns main err code: 12637
TNS-12637: Packet receive failed
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0


***********************************************************************
Fatal OSN connect error 12547, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=
(PROTOCOL=BEQ)(PROGRAM=oracle80)(ARGV0=oracle80ORCL)
(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=
(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=ORCL)
(CID=(PROGRAM=NETERP.exe)(HOST=WINXP_PC01)(USER=dede))))

VERSION INFORMATION:
TNS for 32-bit Windows: Version 2.3.4.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows:
Version 2.3.4.0.0 - Production
Time: 11-OCT-06 16:52:58
Tracing not turned on.
Tns error struct:
nr err code: 12206
TNS-12206: TNS:received a TNS error during navigation
ns main err code: 12547
TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 517
TNS-00517: Lost contact
nt secondary err code: 0
nt OS err code: 0
SQLNET.INBOUND_CONNECT_TIMEOUT

Purpose
Use the SQLNET.INBOUND_CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information.

If the client fails to establish a connection and complete authentication in the time specified, then the database server terminates the connection. In addition, the database server logs the IP address of the client and an ORA-12170: TNS:Connect timeout occurred error message to the sqlnet.log file. The client receives either an ORA-12547: TNS:lost contact or an ORA-12637: Packet receive failed error message.

. Without this parameter, a client connection to the database server can stay open indefinitely without authentication. Connections without authentication can introduce possible denial-of-service attacks, whereby malicious clients attempt to flood database servers with connect requests that consume resources.

To protect both the database server and the listener, Oracle Corporation recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying values for these parameters, consider the following recommendations:

Set both parameters to an initial low value.
Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter.
For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed.

See Also:
Oracle9i Net Services Administrator's Guide for information about configuring these parameters

Default
None

Example
SQLNET.INBOUND_CONNECT_TIMEOUT=3

Others Resources:
  1. Oracle 10g - Troubleshooting Oracle Net Services
  2. http://www.orafaq.com/forum/t/56763/0/
  3. oracle/manual-10gR2/network.102/b14212/

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home