Re: DB_VERIFY

OK so DB_verify isn't supposed to work on redo logs (I kind of knew that already but just wanted to confirm it.. and my redo logs are mirrored anyway.) How about controlfiles?

I get the following for both controlfiles that I backed up:

DBVERIFY: Release 7.3.3.0.0 - Production on Thu Jan 20 11:15:15 2000

Copyright (c) Oracle Corporation 1979, 1996. All rights reserved.

DBVERIFY - Verification starting : FILE = cntrl2a.dbf Page 1 is marked software corrupt
Page 3 is marked software corrupt
Page 4 is marked software corrupt
Page 9 is marked media corrupt
Page 10 is marked media corrupt
Page 11 is marked software corrupt
Page 12 is marked software corrupt
Page 21 is marked software corrupt
Page 22 is marked software corrupt
Page 23 is marked media corrupt
Page 24 is marked media corrupt
Page 25 is marked media corrupt
Page 26 is marked media corrupt
Page 36 is marked software corrupt
Page 141 is marked software corrupt
Page 142 is marked software corrupt
Page 143 is marked media corrupt
Page 144 is marked media corrupt
Page 161 is marked software corrupt
Page 162 is marked software corrupt
Page 164 is marked software corrupt
Page 166 is marked software corrupt

DBVERIFY - Verification complete

Total Pages Examined         : 452
Total Pages Processed (Data) : 0
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 0
Total Pages Failing   (Index): 0
Total Pages Empty            : 430
Total Pages Marked Corrupt   : 22
Total Pages Influx           : 0

i.e. all pages are corrupt that contain anything

I have an upto date "recreate controlfile" sql script (from alter database... to trace). Which I would use instead, I guess.

I can't find any documentation about db_verify errors on technet.oracle.com. Should I be able to???

Thanks again for any input,

Sarah Received on Thu Jan 20 2000 - 05:33:27 CST