This is my PeopleSoft Wiki, a PeopleSoft blog where I document even smallest of every new stuff as I learn and experience with the objective of future reference and to help others also over web community. This PeopleSoft blog also has few simple PeopleSoft tips and tricks which would be useful for fellow PeopleSoft consultants. I have also included few useful solutions to some of the standard PeopleTools and PeopleSoft HCM errors along with Oracle and Crystal Reports.
How to read a SQL Trace in PeopleSoft
As always with so many things, I struggled
initially to understand the trace file. More often, I would generate a trace
file and did not understand every aspect of the trace file. However with
experience, I have figured what is written to the trace file and sharing my
When a trace is run for SQL statements, the
resulting trace statement will have various parts. Here is the list along with
First Part: n-xxxxx.
This is a sequential line counter for the process
(exe). n is a integer starting from 1 to n. xxxxx is reserved for each line
written to the trace file. If there is a second process, then it would be
2-xxxxx, for the third one it would be 3-xxxxx and so on.
Second Part: hh.mi.ss
It indicates the timestamp at which the trace line
is written. This timestamp is retrieved from the machine in which PeopleTools
Third Part: A time value
This is the time elapsed since the previous trace
line was written. The time elapsed between n-xxxxx and n-(xxxxx+1) is written.
Fourth Part: Cur#n
This indicates the cursor number for the statement
Fifth Part: PSFT_DB
Indicates the PeopleSoft database in which this API
call is executing.
Sixth Part: RC=0
This is the return code for the associated API
Seventh Part: Dur=Another time value.
This is the time to execute the assoicated API
Eight Part: COM Stmt=<SQL Statement>
This is the database API call and provides
information on the SQL executed.