{ "content": [ { "type": "text", "text": "# db_upgrade (man)\n\n## NAME\n\ndb5.3upgrade - Upgrade the Berkeley DB version to the current release version.\n\n## SYNOPSIS\n\ndb5.3upgrade [-NsVv] [-h home] [-P password] file ...\n\n## DESCRIPTION\n\nThe db5.3upgrade utility upgrades the Berkeley DB version of one or more files and the data‐\nbases they contain to the current release version.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (7 subsections)\n- **ENVIRONMENT**\n- **AUTHORS**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "db_upgrade", "section": "", "mode": "man", "summary": "db5.3upgrade - Upgrade the Berkeley DB version to the current release version.", "synopsis": "db5.3upgrade [-NsVv] [-h home] [-P password] file ...", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [ { "flag": "-h", "long": null, "arg": null, "description": "directory is used." }, { "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": "-s", "long": null, "arg": null, "description": "ley DB 3.1 release. As part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release, the on- disk format of duplicate data items changed. To correctly upgrade the format requires that applications specify whether duplicate data items in the database are sorted or not. Specifying the -s flag means that the duplicates are sorted; otherwise, they are assumed to be unsorted. Incorrectly specifying the value of this flag may lead to database corruption. Because the db5.3upgrade utility upgrades a physical file (including all the data‐ bases it contains), it is not possible to use db5.3upgrade to upgrade files where some of the databases it includes have sorted duplicate data items, and some of the databases it includes have unsorted duplicate data items. If the file does not have more than a single database, if the databases do not support duplicate data items, or if all the databases that support duplicate data items support the same style of du‐ plicates (either sorted or unsorted), db5.3upgrade will work correctly as long as the -s flag is correctly specified. Otherwise, the file cannot be upgraded using db5.3up‐ grade, and must be upgraded manually using the db5.3dump and db5.0load utilities." }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "-v", "long": null, "arg": null, "description": "" } ], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 3, "subsections": [] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-h", "lines": 2, "flag": "-h" }, { "name": "-N", "lines": 3, "flag": "-N" }, { "name": "-P", "lines": 4, "flag": "-P" }, { "name": "-s", "lines": 19, "flag": "-s" }, { "name": "-V", "lines": 1, "flag": "-V" }, { "name": "-v", "lines": 1, "flag": "-v" }, { "name": "It is important to realize that Berkeley DB database upgrades are done in place, and so are", "lines": 13 } ] }, { "name": "ENVIRONMENT", "lines": 4, "subsections": [] }, { "name": "AUTHORS", "lines": 7, "subsections": [] } ], "sections": { "NAME": { "content": "db5.3upgrade - Upgrade the Berkeley DB version to the current release version.\n", "subsections": [] }, "SYNOPSIS": { "content": "db5.3upgrade [-NsVv] [-h home] [-P password] file ...\n", "subsections": [] }, "DESCRIPTION": { "content": "The db5.3upgrade utility upgrades the Berkeley DB version of one or more files and the data‐\nbases they contain to the current release version.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-h", "content": "directory is used.\n", "flag": "-h" }, { "name": "-N", "content": "tially 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", "flag": "-N" }, { "name": "-P", "content": "strings 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", "flag": "-P" }, { "name": "-s", "content": "ley DB 3.1 release.\n\nAs part of the upgrade from the Berkeley DB 3.0 release to the 3.1 release, the on-\ndisk format of duplicate data items changed. To correctly upgrade the format requires\nthat applications specify whether duplicate data items in the database are sorted or\nnot. Specifying the -s flag means that the duplicates are sorted; otherwise, they are\nassumed to be unsorted. Incorrectly specifying the value of this flag may lead to\ndatabase corruption.\n\nBecause the db5.3upgrade utility upgrades a physical file (including all the data‐\nbases it contains), it is not possible to use db5.3upgrade to upgrade files where\nsome of the databases it includes have sorted duplicate data items, and some of the\ndatabases it includes have unsorted duplicate data items. If the file does not have\nmore than a single database, if the databases do not support duplicate data items, or\nif all the databases that support duplicate data items support the same style of du‐\nplicates (either sorted or unsorted), db5.3upgrade will work correctly as long as the\n-s flag is correctly specified. Otherwise, the file cannot be upgraded using db5.3up‐\ngrade, and must be upgraded manually using the db5.3dump and db5.0load utilities.\n", "flag": "-s" }, { "name": "-V", "content": "", "flag": "-V" }, { "name": "-v", "content": "", "flag": "-v" }, { "name": "It is important to realize that Berkeley DB database upgrades are done in place, and so are", "content": "potentially destructive. This means that if the system crashes during the upgrade procedure,\nor if the upgrade procedure runs out of disk space, the databases may be left in an inconsis‐\ntent and unrecoverable state.\n\nThe db5.3upgrade 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.3upgrade should always be given the chance to detach from the\nenvironment and exit gracefully. To cause db5.3upgrade to release all environment resources\nand exit cleanly, send it an interrupt signal (SIGINT).\n\nThe db5.3upgrade utility exits 0 on success, and >0 if an error occurs.\n" } ] }, "ENVIRONMENT": { "content": "DBHOME\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", "subsections": [] }, "AUTHORS": { "content": "Sleepycat Software, Inc. This manual page was created based on the HTML documentation for\ndbupgrade from Sleepycat, by Thijs Kinkhorst , for the Debian system\n(but may be used by others).\n\n\n\n28 January 2005 DB5.3UPGRADE(1)", "subsections": [] } } } }