How to read and analyze Trace files in oracle

How can one analyze the information generated in bdump tracefiles ?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Use the tkprof utility.

I have attached a code snippet for a simple unix script that processes the latest trace file in the Oracle dump directory (you will need to edit this directory in the script) and generates a readable trace file.

Save the code as a script and call it something like traceit then change the privileges e.g. chmod 775 traceit.

Don't forget to change the database password used by the tkprof call.

If you run the script without an argument it will process the newest file in the udump directory, otherwise it will process the file that you give to the script.

Of course, this assumes you are working on unix!
trace_dir=/sld/oracle/admin/udump   # Location of the trace files
if [ "$1" = "" ]
    infile=`ls -t $trace_dir/sld_ora*.trc | head -1`
echo Converting $infile
tkprof $infile $outfile explain=username/password sort=exeela
if [ $? -eq 0 ]
    echo "Trace output produced in file $outfile"

Open in new window

Hi, just wondered if you had managed to successfully process your trace files.
BDUMP trace files generally have memory dumps and other system-state type information in them are largely unusable to end users.

You can use the Metalink ORA-600 lookup tool to extract info from the dump.

As the previous posts mention UDUMP traces can be parsed and summarized with tkprof, you can also you Oracle's trace analyzer from Metalink.

You can session specific information in a BDUMP tracefile too, but it's still oracle internal calls like "kgxxxxxxxx" many (most?) of which aren't publicly documented.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.