Syntax for dumpobj
The dumpfile that is created contains all metadata plus all relational and BLOb data associated with the specified BLOb IDs. SDL Contenta can use the information in the dumpfile to restore bad blob data to a database and conduct diagnostics. The dumpobj file is located in the Contenta bin/reap directory.
| OS | Command |
|---|---|
| Windows | To create a dumpfile from an existing database (the command must be run from the Contenta_home/bin/reap directory): dumpobj-dbase existingdb@ODBC_DSN <-o|-a> <newdumpfile> <targets> |
To create a new database from an existing dumpfile (the command must be run from the Contenta_home/bin directory): Contenta_home/bin/reap/dumpobj -dbase newdbname@ODBC_DSN -i <existingdumpfile> | |
| Linux | To create a dumpfile from an existing database (the command must be run from the Contenta_home/bin/reap directory): dumpobj -dbase existingdb@SID <-o|-a> <dumpfile> <targets> |
To create a new database from an existing dumpfile (the command must be run from the Contenta_home/bin directory): <Contenta_home>/bin/reap/dumpobj -dbase newdbname@SID -i <dumpfile> |
| Switch | Description |
|---|---|
Windows: <new/existing>dbname@ODBC_DSN —or— Linux: <new/existing>dbname@SID | Required: <new/existing>dbname. The name of the new or 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 | |
| -o | creates and writes to a new dumpfile. Use either the -o or -a switch but not both. |
| -a | appends/writes to an existing dumpfile; if a dumpfile does not exist, it creates a new one. Use either the -o or -a switch but not both. |
| <dumpfile> | used with either the -o or -a switch, it is the userdefined name for the dumpfile. |
| <targets> | -t <blobspec> <blobspec>... —or— -t -f <blobspeclistfile> —or— -c |
| -c gets complete usable database | |
Without -t, blobspecs on cmdline or in listfile must be simple blobids. With -t, blobspecs can also include blobidpaths, for which blobs on the path and all blobs recursively below the path are dumped. Regular blobids with -t are just dumped as is, without parents or recursive children. -t captures enough of the database to be able to select and use the tree under any blobidpath specified. | |
additional options with -t or -c: -n[uloim] suppresses certain table subsets: u = skip users table l = skip linkends tables i = skip *info and project_ancestors tables o = skip pdm_lock/dbclean* tables m = skip main tables (database then usable only with diagnostic tools) |
The output from the dumpobj command is written to the dumpfile. When the command completes writing information to the dumpfile, the following is output to the screen:
Rebuilding ascii MetaData blob
Rebuilding binary MetaData blob
Done