Problem solve
Get help with specific problems with your technologies, process and projects.
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.
Dig Deeper on Oracle and SQL
-
![]()
How is asynchronous microservices tracing best accomplished?
By: Bob Reselman
-
![]()
Dynatrace traces measured route to PurePath 4
By: Adrian Bridgwater
-
![]()
UK, Jersey, Gibraltar contact-tracing apps now interoperable
By: Joe O’Halloran
-
![]()
UK government reveals more insight into imminent contact-tracing app
By: Joe O’Halloran
