Q

Handling a large trace file

Once monthly we run a report of which we have nearly 100,000 records. It takes a long time and the performance is very slow. When I run the SQL trace for the session, the size of the trace file becomes very big. Please help me to solve this issue.

Once monthly we run a report of which we have nearly 100,000 records. It takes a long time and the performance is very slow when we run this report.

When I run the SQL trace for the session for the schema in which the report is executed, the size of the trace file becomes very big and so I put off the SQL trace. Please help me to solve this issue.

You can always format a partial trace file with tkprof, and the resulting report may reveal the problem. If it doesn't, I'd suggest that you direct your trace files to a directory on a disk with plenty of room, so that you can trace the entire operation. The tkprof utility can handle enormous trace files with no problem.
This was first published in September 2005

Dig deeper on Oracle and SQL

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide

SearchDataCenter

SearchContentManagement

SearchFinancialApplications

Close