Shared server trace file

Question

Hi All,
Our production db is 10.2.0.3 with 2 nodes RAC in MS 2003 window servers. I am wondering what kind of information that Oracle capture in the shared server trace file (file name looks like instance_s001_3333.trc) . When I open some of these files I always see one query always there along with the messages like:
WAIT #8: nam='gc cr block 2-way' ela= 1222 p1=65 p2=49677 p3=1 obj#=69689 tim=4137263779
WAIT #8: nam='gc cr block 2-way' ela= 593 p1=65 p2=50863 p3=1 obj#=69689 tim=4137265531
WAIT #8: nam='gc cr block 2-way' ela= 592 p1=65 p2=50879 p3=1 obj#=69689 tim=4137266700
Should we need to tune this query to make it disappear in the shared server trace files? What are the conditions to trigger Oracle put this query into trace file?
Thank you very much in advance for your support!
Shirley

Answer 1

These trace files are very likely generated by some trace statements originating from client programs connected to shared server processes such as client application processes, SQL*Plus, SQL Developer, OEM, TOAD, etc.
Is your client application instrumented ?
Do some people analyze performance problems on the database side ?
The triggering statements may be some ALTER SESSION statements or package calls like DBMS_MONITOR in 10g or other
(see examples in http://www.oracle.com/technology/oramag/oracle/04-jan/o14tech_perf.html).
You should also check that instances are not configured with instance level tracing:
show parameter sql_traceYou can also check current database sessions sql tracing status with:
select sid, serial, program, sql_trace from v$session where username is not null;