Experience: is what you get soon after you need it.

Experience: is what you get soon after you need it.

****************Got the opportunity to pen a Book on Database Cloud Services.......More details to follow.***************

Title : Database Cloud Revealed
Publisher : Apress
Release Date : Jan-2020

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


Rasul Allah (sal Allahu alaihi wa sallam) said: "Restore the trusts of those who trust you, and deal not falsely with him who deals falsely with you." [Abu Dawud, Tirmidhi]


My Cloud Certifications:

AWS Certified Solutions Architect Associate

Azure Certified Administrator

Oracle Cloud Infrastructure 2018 Certified Architect Associate.

Oracle Cloud Infrastructure Classic 2018 Certified Architect Associate.

Oracle Database Cloud Administrator Certified Professional.

Oracle Database Cloud Service Operations Certified Associate.

Search This Blog

Wednesday, September 16, 2015

Oracle Network Tracing

ocm11g : Setup netowrk Tracing
 
How to set up network tracing for Oracle Listener/SQLNET

  1. Setup listener Trace
  2. Setup sqlnet.ora trace
  3. Different Trace Levels


ADR Dir for listener:

[oracle@collabn1 trace]$ pwd
/u01/app/oracle/diag/tnslsnr/collabn1/shaikdb/trace



Subdirectory Name
Contents
alert
The XML-formatted log named log.xml
cdump
Core files
incident
Multiple subdirectories, where each subdirectory is named for a particular incident, and where each contains dumps pertaining only to that incident
trace
Background and server process trace files, SQL trace files, and text version of the log.xml file in the alert directory
(others)
Other subdirectories of ADR home, which store incident packages, health monitor reports, and other information


[oracle@collabn1 trace]$ vi shaikdb.log

Sun Sep 13 12:19:29 2015
Create Relation ADR_CONTROL
Create Relation ADR_INVALIDATION
Create Relation INC_METER_IMPT_DEF
Create Relation INC_METER_PK_IMPTS
System parameter file is /u01/app/oracle/product/11.2.0.2/SHAIKPROD/network/admin/listener.ora
Log messages written to /u01/app/oracle/diag/tnslsnr/collabn1/shaikdb/alert/log.xml
Trace information written to /u01/app/oracle/diag/tnslsnr/collabn1/shaikdb/trace/ora_13146_139713732392704.trc
Trace level is currently 0

Started with pid=13146
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=collabn1.shaiksameer)(PORT=1522)))
Listener completed notification to CRS on start



sqlnet.ora File Diagnostic Parameter Comparison


Parameter
DIAG_ADR_ENABLED=OFF
DIAG_ADR_ENABLED=ON
ADR_BASE
Disabled
Enabled
TRACE_LEVEL_CLIENT
Enabled
Enabled
TRACE_LEVEL_SERVER
Enabled
Enabled
TRACE_DIRECTORY_CLIENT
Enabled
Disabled
TRACE_FILE_CLIENT
Enabled
Disabled
TRACE_UNIQUE_CLIENT
Enabled
Disabled
LOG_DIRECTORY_CLIENT
Enabled
Disabled
LOG_FILE_CLIENT
Enabled
Disabled
LOG_DIRECTORY_SERVER
Enabled
Disabled
TRACE_DIRECTORY_SERVER
Enabled
Disabled
TRACE_FILE_SERVER
Enabled
Disabled



listener.ora File Diagnostic Parameter Comparison


Parameter
DIAG_ADR_ENABLED=OFF
DIAG_ADR_ENABLED=ON
ADR_BASE_listener_name
Disabled
Enabled
LOGGING_listener_name
Enabled
Enabled
TRACE_LEVEL_listener_name
Enabled
Enabled
TRACE_TIMESTAMP_listener_name
Enabled
Enabled
LOG_DIRECTORY_CLIENT_listener_name
Enabled
Disabled
LOG_FILE_CLIENT_listener_name
Enabled
Disabled
TRACE_DIRECTORY_CLIENT_listener_name
Enabled
Disabled
TRACE_FILELEN_listener_name
Enabled
Disabled
TRACE_FILENO_listener_name
Enabled
Disabled



