Oracle tracking file (1)

1. Trace file)

1. Provides detailed debugging information. When a server fails, a trace file containing a large amount of diagnostic information is generated.
2. Enable tracking SQL _TRACE = TRUE
3. Measure oracle
   1. V $ view, such as v $ waitstat and V $ SESSION_EVENT, to reflect what happens to the kernel
   2. Audit Command
   3. Resource Manager
   4. Oracle events: oracle events allow Oracle to generate tracking and diagnostic information
   5. DBMS_TRACE: record the call tree of the stored procedure and exceptions.
   6. Database event triggers: for example, ON SERVERERROR
   7. SQL _TRACE: an extension of the SQL tracking tool, through the 10046oracle event
4. 10046 events need to be tracked
   1. SQL _TRACE = TRUE;
   2. Alter session set events '2017 trace name context forever, level 12'
5. Tracking File Location
   1. Assume that the dedicated server connection mode is used: the trace file generated in the directory specified by the USER_DUMP_DEST Parameter
   2. For example, the shared server connection method is as follows: in the directory of the BACKGROUND_DUMP_DEST parameter tracking File
   3. Check the parameter name of show parameter.

Ii. Tracking File naming rules

1. Related statement generation trace file name

SELECT d. VALUE | '\' | C. INSTANCE_NAME | '_ ora _' | B. SPID | '. trc' trace

FROM v $ session,

V $ process B,

V $ instance c,

V $ parameter d

WHERE a. paddr = B. addr

And a. AUDSID = USERENV ('sessionid ')

And d. NAME = 'user _ dump_dest'

Select * from