Re: trace uncommitted inserts

From: Mark D Powell <>
Date: Sat, 30 Apr 2011 07:16:36 -0700 (PDT)
Message-ID: <>

On Apr 28, 4:08 pm, Tiago <> wrote:
> Hi,
>   I have an application written in .net, I have only the .exe, not the
> source. It keeps processing data from an external source and inserting
> on a table, but sometimes I can't see the data on the table. Sometimes
> it inserts, sometimes doesn't. Vendor is taking too long to figure
> that out, since the message that get inserted look like exactly like
> the one that doesn't :( I suspect it is trying to commit but something
> wrong happens. App log doesn't show any error, external data source
> says it sent the data correctly, App log says it received, but nothing
> is inserted.
> Is there a way to trace uncommited inserts? I would try to check if
> the insert is happening at all, perhaps the App log isn't catching
> something that could be a big error...
> Thanks!
> -- Tiago

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.

Poor error handling often results in problems like you mentioned especially when combined with the programmer taking control of the transaction in the code instead of committing after every DML statement execution which I believe is the normal .net and jodbc for that matter defaults. There are naturally other potential problem causes incudling bugs in the exact version of the framework being used.

HTH -- Mark D Powell -- Received on Sat Apr 30 2011 - 09:16:36 CDT

Original text of this message