cman.ora File Diagnostic Parameter Comparison


Parameter
DIAG_ADR_ENABLED=OFF
DIAG_ADR_ENABLED=ON
ADR_BASE
Disabled
Enabled
LOG_LEVEL
Enabled
Enabled
TRACE_LEVEL
Enabled
Enabled
TRACE_TIMESTAMP
Enabled
Enabled
LOG_DIRECTORY
Enabled
Disabled
TRACE_DIRECTORY
Enabled
Disabled
TRACE_FILELEN
Enabled
Disabled
TRACE_FILENO
Enabled
Disabled



To view trace files using ADRCI, enter ADRCI at a command line.

Client Side
adrci>> SHOW ALERT
adrci>> SHOW BASE -product client
adrci>> SET BASE -product client
adrci>> SHOW TRACEFILE
adrci>> SHOW TRACE trace_file.trc
adrci>> SHOW SPOOL
In the preceding commands, SHOW ALERT will show the log.xml file in a text editor, such as VI. SHOW BASE -product client displays the value of ADR_BASE for the client. Use that value for client in the SET BASE command.
The following are common ADRCI commands to check a server:
Server Side
adrci>> SHOW BASE
adrci>> SHOW TRACEFILE
adrci>> SHOW TRACE trace_file.trc


Demo:

[oracle@collabn1 trace]$ adrci

ADRCI: Release 11.2.0.1.0 - Production on Mon Sep 14 09:40:27 2015

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

ADR base = "/u01/app/oracle"
adrci> show alert

ADR Home = /u01/app/oracle/diag/tnslsnr/collabn1/shaikdb:
*************************************************************************
Output the results to file: /tmp/alert_24020_1406_shaikdb_1.ado



adrci> help

HELP [topic]
  Available Topics:
       CREATE REPORT
       ECHO
       EXIT
       HELP
       HOST
       IPS
       PURGE
       RUN
       SET BASE
       SET BROWSER
       SET CONTROL
       SET ECHO
       SET EDITOR
       SET HOMES | HOME | HOMEPATH
       SET TERMOUT
       SHOW ALERT
       SHOW BASE
       SHOW CONTROL
       SHOW HM_RUN
       SHOW HOMES | HOME | HOMEPATH
       SHOW INCDIR
       SHOW INCIDENT
       SHOW PROBLEM
       SHOW REPORT
       SHOW TRACEFILE
       SPOOL

There are other commands intended to be used directly by Oracle, type
"HELP EXTENDED" to see the list


adrci> show problem

ADR Home = /u01/app/oracle/diag/tnslsnr/collabn1/shaikdb:
*************************************************************************
0 rows fetched


On Linux and UNIX platforms you can use the ADAPTERS utility to verify protocol support. On the database server, run the following command from the ORACLE_HOME/bin director


[oracle@collabn1 trace]$ adapters

Installed Oracle Net transport protocols are:

    IPC
    BEQ
    TCP/IP
    SSL
    RAW
    SDP/IB

Installed Oracle Net naming methods are:

    Local Naming (tnsnames.ora)
    Oracle Directory Naming
    Oracle Host Naming
  Error!!!   Oracle Names Server Naming is not completely installed!

Installed Oracle Advanced Security options are:

    RC4 40-bit encryption
    RC4 56-bit encryption
    RC4 128-bit encryption
    RC4 256-bit encryption
    DES40 40-bit encryption
    DES 56-bit encryption
    3DES 112-bit encryption
    3DES 168-bit encryption
    AES 128-bit encryption
    AES 192-bit encryption
    AES 256-bit encryption
    MD5 crypto-checksumming
    SHA-1 crypto-checksumming
    Kerberos v5 authentication
    RADIUS authentication




