Re: Unable to disable tracing - XE
Date: Wed, 10 Feb 2010 11:51:47 -0800 (PST)
Message-ID: <cd34dea6-9c73-4dfe-ad37-ae1147399264_at_k5g2000pra.googlegroups.com>
On Feb 10, 6:02 am, John Hurley <johnbhur..._at_sbcglobal.net> wrote:
> On Feb 10, 6:49 am, Charles Hooper <hooperc2..._at_yahoo.com> wrote:
>
> snip
>
> > I agree with John - take a look at the number after dep= in the trace
> > file - that is indicating that it is very likely a trigger that is
> > executing these calls, but it could also be an anonymous PL/SQL
> > block. You might try the following SQL statement to see if there is a
> > logon or startup trigger:
>
> It is a little hard to believe that someone would have a trigger in
> effect that they forgot about but ...
>
Not hard to believe at all, it's easy to forget to unwind every bit of instrumentation turned on in the heat of a problem, especially with multiple cooks involved. I didn't even think of a logon trigger because I so rarely do it that way, forehead-slapping obvious now that you guys pointed it out. There was a time I ran startup scripts to pin stuff in the shared library too, but I haven't done that in a very long time, either...
I'm still finding stuff in odd places from a remote developer while I was on vacation last year. Take a complicated stack and put pressure on to get things done, all sorts of weird happens. Then you have to figure out what was fanned and what is necessary but named wrong.
Heck, even Oracle has delivered with trace turned on (otr, was it 7.3.2?). Oops!
jg
-- _at_home.com is bogus. http://www.signonsandiego.com/news/2010/feb/10/barber-finds-fame/Received on Wed Feb 10 2010 - 13:51:47 CST