db_dump [-klNpRrV] [-d ahr] [-f output] [-h home] [-s database] file db_dump185 [-p] [-f output] file
The db_dump utility reads the database file file and writes it to the standard output using a portable flat-text format understood by the db_load utility. The argument file must be a file produced using the Berkeley DB library functions.
The db_dump185 utility is similar to the db_dump utility, except that it reads databases in the format used by Berkeley DB versions 1.85 and 1.86.
The options are as follows:
The output format of the -d option is not standard and may change, without notice, between releases of the Berkeley DB library.
Note: different systems may have different notions about what characters are considered printing characters, and databases dumped in this manner may be less portable to external systems.
Dumping and reloading Hash databases that use user-defined hash functions will result in new databases that use the default hash function. Although using the default hash function may not be optimal for the new database, it will continue to work correctly.
Dumping and reloading Btree databases that use user-defined prefix or comparison functions will result in new databases that use the default prefix and comparison functions. In this case, it is quite likely that the database will be damaged beyond repair permitting neither record storage or retrieval.
The only available workaround for either case is to modify the sources for the db_load utility to load the database using the correct hash, prefix, and comparison functions.
The db_dump185 utility may not be available on your system because it is not always built when the Berkeley DB libraries and utilities are installed. If you are unable to find it, see your system administrator for further information.
The db_dump and db_dump185 utility output formats are documented in the Dump Output Formats section of the Berkeley DB Reference Guide.
The db_dump utility may be used with a Berkeley DB environment (as described for the -h option, the environment variable DB_HOME, or because the utility was run in a directory containing a Berkeley DB environment). In order to avoid environment corruption when using a Berkeley DB environment, db_dump should always be given the chance to detach from the environment and exit gracefully. To cause db_dump to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT).
Even when using a Berkeley DB database environment, the db_dump utility does not use any kind of database locking if it is invoked with the -d, -R, or -r arguments. If used with one of these arguments, the db_dump utility may only be safely run on databases that are not being modified by any other process; otherwise, the output may be corrupt.
The db_dump utility exits 0 on success, and >0 if an error occurs.
The db_dump185 utility exits 0 on success, and >0 if an error occurs.
Copyright Sleepycat Software