sqlnet.ora Parameter
Oracle Net Manager Field
ADR_BASE
You must set this parameter manually.
DIAG_ADR_ENABLED
You must set this parameter manually.
LOG_DIRECTORY_CLIENT
Client Information: Log Directory
LOG_DIRECTORY_SERVER
Server Information: Log Directory
LOG_FILE_CLIENT
Client Information: Log File
LOG_FILE_SERVER
You must set this parameter manually.



listener.ora Parameter
Oracle Net Manager Field
ADR_BASE_listener_name
You must set this parameter manually.
DIAG_ADR_ENABLED_listener_name
You must set this parameter manually.
LOG_DIRECTORY_listener_name
LOG_FILE_listener_name
Log File



cman.ora Parameter
Description
ADR_BASE
The ADR_BASE parameter specifies the base directory for storing tracing and logging incidents.
Use this parameter when DIAG_ADR_ENABLED is set to ON.
DIAG_ADR_ENABLED
The DIAG_ADR_ENABLED parameter indicates whether ADR tracing is enabled.
When the DIAG_ADR_ENABLED parameter is set to OFF, non-ADR file tracing is used.
EVENT_GROUP
The event groups that are logged. Multiple events may be designated using a comma-delimited list. This parameter accepts the following values:
INIT_AND_TERM: initialization and termination MEMORY_OPS: memory operations CONN_HDLG: connection handling PROC_MGMT: process management REG_AND_LOAD: registration and load update WAKE_UP: events related to CMADMIN wakeup queue TIMER: gateway time outs CMD_PROC: command processing RELAY: events associated with connection control blocks
LOG_DIRECTORY
The destination directory for log files.
By default, the directory is ORACLE_HOME/network/log.
This parameter is disabled when ADR_ENABLED is on.
LOG_LEVEL
The level of logging. Four levels are supported:
off (default): no logging user: user log information admin: administrative log information support: Oracle Support Services information

Setting Logging During Control Utilities Run Time

You can set logging during control utility run time. Setting logging with a control utility does not set parameters in the *.ora files, and the setting is only valid for the control utility session.
The following settings can be set for a control utility:
  • For a listener, use the SET LOG_FILE and SET LOG_DIRECTORY commands from the Listener Control utility.
  • For an Oracle Connection Manager, use the SET LOG_DIRECTORY, SET LOG_LEVEL, and SET EVENT commands from the Oracle Connection Manager control utility.




