Monday, March 9, 2015

Sqlnet listener tracing



Use TRCASST to read the files generated

following should be in sqlnet.ora file (sqlnet trace)

TRACE_UNIQUE_CLIENT = on

NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

TRACE_DIRECTORY_CLIENT = /opt/app/oracle/product/10.2.0.5/network/log

TRACE_LEVEL_SERVER = 16

TRACE_FILE_SERVER = sql_trace.trc

TRACE_DIRECTORY_SERVER = /opt/app/oracle/product/10.2.0.5/network/trace/

TRACE_TIMESTAMP_CLIENT = ON


***************************************************************************************************************
following should be in listener.ora file (listener trace)

TRACE_FILE_LISTENER = LISTENERTEST.trc
TRACE_DIRECTORY_LISTENER = /opt/app/crs/11.2.0/11.2.0.3/network/trace/
LOGGING_LISTENER = on
TRACE_LEVEL_LISTENER =SUPPORT
TRACE_LEVEL_LISTENER =ADMIN


/opt/app/oracle/product/11.2.0/11.2.0.4/network/trace


*********************************************************************************

How does this client connect to oracle -- is it using thin jdbc or sqlnet?

If this client is using sqlnet, I need to see a client side trace that shows the client connection attempt failing. Client side tracing is turned on by adding the following syntax to the client's sqlnet.ora file:

TRACE_LEVEL_CLIENT = 16
TRACE_DIRECTORY_CLIENT = Some fully qualified directory likeC:\TEMP
TRACE_FILE_CLIENT = CLIENT
DIAG_ADR_ENABLED= OFF

Try to connect. The connection will still fail upload the resulting client side trace to the SR. 

No comments:

Post a Comment

Featured Post

Apply Patch 22191577 latest GI PSU to RAC and DB homes using Opatch auto or manual steps

Patch 22191577: GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.4.160119 (JAN2016) Unzip the patch 22191577 Unzip latest Opatch Version in or...