Documentation Center

Output: checkblobs

Messages are reported to the window from which the checkblobs program was executed unless you specify the -o switch to redirect messages to a log file.

Bad BLOb space is reported with the following messages:

BAD BLOB <blob-id>: crashed twice trying to read it
BAD BLOB <blob-id>: attach failed
BAD BLOB <blob-id>: validation failed

Where <blob-id> is the BLOb ID.

If you use the -o logfile switch with the checkblobs tool, you can use the log file for input with the dumpobj tool. The log file must be cleaned so that each BLOb ID is on its own line. See Obtaining Diagnostic Data for Bad BLObs.

To extract the bad BLOb IDs on a Linux system, use the following syntax:

grep 'BAD BLOB' logfile | cut -d' ' -f3 | cut -d":" -f1 > blobid_list

Where logfile is the filename designated with the -l switch and blobid_list is a userdefined filename to be used with the dumpobj tool.