sqlnet.ora Parameter
Oracle Net Manager Field
Description
ADR_BASE
You must set this parameter manually.
The ADR_BASE parameter specifies the base directory for storing tracing and logging incidents.
Use this parameter when DIAG_ADR_ENABLED is set to ON.
DIAG_ADR_ENABLED
You must set this parameter manually.
The DIAG_ADR_ENABLED parameter indicates whether ADR tracing is enabled.
When the DIAG_ADR_ENABLED parameter is set to OFF, non-ADR file tracing is used.
LOG_DIRECTORY_CLIENT
Client Information: Log Directory
The destination directory for the client log file. By default, the client directory is the current working directory. This parameter is disabled when ADR_ENABLED is on.
LOG_DIRECTORY_SERVER
Server Information: Log Directory
The destination directory for the database server log files. By default the server directory is ORACLE_HOME/network/log. This parameter is disabled when ADR_ENABLED is on.
LOG_FILE_CLIENT
Client Information: Log File
The name of the log file for the client. By default the log name is sqlnet.log.
LOG_FILE_SERVER
You must set this parameter manually.
The name of the log file for the database server. By default the log name is sqlnet.log.
TRACE_DIRECTORY_CLIENT
Client Information: Trace Directory
The destination directory for the client trace output. By default, the client directory is ORACLE_HOME/network/trace.
TRACE_DIRECTORY_SERVER
Server Information: Trace Directory
The destination directory for the database server trace output. By default, the server directory is ORACLE_HOME/network/trace.
TRACE_FILE_CLIENT
Client Information: Trace File
The name of the trace file for the client. By default, the trace file name is sqlnet.trc.
TRACE_FILE_SERVER
Server Information: Trace File
The name of the trace file for the database server. By default the trace file name is svr_pid.trc.
TRACE_FILELEN_CLIENT
You must set this parameter manually.
The size of the client trace files in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_CLIENT parameter.
TRACE_FILELEN_SERVER
You must set this parameter manually.
The size of the database server trace files in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_SERVER parameter.
TRACE_FILENO_CLIENT
You must set this parameter manually.
The number of trace files for client tracing. When this parameter is set along with the TRACE_FILELEN_CLIENT parameter, trace files are used in a cyclical fashion. The first file is filled, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of sqlnet.trc is used, and this parameter is set to 3, then the trace files would be named sqlnet1_pid.trc, sqlnet2_pid.trc and sqlnet3_pid.trc.
In addition, trace events in the trace files are preceded by the sequence number of the file.
TRACE_FILENO_SERVER
You must set this parameter manually.
The number of trace files for database server tracing. When this parameter is set along with the TRACE_FILELEN_SERVER parameter, trace files are used in a cyclical fashion. The first file is filled, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of svr_pid.trc is used, and this parameter is set to 3, then the trace files would be named svr1_pid.trc, svr2_pid.trc and svr3_pid.trc.
In addition, trace events in the trace files are preceded by the sequence number of the file.
TRACE_LEVEL_CLIENT
Client Information: Trace Level
The level of detail the trace facility records for the client.
The trace level value can either be a value within the range of 0 (zero) to 16 where 0 is no tracing and 16 represents the maximum amount of tracing) or one of the following values:
off (equivalent to 0) provides no tracing. user (equivalent to 4) traces to identify user-induced error conditions. admin (equivalent to 6) traces to identify installation-specific problems. support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services.
TRACE_LEVEL_SERVER
Server Information: Trace Level
The level of detail the trace facility records for the database server. The trace level value can either be a value within the range of 0 (zero) to 16 where 0 is no tracing and 16 represents the maximum amount of tracing) or one of the following values:
off (equivalent to 0) provides no tracing. user (equivalent to 4) traces to identify user-induced error conditions. admin (equivalent to 6) traces to identify installation-specific problems. support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services.
TRACE_TIMESTAMP_CLIENT
You must set this parameter manually.
A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for every trace event in the client trace file, sqlnet.trc.
TRACE_TIMESTAMP_SERVER
You must set this parameter manually.
A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for every trace event in the client trace file, sqlnet.trc.
TRACE_UNIQUE_CLIENT
Client Information: Unique Trace File Name
The value is set to on, Oracle Net creates a unique file name for each trace session by appending a process identifier to the name of each trace file generated, and enabling several files to coexist. For example, trace files named sqlnetpid.trc are created if default trace file name sqlnet.trc is used. When the value is set to off, data from a new client trace session overwrites the existing file.




TNSPING Trace Parameters

sqlnet.ora Parameter
Description
TNSPING.TRACE_DIRECTORY
The destination directory for TNSPING trace file, tnsping.trc. By default, the directory is ORACLE_HOME/network/trace.
TNSPING.TRACE_LEVEL
The level of detail the trace facility records for the TNSPING utility. The trace level value can either be a value within the range of 0 (zero) to 16 where 0 is no tracing and 16 represents the maximum amount of tracing) or one of the following values:
off (equivalent to 0) provides no tracing. user (equivalent to 4) traces to identify user-induced error conditions. admin (equivalent to 6) traces to identify installation-specific problems. support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services.



