Re: Implicit Commit...pls remind me.

If your stored procedure code contains a commit, then your commit should be applied successfully. However, if you are relying on the client to issue the commit, your transaction should get rolled back *IF* the Windows client crashed abnormally.

If you need to commit regardless of what Windows does, then the PL/SQL should contain an explicit commit or rollback on error. Tools and drivers have configurable commit behavior. In my SQL*PLUS for windows, the autocommit is set to OFF/false. If you set autocommit to ON/TRUE then your client will issue a commit at the end of your session.

So... The answer to your question is that it depends on how the client is configured, where the transaction was expecting the rollback or commit, and how the client crashed - blue screen, lost channel, timeout, etc.

Good Luck!

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Chris Weiss
mailto:chris_at_hpdbe.com
www.hpdbe.com
High Performance Database Engineering
Available for long and short term contracts


"R Chin" <rchin_at_panix.com> wrote in message
news:aautpc$mr$1_at_reader1.panix.com...


> Someone please remind me.....

>

> 8.1.7/AIX

>

> If I am in the middle of a lengthy transaction (PL/SQL) like..

>

> procedure MAIN

> is

> begin

>   proc_1;

>   proc_2;

>   proc_3;

>   ........

> end;

>

> executing MAIN in SQL+...

> If the client (windoz) crashes on me....am I gonna get an implicit commit

?


> What if I run each proc separately, one at a time....then crash....?

>

> Thanks

> Rob

>

>

>