Interpret Trace File

I collected some trace file which might contains errors detail .
The trace file is generated from an oracle8.0.5 database and now
I have only oracle7.3/Oracle8.1.X TKPROF .

After running tkprof against those trace file . There are no errors reported but the output file is very small and no much information in it ( trace file itself contains quite a lot information , each around 200KB) I am wondering whether it's due to version incompatiable .

In fact the main error shows in trace file is :
*** 2002.10.23.09.20.38.190
*** SESSION ID:(18.1395) 2002.10.23.09.20.34.104
FATAL ERROR IN TWO-TASK SERVER: error = 12571
*** 2002.10.23.09.20.38.250
ksedmp: internal or fatal error
Current SQL statement for this session:
SELECT B_BISSUE,B_BITEM,B_BREVISION,B_BITEMD,B_BINOHQTY,B_BMOVEQTY,B_BREMARK FROM B_BISSD WHERE B_BISSUE=:K00000 AND (B_BITEM BETWEEN :L00001 AND :H00001) ORDER BY B_BISSUE,B_BITEM,B_BREVISION
----- Call Stack Trace -----

how to found the details of this kind of error (12571)



the output looks like :
TKPROF: Release 8.1.6.0.0 - Production on Mon Oct 28 09:38:05 2002

(c) Copyright 1999 Oracle Corporation. All rights reserved.

Trace file: ORA00077.TRC
Sort options: default

********************************************************************************
count = number of times OCI procedure was executed
cpu = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk = number of physical reads of buffers from disk
query = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows = number of rows processed by the fetch or execute call
********************************************************************************
Trace file: ORA00077.TRC
Trace file compatibility: 8.00.04
Sort options: default

2 sessions in tracefile.
0 user SQL statements in trace file.
0 internal SQL statements in trace file.
0 SQL statements in trace file.
0 unique SQL statements in trace file.
5465 lines in trace file.

If I am not wrong TKPORF is used on SQL_TRACE files, not on trace files generated by errors.

Sanjay

OIC

THEN HOW TO ANALYZE ORACLE ERROR TRACE FILE.
BECAUSE I AM ALSO FACING SAME PROBLEM

sned them to oracle support

sned them to oracle support
we hv no oracle support.



P.soni

why not?

i tried the link provided for oracle support in this forum, but ask some code which we don't know.
bye-the-way i have gone thru oracle documentation it says that there is a utility DUMPFMT in oracle which format the oracle trace file.
i searhed my server but couldn't found the utility. anyone hv any idea ??


P.soni

i presume you went to metalink and tired that, but since you haveno support you dont have access to it (i.e it needs to be paid for)

only thing you can is search forums, google and newsgroups for help

any idea about DUMPFMT ?