Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!ucsd!ucbvax!bloom-beacon!primerd!ENI!ENY!LEBRUN
From: LEBRUN@ENY.Prime.COM
Newsgroups: comp.databases
Subject: Re: ORACLE and Regular Filesystems
Message-ID: <39700005@ENY.Prime.COM>
Date: 31 May 90 10:37:00 GMT
References: <48808@seismo.CSS.GOV>
Lines: 21
Nf-ID: #R:seismo.CSS.GOV:-4880800:ENY:39700005:000:781
Nf-From: ENY.Prime.COM!LEBRUN    May 31 10:37:00 1990



I think you problem is the your port of Oracle is not doing a forced
write at COMMIT.

There was a bug is at least some of the 6.0.26 version of the Oracle
source where forced writes were not being done at commit.  Not doing a
forced write of the buffers at COMMIT, will ruin your changes of
recovering from a crash.  It also points to the problem you are seeing.

Without a forced write at COMMIT data might not be written to the database
for some time.

I would look into this.

-----------------------------------------------------------------------------
John Lebrun                            "Software is never fast enough!"
lebrun@primerd.prime.com

I the above comments are mine and only mine.
-----------------------------------------------------------------------------