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 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.

    Requires Free Membership to View

    By submitting your registration information to SearchOracle.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchOracle.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

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

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.