]
October 10, cc:
2002 10:14 AMSubject: RE: DROP DEVELOPER not working -
10046 trace(Document link:
Rajesh Rao
Title: RE: DROP DEVELOPER not working - 10046 trace
execution plan comes at the end ... that's why ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't
As I was investigating more on this issue, I took a close look at the
select statement which runs just before the drop. Isnt this select
statement supposed to have a STAT with the execution plan in the 10046
trace file. Why dont I see it here? The entries in the trace file are :
PARSING IN
DEVELOPER not
working - 10046 trace(Document link:
Rajesh Rao)
As I was investigating more on this issue, I took a close look at the
select statement which runs just before the drop. Isnt this select
statement supposed to have a STAT
:
@espn.com Subject: RE: DROP DEVELOPER not
working - 10046 trace
Sent
:
Sent by: Subject: RE: DROP DEVELOPER not
working - 10046 trace
[EMAIL PROTECTED
Sorry, I did not pay attention to what level trace you were generating... :(
- Kirti
-Original Message-
Sent: Thursday, October 10, 2002 2:25 PM
To: Multiple recipients of list ORACLE-L
Thanks Kirti. While I cannot stop drops completely, I am thinking I could
use dbms_system with the
Raj,
This reminds me of a similar situation I encountered several years
ago, perhaps there will be something in it that will help...
A 3rd party app was periodically committing only 2 of 3 changes that
were required. The most likely explanation of the problem was that there was
an
PROTECTED]
October 10, cc:
2002 10:14 AMSubject: RE: DROP DEVELOPER
not working - 10046 trace(Document link:
Rajesh Rao)
As I was investigating more on this issue, I took a close look