listener.ora Parameter
Oracle Net Manager Field
Description
ADR_BASE_listener_name
You must set this parameter manually.
The ADR_BASE_listener_name parameter specifies the base directory for storing which tracing and logging incidents.
Use when DIAG_ADR_ENABLED_listener_name is set to ON.
DIAG_ADR_ENABLED_listener_name
You must set this parameter manually.
The DIAG_ADR_ENABLED_listener_name parameter indicates whether ADR tracing is enabled.
When DIAG_ADR_ENABLED_listener_name is set to OFF, non-ADR file tracing is used.
LOG_DIRECTORY_listener_name
LOG_FILE_listener_name
Log File
The destination directory and file for the log file that is automatically generated for listener events. By default the directory is ORACLE_HOME/network/log, and the file name is
listener.ora Parameter
Oracle Enterprise Manager/Oracle Net Manager Field
Description
TRACE_LEVEL_listener_name
Select a trace level/Trace Level
The level of detail the trace facility records for the listener. The trace level value can either be a value within the range of 0 (zero) to 16 where 0 is no tracing and 16 represents the maximum amount of tracing) or one of the following values:
off (equivalent to 0) provides no tracing. user (equivalent to 4) traces to identify user-induced error conditions. admin (equivalent to 6) traces to identify installation-specific problems. support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services.
TRACE_DIRECTORY_listener_name
TRACE_FILE_listener_name
Trace File
The destination directory and file for the trace file. By default the directory is ORACLE_HOME/network/trace, and the file name is listener.trc.
TRACE_FILELEN_listener_name
You must set this parameter manually.
The size of the listener trace files in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter
TRACE_FILENO_listener_name
You must set this parameter manually.
The number of trace files for listener tracing. When this parameter is set along with the TRACE_FILELEN_listener_name parameter, trace files are used in a cyclical fashion. The first file is filled, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of listener.trc is used, and this parameter is set to 3, then the trace files would be named listener1.trc, listener2.trc and listener3.trc.
In addition, trace events in the trace files are preceded by the sequence number of the file.
TRACE_TIMESTAMP_listener_name
You must set this parameter manually.
A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for every trace event in the listener trace file.

Using the Trace Assistant to Examine Trace Files

Oracle Net Services provides a tool called the Trace Assistant to help you understand the information provided in trace files by converting existing lines of trace file text into a more readable paragraph. The Trace Assistant works only with level 16 (support) Oracle Net Services trace files.

To run the Trace Assistant, enter the following command at any command line prompt:
trcasst [options] filename


Option Description
-elevel
Displays error information. After the -e, use 0, 1, or 2 error decoding level may follow:
  • 0 or nothing translates the NS error numbers dumped from the nserror function plus lists all other errors
  • 1 displays only the NS error translation from the nserror function
  • 2 displays error numbers without translation
-la
If a connection ID exists in the NS connect packet, then the output displays the connection IDs. Connection IDs are displayed as hexadecimal, eight-byte IDs. A generated ID is created by Trace Assistant if the packet is not associated with any connection, that is, the connect packet is overwritten in the trace file. This can occur with cyclic trace files.
For each ID, the output lists the following:
  • Socket ID, if the connection has one.
  • Connect packet send or receive operation.
  • Current setting of the MULTIPLEX attribute of the DISPATCHERS parameter in the initialization parameter file. When MULTIPLEX is set to ON, session multiplexing is enabled.
  • Session ID, if MULTIPLEX is set to ON.
  • Connect data information.
Notes:
  • Do not use this option with other options.
  • The IDs generated by the Trace Assistant do not correlate with client/server trace files.
-li ID
Displays the trace for a particular ID from the -la output
Note: Only use this option with output from the -la option.
-otype
Displays the amount and type of information to be output. After the -o the following options can be used:
  • c to display summary connectivity information.
  • d to display detailed connectivity information.
  • u to display summary Two-Task Common (TTC) information.
  • t to display detailed TTC information.
  • q to display SQL commands enhancing summary TTC information. Use this option with u, such as -ouq.
