Edit File - File Manager

Edit File: utilities.html

<html>
<head>
<title>Berkeley DB Reference Guide: Supporting utilities</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<a name="2"></a>
<table width="100%"><tr valign=top>
<td><dl><dt>Berkeley DB Reference Guide:<dd>Architecture</dl></td>
<td align=right><a href="../arch/script.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../env/intro.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Supporting utilities
The following are the standalone utilities that provide supporting
functionality for the Berkeley DB environment:
 
<a href="../../utility/berkeley_db_svc.html">berkeley_db_svc</a><ul compact><li>The <a href="../../utility/berkeley_db_svc.html">berkeley_db_svc</a> utility is the Berkeley DB RPC server that
provides standard server functionality for client applications.</ul>
<a href="../../utility/db_archive.html">db_archive</a><ul compact><li>The <a href="../../utility/db_archive.html">db_archive</a> utility supports database backup and archival,
and log file administration. It facilitates log reclamation and the
creation of database snapshots. Generally, some form of log archival
must be done if a database environment has been configured for logging
or transactions.</ul>
<a href="../../utility/db_checkpoint.html">db_checkpoint</a><ul compact><li>The <a href="../../utility/db_checkpoint.html">db_checkpoint</a> utility runs as a daemon process, monitoring
the database log and periodically issuing checkpoints. It facilitates
log reclamation and the creation of database snapshots. Generally, some
form of database checkpointing must be done if a database environment has
been configured for transactions.</ul>
<a href="../../utility/db_deadlock.html">db_deadlock</a><ul compact><li>The <a href="../../utility/db_deadlock.html">db_deadlock</a> utility runs as a daemon process, periodically
traversing the database lock structures and aborting transactions when it
detects a deadlock. Generally, some form of deadlock detection must be
done if a database environment has been configured for locking.</ul>
<a href="../../utility/db_dump.html">db_dump</a><ul compact><li>The <a href="../../utility/db_dump.html">db_dump</a> utility writes a copy of the database to a flat-text
file in a portable format.</ul>
<a href="../../utility/db_load.html">db_load</a><ul compact><li>The <a href="../../utility/db_load.html">db_load</a> utility reads the flat-text file produced by
<a href="../../utility/db_dump.html">db_dump</a> and loads it into a database file.</ul>
<a href="../../utility/db_printlog.html">db_printlog</a><ul compact><li>The <a href="../../utility/db_printlog.html">db_printlog</a> utility displays the contents of Berkeley DB log files
in a human-readable and parsable format.</ul>
<a href="../../utility/db_recover.html">db_recover</a><ul compact><li>The <a href="../../utility/db_recover.html">db_recover</a> utility runs after an unexpected Berkeley DB or system
failure to restore the database to a consistent state. Generally, some
form of database recovery must be done if databases are being modified.</ul>
<a href="../../utility/db_stat.html">db_stat</a> <ul compact><li>The <a href="../../utility/db_stat.html">db_stat</a> utility displays statistics for databases and database
environments.</ul>
<a href="../../utility/db_upgrade.html">db_upgrade</a><ul compact><li>The <a href="../../utility/db_upgrade.html">db_upgrade</a> utility provides a command-line interface for
upgrading underlying database formats.</ul>
<a href="../../utility/db_verify.html">db_verify</a><ul compact><li>The <a href="../../utility/db_verify.html">db_verify</a> utility provides a command-line interface for
verifying the database format.</ul>
 
All of the functionality implemented for these utilities is also available
as part of the standard Berkeley DB API. This means that threaded applications
can easily create a thread that calls the same Berkeley DB functions as do the
utilities. This often simplifies an application environment by removing
the necessity for multiple processes to negotiate database and database
environment creation and shut down.
<table width="100%"><tr><td> </td><td align=right><a href="../arch/script.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../env/intro.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager