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.
Dig Deeper on Oracle and SQL
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.