Note: As output for d contains the same information as displayed for c, do not submit both c and d. If you submit both, then only output d is processed.
-s
Displays the following statistical information:
  • Total number of bytes sent and received.
  • Maximum open cursors.
  • Currently open cursors.
  • Count and ratio of operations.
  • Parsing and execution count for PL/SQL.
  • Total calls sent and received.
  • Total, average, and maximum number of bytes sent and received.
  • Total number of transports and sessions present.
  • Timestamp information, if any.
  • Sequence numbers, if any.


If no options are provided, then the default is -odt -e0 -s, which provides detailed connectivity and TTC events, error level zero (0), and statistics in the trace file



Demo:

Before you enable Network Tracing try to understand this “DIAG_ADR_ENABLED” parameter it has good significance in 11gR2.

The default value of DIAG_ADR_ENABLED is on. Therefore, the DIAG_ADR_ENABLED parameter must explicitly be set to off in order for non-ADR tracing to be used in your sqlnet or listener.ora files..


Note:- You don’t need to bounce any services for sqlnet.ora changes:


[oracle@collabn1 admin]$ adrci

ADRCI: Release 11.2.0.1.0 - Production on Wed Sep 16 11:35:38 2015

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

ADR base = "/u01/app/oracle"
adrci> show tracefile
    diag/netcman/collabn1/cman_collabn1/trace/cman_collabn1.log
    diag/tnslsnr/collabn1/listener/trace/listener.log
    diag/tnslsnr/collabn1/cman/trace/cman.log
    diag/tnslsnr/collabn1/shaikdb/trace/shaikdb.log
adrci>


[oracle@collabn1 admin]$ vi /u01/app/oracle/diag/tnslsnr/collabn1/shaikdb/trace/shaikdb.log

Wed Sep 16 11:35:14 2015
16-SEP-2015 11:35:14 * service_update * SHAIKDB * 0
Wed Sep 16 11:35:38 2015
16-SEP-2015 11:35:38 * service_update * SHAIKDB * 0
Wed Sep 16 11:36:14 2015
16-SEP-2015 11:36:14 * service_update * SHAIKDB * 0


Create a trace directory for client & server:


[oracle@collabn1 oracle]$ ls -lrt
total 8
drwxr-xr-x 3 oracle dba      4096 Sep 16 10:56 client
drwxr-xr-x 3 oracle oinstall 4096 Sep 16 10:58 server


Enable tracing on the server:

vi $TNS_ADMIN/sqlnet.ora

#Logging details
DIAG_ADR_ENABLED=OFF
TRACE_DIRECTORY_SERVER=/u02/app/oracle/server/trace
TRACE_FILE_SERVER=SHAIKDB_SERVER.trc
TRACE_LEVEL_SERVER=admin
TRACE_TIMESTAMP_SERVER=ON
                          

[oracle@collabn1 diag]$ ls -lrt /u02/app/oracle/server/trace
total 92
-rw-r----- 1 oracle dba 36450 Sep 16 11:30 shaikdb_server_23228.trc
-rw-r----- 1 oracle dba 38633 Sep 16 11:30 shaikdb_server_23282.trc
-rw-r----- 1 oracle dba  5137 Sep 16 11:31 shaikdb_server_24305.trc
-rw-r----- 1 oracle dba  3062 Sep 16 11:31 shaikdb_server_24307.trc
-rw-r----- 1 oracle dba  3062 Sep 16 11:33 shaikdb_server_24879.trc

With TRACE_LEVE_SERVER=admin

vi /u02/app/oracle/server/trace/shaikdb_server_23282.trc

