Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

db_dump(8) [osf1 man page]

db_dump(8)						      System Manager's Manual							db_dump(8)

NAME
db_dump, db_dump185 - Reads and writes the security databases (Enhanced Security) SYNOPSIS
/usr/tcb/bin/db_dump [-dN] [-f output] db_file /usr/tcb/bin/db_dump [-p] [-f output] [-h home] db_file /usr/tcb/bin/db_dump185 [-p] [-f output] db_file FLAGS
Dump the specified database in a format helpful for debugging the Berkeley DB library routines. The output format of the -d option is not standard and may change without notice between releases of the Berkeley DB library. Write to the specified file instead of to the standard output Specify a home directory for the database. The correct directory for enhanced security is /var/tcb/files. Do not acquire shared region locks while searching the database. This option is intended only for debugging and should not be used under any other circumstances. If characters in either the key or data items are printing characters (as defined by isprint, 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. DESCRIPTION
A customized version of the Berkeley Database (Berkeley DB) is embedded in the operating system to provide high-performance database sup- port for critical security files. The DB includes full transactional support and database recovery, using write-ahead logging and check- pointing to record changes. The db_dump utility reads the security database file db_file and writes it to the standard output using a portable flat-text format under- stood by the db_load utility. The db_dump and db_dump185 utilities are included in Tru64 UNIX for use by installation and update utilities, and are not recommended for use by system administration. The edauth utility provides a supported means of copying records from the security databases. Earlier versions of Tru64 UNIX used Version 1.85 of the Berkeley DB for enhanced security databases. So the db_dump185 utility, which 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, is included with Tru64 UNIX. Dumping and reloading hash databases that use user-defined hash functions will result in new databases that use the default hash function. While 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 a user-defined prefix or comparison functions results 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. RETURN VALUES
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. ENVIRONMENT VARIABLES
If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home. The home directory for security is /var/tcb/files. FILES
/var/tcb/files/auth.db /var/tcb/files/dblogs/* RELATED INFORMATION
Commands: edauth(8), db_load(8) delim off db_dump(8)

Check Out this Related Man Page

db_recover(8)						      System Manager's Manual						     db_recover(8)

NAME
db_recover - Restores the database to a consistent state (Enhanced Security) SYNOPSIS
/usr/tcb/bin/db_recover [-cv] [-h home] FLAGS
Failure was catastrophic. Specify a home directory for the database. The correct directory for enhanced security is /var/tcb/files. Write out the pathnames of all of the database log files, whether or not they are involved in active transactions. Run in verbose mode. DESCRIPTION
A customized version of the Berkeley Database (Berkeley DB) is embedded in the operating system to provide high-performance database sup- port for critical security files. The DB includes full transactional support and database recovery, using write-ahead logging and check- pointing to record changes. The db_recover utility runs after an unexpected system failure to restore the security database to a consistent state. All committed transactions are guaranteed to appear after db_recover has run, and all uncommitted transactions are completely undone. DB recovery is normally performed automatically for the security files as part of system startup. In the case of catastrophic failure, 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, db_recover identifies the missing log files and fails, in which case the missing log files need to be restored and recovery performed again. The db_recover utility attaches to one or more of the Berkeley DB shared memory regions. In order to avoid region corruption, it should always be given the chance to detach and exit gracefully. To cause db_recover to clean up after itself and exit, send it an interrupt sig- nal (SIGINT). RETURN VALUES
The db_recover utility exits 0 on success, and >0 if an error occurs. ENVIRONMENT VARIABLES
If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home. The home directory for security is /var/tcb/files. FILES
/var/tcb/files/auth.db /var/tcb/files/dblogs/* RELATED INFORMATION
Commands: db_archive(8), db_checkpoint(8), db_printlog(8), db_dump(8), db_load(8), db_stat(8), secconfig(8) delim off db_recover(8)
Man Page