Issuing a commit forces the LGWR to write the log buffer contents to disk physically, which is a primary mechanism for database consistency. After the successful write, committed changes are permanent whether instance crashes or not later. From your error message, I think that *somehow* log writes are partly successful leading to corruption.
It is scary to have redo log corruption just due to out-of-space errors..
I don't know much about NFS3 protocol, but is your vendor / file system in this list ?
Allen, Brandon wrote: > It is NFS3 - details below: > > > /baan4 ->mount|grep -e mounted -e --- -e baan4db > node mounted mounted over vfs date options > -- ----- -- ---- ---- -- -- ---- ---- -- -- --- -- ---- ---- -- ---- ---- -- > gbtnas01 /baan4db /baan4 nfs3 Feb 12 21:29 rw,bg,hard ,intr,rsize=8192,wsize=8192,vers=3,proto=tcp,biods=24 > > > Please let me know if you see any problems with the above config. > > Thanks, > Brandon > > > -- --Original Message-- -- > From: Riyaj Shamsudeen [mailto:rshamsud@(protected)] > Sent: Tuesday, April 18, 2006 12:14 PM > To: Allen, Brandon > Cc: Binley Lim; oracle-l@(protected) > Subject: Re: Recovery with logs, then incremental, then more logs? > > > What type of file system are you using for your redo log files ? Is there any special mount options in use ? While I agree with the solution as point-in -time recovery for online redo log corruption, but out-of-space error as a cause , does not fit for redo log files. > > > > Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. > > >
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If the reader of this message is not the intended recipient, you are hereby notified that your access is unauthorized, and any review, dissemination, distribution or copying of this message including any attachments is strictly prohibited. If you are not the intended recipient, please contact the sender and delete the material from any computer.
