Syntax for checkblobs
The BLOb checking command (checkblobs) is located in the Contenta bin/reap directory; the command must be executed from that directory.
| OS | Command |
|---|---|
| Windows | checkblobs –dbase dbname@ODBC_DSN -restart filename [switches] |
| Linux | checkblobs –dbase dbname@sid -restart filename [switches] |
| Switch | Description |
|---|---|
Windows: dbname@ODBC_DSN —or— Linux: dbname@SID | Required: dbname. The name of the existing Contenta database. |
Optional: ODBC_DSN (Windows) The ODBC data source name. If not specified, the default is used—as defined in the registry for XYV_PDM_ODBC_DSN | |
Optional: SID (Linux) The system identifier. If not specified, the default is used—as defined in the registry for XYV_PDM_DATABASE_SID | |
| -diag filename | Optional. Where filename is the name of the file to which to write relational BLOb information—to be used for recovery. |
| -max_proc_time HH:MM | Optional Specify the maximum amount of time to allow for processing. You can continue processing at another time using the -restart and -continue switches. |
| -o logfile | Optional Sends all output messages to the specified file. Default: The file is created in the directory where checkblobs was executed. |
| -objtype typename [typename] | Optional. Where typename [typename] is one or more object types to process separated by spaces, for example: -objtype Project CompoundAscii
Only objects of the specified type are processed.
|
| -plist | Optional. Use to check that display-list children are also mentioned as children in the parent_list. Missing entries are reported but do not cause the BLOb to be marked bad. |
| -range [start_blob_id | -1] [end_blob_id | -1] | Optional. Specify the start and end BLOb numbers. Alternatively, you can specify -1 to start at the lowest BLOb id, or end at the highest existing BLOb id. |
| -restart filename | Optional (recommended) Where filename is the name of a file where checkblobs can track the id of the blob that is being processed. If a BLOb cannot be read without crashing, it allows the program to restart itself on the next BLOb. Although not required, this argument is essential if you're examining more than a small range of BLObs, in the event that one of them should cause a crash. |
| -continue | Use with the -restart switch to start processing where the previous checkblobs session stopped. |
| -v | Optional. Specify for verbose mode. Verbose mode reports the id of each blob that is checked. |
| -xrefs | Optional. Use to check for the existence of other BLOBs referred to by the object. For example: Configurations mentioned in the checkpoint table, display-list children, workflows belonging to standard Projects or ContentRoutingProjects, and graphic data BLOBs belonging to graphics. |
| delete | PDM2.5+ only |