Re: 10.2.0.1 trace uncommitted inserts
From: John Hurley <hurleyjohnb_at_yahoo.com>
Date: Fri, 29 Apr 2011 15:29:10 -0700 (PDT)
Message-ID: <06a1a0dc-7a24-4654-93c4-957fdba600fe_at_m13g2000yqb.googlegroups.com>
David:
Date: Fri, 29 Apr 2011 15:29:10 -0700 (PDT)
Message-ID: <06a1a0dc-7a24-4654-93c4-957fdba600fe_at_m13g2000yqb.googlegroups.com>
David:
# That is not what Mladen said or implied.
So you are Mladen are twins that understand exactly what the other was trying to convey in a newsgroup posting?
I did not realize that ...
# The intent here is to suggest that the OP possibly create a trigger
to capture insert transactions into a separate table, with other
information such as who did the insert and when, to track what is or
isn't happening.
That's such a better idea than getting a 10046 trace initially eh?
# There was no mention that the venedor is using triggers.
Try reading the next several lines of Mladens reply that I left out a couple of times. Do the shampoo thing ( rinse and repeat ) ... Received on Fri Apr 29 2011 - 17:29:10 CDT