Background: \nThe database was being backed-up thru a process of disk copy/syncing from a working, live production database server.  Hence, the state log of the database was marked consistent, see infodb.log\n\nErrors from errlog.log:\n1. E_DM930C_DM0P_PAGE_CHKSUM_FAIL Page Checksum failure detected. Database pfmdb, Table iiattribute.  This is because of a corrupted system catalog.\n2. E_RD0060_DMT_SHOW Cannot access table information due to a non-recoverable DMT_SHOW error. This happens when the underlying physical files for the tables do not exist anymore or is corrupted.\n\nSteps taken:\nIf the database is inconsistent due to operation, we tried to force it consistent thru the following commands:\n1. sql -A10 pfmdb -- This returns E_QE007C Error trying to get a record.  This happens if the said database is inconsistent but unfortunately the -A10 should force it consistent already.\n2. verifydb -mrun -sdbname pfmdb -oforce_consistent.  This command will flag the state of the database consistent for access but also failed.\n3. sysmod pfmdb -- Failed with errors.\n\nFindings:\n1. Prior to this incident, a corrupted database and system file was seen, files with priviledge, ownership and group with (?).\n2. The database is corrupted and NOT inconsistent due to a corrupted system / database file.\n\nResolution:\nTry to recover the database using rollforwarddb from an existing checkpoint file/s:\n1. destroydb pfmdb\n2. rollforwarddb pfmdb\n3. sysmod\n\n\n\n\n\n