[16-SEP-2015 11:30:26:273] --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
[16-SEP-2015 11:30:26:273] New trace stream is /u02/app/oracle/server/trace/shaikdb_server_23282.trc
[16-SEP-2015 11:30:26:273] New trace level is 6
[16-SEP-2015 11:30:26:273] --- TRACE CONFIGURATION INFORMATION ENDS ---
[16-SEP-2015 11:30:26:273] --- PARAMETER SOURCE INFORMATION FOLLOWS ---
[16-SEP-2015 11:30:26:273] Attempted load of system pfile source /u01/app/oracle/product/11.2.0.2/SHAIKPROD/network/admin/sqlnet.ora
[16-SEP-2015 11:30:26:273] Parameter source loaded successfully
[16-SEP-2015 11:30:26:273]
[16-SEP-2015 11:30:26:273]  -> PARAMETER TABLE LOAD RESULTS FOLLOW <-
[16-SEP-2015 11:30:26:273] Successful parameter table load
[16-SEP-2015 11:30:26:273]  -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <-
[16-SEP-2015 11:30:26:273]   DIAG_ADR_ENABLED = OFF
[16-SEP-2015 11:30:26:273]   TRACE_DIRECTORY_SERVER = /u02/app/oracle/server/trace
[16-SEP-2015 11:30:26:273]   TCP.INVITED_NODES = (collabn1.shaiksameer, collabn2.shaiksameer)
[16-SEP-2015 11:30:26:273]   TRACE_FILE_CLIENT = SHAIKDB_CLIENT.trc



With TRACE_LEVE_SERVER=user

[16-SEP-2015 11:57:09:415] --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
[16-SEP-2015 11:57:09:415] New trace stream is /u02/app/oracle/server/trace/shaikdb_server_2243.trc
[16-SEP-2015 11:57:09:415] New trace level is 4
[16-SEP-2015 11:57:09:415] --- TRACE CONFIGURATION INFORMATION ENDS ---
[16-SEP-2015 11:57:09:415] --- PARAMETER SOURCE INFORMATION FOLLOWS ---
[16-SEP-2015 11:57:09:415] Attempted load of system pfile source /u01/app/oracle/product/11.2.0.2/SHAIKPROD/network/admin/sqlnet.ora
[16-SEP-2015 11:57:09:415] Parameter source loaded successfully



With TRACE_LEVE_SERVER=support

[16-SEP-2015 12:01:42:191] --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
[16-SEP-2015 12:01:42:191] New trace stream is /u02/app/oracle/server/trace/shaikdb_server_4386.trc
[16-SEP-2015 12:01:42:191] New trace level is 16
[16-SEP-2015 12:01:42:191] --- TRACE CONFIGURATION INFORMATION ENDS ---
[16-SEP-2015 12:01:42:191] --- PARAMETER SOURCE INFORMATION FOLLOWS ---
[16-SEP-2015 12:01:42:191] Attempted load of system pfile source /u01/app/oracle/product/11.2.0.2/SHAIKPROD/network/admin/sqlnet.ora
[16-SEP-2015 12:01:42:191] Parameter source loaded successfully
[16-SEP-2015 12:01:42:191]



Enable Listener tracing:

Since you could have multiple listeners in listener.ora file  you have to explicitly call out the name of the “listener” while setting the tracing parameters in listener.ora.


Caveat with listener is you have to change the DIAG_ADR_ENABLED_LISTENER_NAME=OFF

vi listener.ora
DIAG_ADR_ENABLED_SHAIKDB=OFF
TRACE_DIRECTORY_shaikdb=/u02/app/oracle/listener/trace
TRACE_FILE_shaikdb=SHAIKDB_listener.trc
TRACE_LEVEL_shaikdb=admin
TRACE_TIMESTAMP_shaikdb=ON


Before the bounce of listener:

[oracle@collabn1 ~]$ lsnrctl status shaikdb

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 16-SEP-2015 12:30:19

Copyright (c) 1991, 2009, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=collabn1.shaiksameer)(PORT=1522)))
STATUS of the LISTENER
------------------------
Alias                     SHAIKDB
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                14-SEP-2015 00:34:02
Uptime                    2 days 11 hr. 56 min. 16 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/11.2.0.2/SHAIKPROD/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/collabn1/shaikdb/alert/log.xml
Listening Endpoints Summary...
 (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=collabn1.shaiksameer)(PORT=1522)))
