Hi Pete, Are you running on SAN storage? I encountered a scenario before that filesystems just got read only (non internal disks). And we keep on recovering the database files and putting them on the other file systems because we suspected problems on disks. Then we have it checked by the EMC engineer and sent the emcgrab to Powerlink then found out that it was an EMC Powerpath related problem, caused by two failing storage processors which resulted to filesystems not being synced with the actual storage, this is causing Linux to mount the filesystems /u02 & /u06 in Read-only mode and Oracle Database not obtaining lock on the datafiles. You could also look at dmesg and /var/log/messages - Karl Arao http://karlarao.wordpress.com On Tue, Jul 14, 2009 at 5:10 PM, Peter Hitchman<pjhoraclel@xxxxxxxxx> wrote: > Hi, > I tried dbv today with 11.1.0.06 on RHL4, normal cooked file system. > > I get: > > dbv file=system01.dbf blocksize=8192 > > DBVERIFY: Release 11.1.0.6.0 - Production on Tue Jul 14 10:07:17 2009 > > Copyright (c) 1982, 2007, Oracle. All rights reserved. > > > DBV-00600: Fatal Error - [21] [2] [0] [0] > > MetaLink lists a bug (Bug 6820317 -) about not having write access the > file, but this is not the case here and the error message is different. > > I only tried this because over-night the some oddity made the root file > system read only and we had to reboot. > > Any one else seen this? > > Regards > > Pete > -- //www.freelists.org/webpage/oracle-l