{ "mode": "man", "parameter": "db_recover", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/db_recover/1/json", "generated": "2026-06-15T14:27:15Z", "synopsis": "db5.3recover [-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]]", "sections": { "NAME": { "content": "db5.3recover - Restore the database to a consistent state\n", "subsections": [] }, "SYNOPSIS": { "content": "db5.3recover [-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]]\n", "subsections": [] }, "DESCRIPTION": { "content": "The db5.3recover utility must be run after an unexpected application, Berkeley DB, or system\nfailure to restore the database to a consistent state. All committed transactions are guaran‐\nteed to appear after db5.3recover has run, and all uncommitted transactions will be com‐\npletely undone.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-c", "content": "", "flag": "-c" }, { "name": "-e", "content": "a DBCONFIG file is present in the home directory. If a DBCONFIG file is not\npresent, then the regions will be created with default parameter values.\n", "flag": "-e" }, { "name": "-h", "content": "directory is used.\n", "flag": "-h" }, { "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": "-t", "content": "timestamp argument should be in the form [[CC]YY]MMDDhhmm[.SS] where each pair of let‐\nters represents the following:\n\nCC The first two digits of the year (the century).\n\nYY The second two digits of the year. If \"YY\" is specified, but \"CC\" is not, a\nvalue for \"YY\" between 69 and 99 results in a \"CC\" value of 19. Otherwise, a\n\"YY\" value of 20 is used.\n\nMM The month of the year, from 1 to 12.\n\nDD The day of the month, from 1 to 31.\n\nhh The hour of the day, from 0 to 23.\n\nmm The minute of the hour, from 0 to 59.\n\nSS The second of the minute, from 0 to 61.\n\nIf the \"CC\" and \"YY\" letter pairs are not specified, the values default to the current\nyear. If the \"SS\" letter pair is not specified, the value defaults to 0.\n", "flag": "-t" }, { "name": "-V", "content": "", "flag": "-V" }, { "name": "-v", "content": "In the case of catastrophic recovery, an archival copy - or snapshot - of all database files\nmust be restored along with all of the log files written since the database file snapshot was\nmade. (If disk space is a problem, log files may be referenced by symbolic links).\n\nIf the failure was not catastrophic, the files present on the system at the time of failure\nare sufficient to perform recovery.\n\nIf log files are missing, db5.3recover will identify the missing log file(s) and fail, in\nwhich case the missing log files need to be restored and recovery performed again.\n\nThe db5.3recover utility uses a Berkeley DB environment (as described for the -h option, the\nenvironment variable DBHOME, or because the utility was run in a directory containing a\nBerkeley DB environment). In order to avoid environment corruption when using a Berkeley DB\nenvironment, db5.3recover should always be given the chance to detach from the environment\nand exit gracefully. To cause db5.3recover to release all environment resources and exit\ncleanly, send it an interrupt signal (SIGINT).\n\nThe db5.3recover utility exits 0 on success, and >0 if an error occurs.\n", "flag": "-v" } ] }, "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\ndbrecover from Sleepycat, by Thijs Kinkhorst , for the Debian system\n(but may be used by others).\n\n\n\n28 January 2005 DB5.3RECOVER(1)", "subsections": [] } }, "summary": "db5.3recover - Restore the database to a consistent state", "flags": [ { "flag": "-c", "long": null, "arg": null, "description": "" }, { "flag": "-e", "long": null, "arg": null, "description": "a DBCONFIG file is present in the home directory. If a DBCONFIG file is not present, then the regions will be created with default parameter values." }, { "flag": "-h", "long": null, "arg": null, "description": "directory is used." }, { "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": "-t", "long": null, "arg": null, "description": "timestamp argument should be in the form [[CC]YY]MMDDhhmm[.SS] where each pair of let‐ ters represents the following: CC The first two digits of the year (the century). YY The second two digits of the year. If \"YY\" is specified, but \"CC\" is not, a value for \"YY\" between 69 and 99 results in a \"CC\" value of 19. Otherwise, a \"YY\" value of 20 is used. MM The month of the year, from 1 to 12. DD The day of the month, from 1 to 31. hh The hour of the day, from 0 to 23. mm The minute of the hour, from 0 to 59. SS The second of the minute, from 0 to 61. If the \"CC\" and \"YY\" letter pairs are not specified, the values default to the current year. If the \"SS\" letter pair is not specified, the value defaults to 0." }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "-v", "long": null, "arg": null, "description": "In the case of catastrophic recovery, an archival copy - or snapshot - of all database files must be restored along with all of the log files written since the database file snapshot was made. (If disk space is a problem, log files may be referenced by symbolic links). If the failure was not catastrophic, the files present on the system at the time of failure are sufficient to perform recovery. If log files are missing, db5.3recover will identify the missing log file(s) and fail, in which case the missing log files need to be restored and recovery performed again. The db5.3recover utility uses a Berkeley DB environment (as described for the -h option, the environment variable DBHOME, 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, db5.3recover should always be given the chance to detach from the environment and exit gracefully. To cause db5.3recover to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). The db5.3recover utility exits 0 on success, and >0 if an error occurs." } ], "examples": [], "see_also": [] }