Trace File extract

[st2000]

Hello Guys:

Following are the incerpts from a trace file that I run all night on a job that kicks off from the application. I have put the entire db in trace mode.. and removed later on.

How do I go about decoding this?

Actually, the application vendor has asked us to do this and forward the findings to them. The trace file is about 6700 pages (in MS Word).. How on earth would they be able to decode the whole file.. Would Vendors usually develop tools for these things?


===============================================================================
PARSING IN CURSOR #91 len=237 dep=1 uid=18 oct=2 lid=18 tim=4265269657 hv=369538325 ad='32f7c690'
INSERT INTO SDIFINGLH ( GLI_BATCH_NUM,GL_CO_CODE,POSTING_DATE,FIN_CAL_FISC,FIN_CAL_PER,TOTAL_GL_AMOUNT,SOURCE,POSTING_USER,T OTAL_GL_COUNT,GL_BEG_DATE,GL_END_DATE,CURR_CODE ) VALUES ( :b1,:b2,:b3,:b4,:b5,:b6,:b7,:b8,:b9,:b10,:b11,:b12 )
END OF STMT
PARSE #91:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=0,tim=4265269657
EXEC #91:c=0,e=0,p=0,cr=1,cu=3,mis=0,r=1,dep=1,og=4,tim=4265269657
XCTEND rlbk=0, rd_only=0
=====================

Thanks, ST2000

[pando]

tkprof

[noor]

Hello,

As pendo indicated, you have to use tkprof (or tkprof80) in order to obtain a more readable file.

Command :

tkprof your_trace_file_name your_output_file_name

[stmontgo]

tkprof as indicated is the best way to go,

if you feel like punishing yourself or perhaps require a more discrete level of anlysis then have a look at the following note on metalink. If you don't have access to metalink I'll send it to you if you like

Doc ID: Note:39817.1
Subject: Interpreting Raw SQL_TRACE and DBMS_SUPPORT.START_TRACE output
Type: REFERENCE
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 24-DEC-1997
Last Revision Date: 12-AUG-2002


steve

[st2000]

Thanks... Guys