Difference: SQLTraceAnalysis (7 vs. 8)

Revision 82006-06-19 - LucaCanali

Line: 1 to 1
 
META TOPICPARENT name="DbaArea"

SQL Trace Access and Analysis: OraSRP

Line: 17 to 17
 
  1. export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/scripts/orasrp; export PATH=$PATH:$HOME/scripts/orasrp
  2. (optional) create password-authenticated user
    • cd to the UDUMP directory. Example: cd /ORA/dbs00/oracle/admin/DBNAME/udump
Changed:
<
<
    • create user. Example: htpasswd -c .htpasswd luca
>
>
    • create user (optional) . Example: htpasswd -c .htpasswd luca
 
    • run orasrp listening on a chosen port. optionally define a keyword on the trace files. Example:
Changed:
<
<
nophup orasrp -d /ORA/dbs00/oracle/admin/DBNAME/udump --htpasswd --port 2502 --pattern=luca &
>
>
nohup orasrp -d $PWD --port 2502 --pattern=luca &
 
    • Note: on RAC orasrp should be run on multiple nodes
    • Note: different port numbers can be used to run orasrp simultaneously for different users.
Changed:
<
<
>
>
    • Note: add --htpasswd to the command line enforce user/pass authentication
 

Instructions to get started:

  • the session parameter tracefile_identifier is needed to add the pattern defined above to the trace files. Example: alter session set tracefile_identifier='luca';
  • activate the trace. Example: exec dbms_monitor.SESSION_TRACE_ENABLE;
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback