Re: Certain dynamic sql statements make stored procedures "forget" transaction?

From: neilsolent <>
Date: Thu, 16 May 2013 08:48:44 -0700 (PDT)
Message-ID: <>

> > Inserts to log files should always be made as an autonomous transaction.
> > So that log will never be rolled back.
> Or, you can use DBMS_SYSTEM.KSDWRT(2,....) which will make them
> impossible to roll back, as the destination is not a relational database.
> I believe it's even cheaper than to write into a table. Note to myself:
> test this with 11G where alert log is an XML file.

But I want the insert to the audit log to roll back, if the operation was rolled back.
When the audit log is examined, I want a record to mean an operation was done, rather than merely attempted (or syntactically wrong, etc). Received on Thu May 16 2013 - 17:48:44 CEST

Original text of this message