You should perform a full backup of your database to eliminate risks ..
I don't know a command to check log integrity ... But you can restore a backup on to a different system and rollforward through the afftected logs to confirm it doesn't return errors
Sathyaram
Quote:
Originally posted by ksimpson
Here is the DB2 info for DB running on Solaris 2.8
$ db2level
DB21085I Instance "ldapdb2" uses DB2 code release "SQL07028" with level
identifier "03090105" and informational tokens "DB2 v7.1.0.82", "s030617" and
"U488493".
Solaris reported a "RAID event" when writing to the file system which contains our logs. According to our sys admin. Sun is saying there may
have been a faulty write. Is there any way to validate the structure/
contents of the logs to make sure one isn't corrupted? There aren't
any signs of in the db2diag.log.
Thanks
Ken
|