{ "content": [ { "type": "text", "text": "# DB5.3_DUMP(1) (man)\n\n**Summary:** db5.3dump - Write database to flat-text format\n\n**Synopsis:** db5.3dump [-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| -d | — | — | routines. a Display all information. h Display only page headers. r Do not display the free-list or pages on the free li |\n| -f | — | — | |\n| -h | — | — | directory is used. |\n| -k | — | — | |\n| -l | — | — | |\n| -N | — | — | tially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and shou |\n| -P | — | — | strings as soon as possible, be aware there may be a window of vulnerability on sys‐ tems where unprivileged users can s |\n| -p | — | — | isprint(3)), use printing characters in file to represent them. This option permits users to use standard text editors a |\n| -R | — | — | -r option in that it will return all possible data from the file at the risk of also returning already deleted or otherw |\n| -r | — | — | option should return equivalent data to a normal dump, but most likely in a different order. |\n| -s | — | — | database file are dumped. |\n| -V | — | — | Dumping and reloading Hash databases that use user-defined hash functions will result in new databases that use the defa |\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (2 lines)\n- **DESCRIPTION** (4 lines)\n- **OPTIONS** (1 lines) — 14 subsections\n - -d (12 lines)\n - -f (1 lines)\n - -h (2 lines)\n - -k (1 lines)\n - -l (1 lines)\n - -N (3 lines)\n - -P (4 lines)\n - -p (7 lines)\n - -R -R (5 lines)\n - -r (3 lines)\n - -s (2 lines)\n - -V (6 lines)\n - case, it is quite likely that the database will be damaged (1 lines)\n - record storage or retrieval. (20 lines)\n- **ENVIRONMENT** (4 lines)\n- **AUTHORS** (7 lines)\n\n## Full Content\n\n### NAME\n\ndb5.3dump - Write database to flat-text format\n\n### SYNOPSIS\n\ndb5.3dump [-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file\n\n### DESCRIPTION\n\nThe db5.3dump utility reads the database file file and writes it to the standard output us‐\ning a portable flat-text format understood by the db5.3load utility. The file argument must\nbe a file produced using the Berkeley DB library functions.\n\n### OPTIONS\n\n#### -d\n\nroutines.\n\na Display all information.\n\nh Display only page headers.\n\nr Do not display the free-list or pages on the free list. This mode is used by\nthe recovery tests.\n\nThe output format of the -d option is not standard and may change, without notice, be‐‐\ntween releases of the Berkeley DB library.\n\n#### -f\n\n#### -h\n\ndirectory is used.\n\n#### -k\n\n#### -l\n\n#### -N\n\ntially fatal errors in Berkeley DB, will be ignored as well. This option is intended\nonly for debugging errors, and should not be used under any other circumstances.\n\n#### -P\n\nstrings as soon as possible, be aware there may be a window of vulnerability on sys‐\ntems where unprivileged users can see command-line arguments or where utilities are\nnot able to overwrite the memory containing the command-line arguments.\n\n#### -p\n\nisprint(3)), use printing characters in file to represent them. This option permits\nusers to use standard text editors and tools to modify the contents of databases.\n\nNote: different systems may have different notions about what characters are consid‐\nered printing characters, and databases dumped in this manner may be less portable to\nexternal systems.\n\n#### -R -R\n\n-r option in that it will return all possible data from the file at the risk of also\nreturning already deleted or otherwise nonsensical items. Data dumped in this fashion\nwill almost certainly have to be edited by hand or other means before the data is\nready for reload into another database\n\n#### -r\n\noption should return equivalent data to a normal dump, but most likely in a different\norder.\n\n#### -s\n\ndatabase file are dumped.\n\n#### -V\n\nDumping and reloading Hash databases that use user-defined hash functions will result in new\ndatabases that use the default hash function. Although using the default hash function may\nnot be optimal for the new database, it will continue to work correctly.\n\nDumping and reloading Btree databases that use user-defined prefix or comparison functions\nwill result in new databases that use the default prefix and comparison functions. In this\n\n#### case, it is quite likely that the database will be damaged beyond repair permitting neither\n\n#### record storage or retrieval.\n\nThe only available workaround for either case is to modify the sources for the db5.3load\nutility to load the database using the correct hash, prefix, and comparison functions.\n\nThe db5.3dump utility output format is documented in the Dump Output Formats section of the\nBerkeley DB Reference Guide.\n\nThe db5.3dump utility may be used with a Berkeley DB environment (as described for the -h\noption, the environment variable DBHOME, or because the utility was run in a directory con‐\ntaining a Berkeley DB environment). In order to avoid environment corruption when using a\nBerkeley DB environment, db5.3dump should always be given the chance to detach from the en‐\nvironment and exit gracefully. To cause db5.3dump to release all environment resources and\nexit cleanly, send it an interrupt signal (SIGINT).\n\nEven when using a Berkeley DB database environment, the db5.3dump utility does not use any\nkind of database locking if it is invoked with the -d, -R, or -r arguments. If used with\none of these arguments, the db5.3dump utility may only be safely run on databases that are\nnot being modified by any other process; otherwise, the output may be corrupt.\n\nThe db5.3dump utility exits 0 on success, and >0 if an error occurs.\n\n### ENVIRONMENT\n\nDBHOME\nIf the -h option is not specified and the environment variable DBHOME is set, it is\nused as the path of the database home, as described in DBENV->open.\n\n### AUTHORS\n\nSleepycat Software, Inc. This manual page was created based on the HTML documentation for\ndbdump from Sleepycat, by Thijs Kinkhorst , for the Debian system (but\nmay be used by others).\n\n\n\n28 January 2005 DB5.3DUMP(1)\n\n" } ], "structuredContent": { "command": "DB5.3_DUMP", "section": "1", "mode": "man", "summary": "db5.3dump - Write database to flat-text format", "synopsis": "db5.3dump [-klNpRrV] [-d ahr] [-f output] [-h home] [-P password] [-s database] file", "flags": [ { "flag": "-d", "long": null, "arg": null, "description": "routines. a Display all information. h Display only page headers. r Do not display the free-list or pages on the free list. This mode is used by the recovery tests. The output format of the -d option is not standard and may change, without notice, be‐‐ tween releases of the Berkeley DB library." }, { "flag": "-f", "long": null, "arg": null, "description": "" }, { "flag": "-h", "long": null, "arg": null, "description": "directory is used." }, { "flag": "-k", "long": null, "arg": null, "description": "" }, { "flag": "-l", "long": null, "arg": null, "description": "" }, { "flag": "-N", "long": null, "arg": null, "description": "tially fatal errors in Berkeley DB, will be ignored as well. This option is intended only for debugging errors, and should not be used under any other circumstances." }, { "flag": "-P", "long": null, "arg": null, "description": "strings as soon as possible, be aware there may be a window of vulnerability on sys‐ tems where unprivileged users can see command-line arguments or where utilities are not able to overwrite the memory containing the command-line arguments." }, { "flag": "-p", "long": null, "arg": null, "description": "isprint(3)), use printing characters in file to represent them. This option permits users to use standard text editors and tools to modify the contents of databases. Note: different systems may have different notions about what characters are consid‐ ered printing characters, and databases dumped in this manner may be less portable to external systems." }, { "flag": "-R", "long": null, "arg": null, "description": "-r option in that it will return all possible data from the file at the risk of also returning already deleted or otherwise nonsensical items. Data dumped in this fashion will almost certainly have to be edited by hand or other means before the data is ready for reload into another database" }, { "flag": "-r", "long": null, "arg": null, "description": "option should return equivalent data to a normal dump, but most likely in a different order." }, { "flag": "-s", "long": null, "arg": null, "description": "database file are dumped." }, { "flag": "-V", "long": null, "arg": null, "description": "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" } ], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 4, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-d", "lines": 12, "flag": "-d" }, { "name": "-f", "lines": 1, "flag": "-f" }, { "name": "-h", "lines": 2, "flag": "-h" }, { "name": "-k", "lines": 1, "flag": "-k" }, { "name": "-l", "lines": 1, "flag": "-l" }, { "name": "-N", "lines": 3, "flag": "-N" }, { "name": "-P", "lines": 4, "flag": "-P" }, { "name": "-p", "lines": 7, "flag": "-p" }, { "name": "-R -R", "lines": 5, "flag": "-R" }, { "name": "-r", "lines": 3, "flag": "-r" }, { "name": "-s", "lines": 2, "flag": "-s" }, { "name": "-V", "lines": 6, "flag": "-V" }, { "name": "case, it is quite likely that the database will be damaged beyond repair permitting neither", "lines": 1 }, { "name": "record storage or retrieval.", "lines": 20 } ] }, { "name": "ENVIRONMENT", "lines": 4, "subsections": [] }, { "name": "AUTHORS", "lines": 7, "subsections": [] } ] } }