Re: Hot and Cold backups

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:p1idd193h6kf8a29fa4mokfspedf6effr8_at_4ax.com...
> On Thu, 14 Jul 2005 19:29:41 GMT, "Randy Harris" <randy_at_SpamFree.com>
> wrote:
>
> >Thanks for the explanation. As I posted earlier, I was under the
impression
> >that shutdown immediate was safe, no transactions could be lost. I
> >understand now that is not the case. If I want to be certain that no
data
> >is lost, I need to use shutdown transactional.
>
> Obviously you still don't understand what is going on. You won't loose
> transactions. An uncommitted transaction is simply not a transaction.
> And of course, using shutdown transactional, will make sure you can't
> shut down the database, ever.
>
>
> --
> Sybrand Bakker, Senior Oracle DBA

Well then I sure wish someone would explain it so that I can understand.

1 - server receives a DML statement from a client application, it begins processing it, it will be committed when completed 2 - before the statement is finished processing a shutdown immediate is issued

3 - Oracle halts processing of the DML statement and rolls back the data
4 - Oracle server discards that DML statement and shuts down the database
5 - the data in that DML statement is lost

Please, please explain which part of this is wrong. Are you saying that it is the responsibility of the client application to know that the transaction was never committed? Received on Thu Jul 14 2005 - 16:07:34 CDT