{ "mode": "man", "parameter": "db5.3_archive", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/db5.3_archive/1/json", "generated": "2026-05-30T05:15:24Z", "synopsis": "db5.3archive [-adlsVv] [-h home] [-P password]", "sections": { "NAME": { "content": "db5.3archive - Find unused log files for archiving purposes\n", "subsections": [] }, "SYNOPSIS": { "content": "db5.3archive [-adlsVv] [-h home] [-P password]\n", "subsections": [] }, "DESCRIPTION": { "content": "The db5.3archive utility writes the pathnames of log files that are no longer in use (for\nexample, no longer involved in active transactions), to the standard output, one pathname per\nline. These log files should be written to backup media to provide for recovery in the case\nof catastrophic failure (which also requires a snapshot of the database files), but they may\nthen be deleted from the system to reclaim disk space.\n", "subsections": [] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-a", "content": "directories.\n", "flag": "-a" }, { "name": "-d", "content": "file removal is likely to make catastrophic recovery impossible.\n", "flag": "-d" }, { "name": "-h", "content": "directory is used.\n", "flag": "-h" }, { "name": "-l", "content": "volved in active transactions.\n", "flag": "-l" }, { "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": "cover the database from catastrophic failure. If any of the database files have not\nbeen accessed during the lifetime of the current log files, db5.3archive will not in‐\nclude them in this output.\n\nIt is possible that some of the files to which the log refers have since been deleted\nfrom the system. In this case, db5.3archive will ignore them. When db5.3recover is\nrun, any files to which the log refers that are not present during recovery are as‐\nsumed to have been deleted and will not be recovered.\n", "flag": "-s" }, { "name": "-V", "content": "", "flag": "-V" }, { "name": "-v", "content": "Log cursor handles (returned by the DBENV->logcursor method) may have open file descriptors\nfor log files in the database environment. Also, the Berkeley DB interfaces to the database\nenvironment logging subsystem (for example, DBENV->logput and DBTXN->abort) may allocate\nlog cursors and have open file descriptors for log files as well. On operating systems where\nfilesystem related system calls (for example, rename and unlink on Windows/NT) can fail if a\nprocess has an open file descriptor for the affected file, attempting to move or remove the\nlog files listed by db5.3archive may fail. All Berkeley DB internal use of log cursors op‐\nerates on active log files only and furthermore, is short-lived in nature. So, an applica‐\ntion seeing such a failure should be restructured to close any open log cursors it may have,\nand otherwise to retry the operation until it succeeds. (Although the latter is not likely\nto be necessary; it is hard to imagine a reason to move or rename a log file in which trans‐\nactions are being logged or aborted.)\n\nThe db5.3archive 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.3archive should always be given the chance to detach from the environment\nand exit gracefully. To cause db5.3archive to release all environment resources and exit\ncleanly, send it an interrupt signal (SIGINT).\n\nThe DBENV->logarchive method is the underlying method used by the db5.3archive utility.\nSee the db5.3archive utility source code for an example of using DBENV->logarchive in a\nIEEE/ANSI Std 1003.1 (POSIX) environment.\n\nThe db5.3archive 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\ndbarchive from Sleepycat, by Thijs Kinkhorst , for the Debian system\n(but may be used by others).\n\n\n\n28 January 2005 DB5.3ARCHIVE(1)", "subsections": [] } }, "summary": "db5.3archive - Find unused log files for archiving purposes", "flags": [ { "flag": "-a", "long": null, "arg": null, "description": "directories." }, { "flag": "-d", "long": null, "arg": null, "description": "file removal is likely to make catastrophic recovery impossible." }, { "flag": "-h", "long": null, "arg": null, "description": "directory is used." }, { "flag": "-l", "long": null, "arg": null, "description": "volved in active transactions." }, { "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": "cover the database from catastrophic failure. If any of the database files have not been accessed during the lifetime of the current log files, db5.3archive will not in‐ clude them in this output. It is possible that some of the files to which the log refers have since been deleted from the system. In this case, db5.3archive will ignore them. When db5.3recover is run, any files to which the log refers that are not present during recovery are as‐ sumed to have been deleted and will not be recovered." }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "-v", "long": null, "arg": null, "description": "Log cursor handles (returned by the DBENV->logcursor method) may have open file descriptors for log files in the database environment. Also, the Berkeley DB interfaces to the database environment logging subsystem (for example, DBENV->logput and DBTXN->abort) may allocate log cursors and have open file descriptors for log files as well. On operating systems where filesystem related system calls (for example, rename and unlink on Windows/NT) can fail if a process has an open file descriptor for the affected file, attempting to move or remove the log files listed by db5.3archive may fail. All Berkeley DB internal use of log cursors op‐ erates on active log files only and furthermore, is short-lived in nature. So, an applica‐ tion seeing such a failure should be restructured to close any open log cursors it may have, and otherwise to retry the operation until it succeeds. (Although the latter is not likely to be necessary; it is hard to imagine a reason to move or rename a log file in which trans‐ actions are being logged or aborted.) The db5.3archive 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.3archive should always be given the chance to detach from the environment and exit gracefully. To cause db5.3archive to release all environment resources and exit cleanly, send it an interrupt signal (SIGINT). The DBENV->logarchive method is the underlying method used by the db5.3archive utility. See the db5.3archive utility source code for an example of using DBENV->logarchive in a IEEE/ANSI Std 1003.1 (POSIX) environment. The db5.3archive utility exits 0 on success, and >0 if an error occurs." } ], "examples": [], "see_also": [] }