Re: Questions: transaction log and commit
From: Stefan Pommerenk <spommere_at_de.oracle.com>
Date: 1996/05/31
Message-ID: <4olsup$qko_at_inet-nntp-gw-1.us.oracle.com>#1/1
Date: 1996/05/31
Message-ID: <4olsup$qko_at_inet-nntp-gw-1.us.oracle.com>#1/1
Hi,
you're absolutely right with this reasoning.
This can happen when having placed the redo logs on
RAID5 logical drives and having write cache enabled. So a commit won't
guarantee
to get the committed tx recorded on disk. In case of a system crash,
transaction
recovery could fail due to a incomplete thread recovery (rollforward with the
redo logs) und could end up with an inconsistent database.
Hope this helps
- Stefan Pommerenk, Central Technical Support Germany, RDBMS/Languages * *-----------------------------------------------------------------------------*
- Phone: +49(0)89/14350-100 MailId: spommere.DE *
- Fax: +49(0)89/14977-144 Internet: spommere_at_de.oracle.com *
- Compuserve: 100427.1516_at_compuserve.com *
- *
- --- And,... the ball is gone,... it's a HOMERUN ! --- *