Re: external storage and commit?

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Mon, 15 Apr 2002 18:43:42 +0200
Message-ID: <0n0mbu83890l9usqighq1i2iqtv0cad1sn@4ax.com>

On 15 Apr 2002 05:51:47 -0700, timasmith_at_hotmail.com (Tim Smith) wrote:

>Hi,
> For Direct Attached Storage I believe I am correct in saying that
>when a transaction is committed it is written to disk.
>
> For external storage, such as an IBM ESS(Shark) am I correct in
>saying that a transactions may be written to the ESS cache and not
>written to disk?
>
> Would this mean a subsequent general power failure could cause
>transactions (otherwise supposed to be committed) to be lost?
>
>thanks
>
>Tim

Generally speaking any O/S caching should be turned off or limited as much as possible.
All transactions are protected using the online redo log, and of course you run in archivelog, and you don't have all your database files (and definitely not the online redologs) on such a device.

Hth

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Mon Apr 15 2002 - 11:43:42 CDT