Re: 10.2.0.1 trace uncommitted inserts
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Sat, 30 Apr 2011 17:14:21 +0000 (UTC)
Message-ID: <pan.2011.04.30.17.14.21_at_gmail.com>
On Sat, 30 Apr 2011 07:16:36 -0700, Mark D Powell wrote:
Date: Sat, 30 Apr 2011 17:14:21 +0000 (UTC)
Message-ID: <pan.2011.04.30.17.14.21_at_gmail.com>
On Sat, 30 Apr 2011 07:16:36 -0700, Mark D Powell wrote:
> Tiago, I think John's recommendation to use the standard Oracle trace
> feature is a good one. Every insert will be caugth by trace committed
> or not. The commits will also be caught by the trace though you will
> need to scan the raw trace file to see statements.
Of course, in case of the 3-tier application, it will be a joy to read the traces from all the server processes, especially if the application doesn't use DBMS_APPLICATION_INFO and launches a 100 or so processes when it is started.
-- http://mgogala.byethost5.comReceived on Sat Apr 30 2011 - 12:14:21 CDT