Re: Oracle transactions and DDL statements.

peter.koch.larsen_at_gmail.com skrev:

> Hi all
>
>
> We've run into yet another problem regarding Oracle (10g -but I doubt
> this matters), namely that the execution of a DDL statement causes a
> transaction commit. Is there any way to make this not happen? It's a
> real showstopper as we use Oracle in a distributed transaction and this
> transaction contains several DDL statements.
>
> Kind regards
> Peter

Hi all

I've been asked why DDL-statements need to be part of a transaction - I'll try to answer that here.
The application is a very flexible, distributed program with its own language and compiler that allows you to "change the application" on the fly. Part of that change involves creating the code that runs together with the data, which might be distributed on more than one database system, but even if there is only one DBMS, the code that is distributed in the system takes part in the transaction (a commit causing the old code to be discarded and the new code to be run) and the compiler can abort the transaction as well, The system has been in production for a very long time (more than ten years), and has been ported to e.g. Microsoft SQL Server, Sybase, Ingres and Teradata database system (and possible others I don't know - I am relatively new in my job). Also, I believe that similar code has been run on Oracle before - apparantly without discovering that Oracle commits no-matter-what after a DDL statement.

Kind regards
Peter Received on Mon May 08 2006 - 16:31:00 CDT