RE: dbms_support and not getting an explain plan
Date: Mon, 19 May 2008 13:39:53 -0400
Message-ID: <21469B88E0EA11498818517F210335310455AE7F@EPRI17P32001A.csfb.cs-group.com>
When the plan is in the raw trace file, it's easy to see it. I think
tkprof output with no plan results simply from the plan's absence from
the raw trace file.
Paul Baumgartel
CREDIT SUISSE
Information Technology
Prime Services Databases Americas
One Madison Avenue
New York, NY 10010
USA
Phone 212.538.1143
paul.baumgartel_at_credit-suisse.com
www.credit-suisse.com
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Allen, Brandon
Sent: Monday, May 19, 2008 12:37 PM
To: ricks12345_at_gmail.com; oracle-l_at_freelists.org
Subject: RE: dbms_support and not getting an explain plan
I have the same problem pretty frequently - it applies to all 10046 traces, whether you get it from event 10046, sql_trace=true, dbms_support, etc. and I think it comes from tkprof not being able to properly sort out multiple queries with the same cursor number when there are multiple sessions for the same process so they're written to a single trace file.
I think all you can do is go into the raw trace file and get the plan directly from the STAT lines. You might be able to edit the raw trace file and manually remove all other queries using the same cursor number and then run tkprof again and see if that works, but that could be a pretty tedious process.
Regards,
Brandon
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
-- http://www.freelists.org/webpage/oracle-lReceived on Mon May 19 2008 - 12:39:53 CDT