Consistency checking and backup in 24-7 environment
Posted in 1999
According to the manuals, one should perform a variety of
oncheck commands to ensure your instance is clean before
a level 0 archive. Since I'm the kind of person that does
what I am told, I have a script that executes the following
commands before each level 0 archive:
# validate reserved pages
oncheck -crq
# validate system catalog tables
oncheck -ccq
# validate extends
oncheck -ceq
# validate indexes
oncheck -cIq
# validate pages
oncheck -cDq
The problem is locking. oncheck might bail out because it can't
get exclusive access to a table or an application might get a
lock timeout because of oncheck's locks.
Do I dare eliminate any of the above checks? Could I perhaps do
some or all of them less frequently? What consequences might I
face if an inconsistency in the database occurs?
Jeff Larsen