Services Summary...
Service "SHAIKDB.shaiksameer" has 2 instance(s).
 Instance "SHAIKDB", status UNKNOWN, has 1 handler(s) for this service...
 Instance "SHAIKDB", status READY, has 1 handler(s) for this service...
The command completed successfully


TO:

[oracle@collabn1 ~]$ lsnrctl reload shaikdb

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 16-SEP-2015 14:21:41

Copyright (c) 1991, 2009, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=collabn1.shaiksameer)(PORT=1522)))
The command completed successfully


[oracle@collabn1 ~]$ lsnrctl status shaikdb

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 16-SEP-2015 14:21:49

Copyright (c) 1991, 2009, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=collabn1.shaiksameer)(PORT=1522)))
STATUS of the LISTENER
------------------------
Alias                     shaikdb
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                16-SEP-2015 13:58:56
Uptime                    0 days 0 hr. 22 min. 52 sec
Trace Level               admin
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/11.2.0.2/SHAIKPROD/network/admin/listener.ora
Listener Log File         /u02/app/oracle/listener/trace/shaikdb.log
Listener Trace File       /u02/app/oracle/listener/trace/shaikdb_listener.trc
Listening Endpoints Summary...
 (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=collabn1.shaiksameer)(PORT=1522)))
Services Summary...
Service "SHAIKDB.shaiksameer" has 1 instance(s).
 Instance "SHAIKDB", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully


Trace files:

[oracle@collabn1 admin]$ cd /u02/app/oracle/listener/trace/

[oracle@collabn1 trace]$ ls -lrt
total 68
-rw-r----- 1 oracle oinstall  3033 Sep 16 14:24 shaikdb.log
-rw-r----- 1 oracle oinstall 62762 Sep 16 14:24 shaikdb_listener.trc


[oracle@collabn1 trace]$ vi shaikdb_listener.trc

NSLSNR for Linux: Version 11.2.0.1.0 - Production on 16-SEP-2015 14:21:41

Copyright (c) 1991, 2009, Oracle.  All rights reserved.

[16-SEP-2015 14:21:41:900] --- TRACE CONFIGURATION INFORMATION FOLLOWS ---
[16-SEP-2015 14:21:41:900] New trace stream is /u02/app/oracle/listener/trace/shaikdb_listener.trc
[16-SEP-2015 14:21:41:900] New trace level is 6
[16-SEP-2015 14:21:41:900] --- TRACE CONFIGURATION INFORMATION ENDS ---
[16-SEP-2015 14:21:41:900] --- LOG CONFIGURATION INFORMATION FOLLOWS ---
[16-SEP-2015 14:21:41:900] Existing log stream is identical to desired "/u02/app/oracle/listener/trace/shaikdb.log"; ignoring alter
[16-SEP-2015 14:21:41:900] --- LOG CONFIGURATION INFORMATION ENDS ---
------
----

[16-SEP-2015 14:25:00:120] nsevfnt: cxd: 0xa62f50 stage 0: NS events set:
       READY FOR SEND
[16-SEP-2015 14:25:00:120] nsevrec: event is 0x10, on 4
[16-SEP-2015 14:25:00:120] nsevwait: 1 posted event(s)
[16-SEP-2015 14:25:00:120] nsglhe: entry
[16-SEP-2015 14:25:00:120] nsglrohe: entry
[16-SEP-2015 14:25:00:120] nsevmute: cid=4
[16-SEP-2015 14:25:00:120] nsglrohe: exit
[16-SEP-2015 14:25:00:120] nsglhe: exit
[16-SEP-2015 14:25:00:120] nsevwait: 3 registered connection(s)
[16-SEP-2015 14:25:00:120] nsevwait: 0 pre-posted event(s)
[16-SEP-2015 14:25:00:120] nsevwait: waiting for transport event (1 thru 4)...
Posted by sameer at 8:16 AM
Labels: ,
Reactions: 

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)