1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Supporting utilities</title>
<link rel="stylesheet" href="gettingStarted.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
<link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" />
<link rel="up" href="arch.html" title="Chapter 8. Berkeley DB Architecture" />
<link rel="prev" href="arch_script.html" title="Scripting languages" />
<link rel="next" href="env.html" title="Chapter 9. The Berkeley DB Environment" />
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Supporting utilities</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="arch_script.html">Prev</a> </td>
<th width="60%" align="center">Chapter 8.
Berkeley DB Architecture
</th>
<td width="20%" align="right"> <a accesskey="n" href="env.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="arch_utilities"></a>Supporting utilities</h2>
</div>
</div>
</div>
<p>The following are the standalone utilities that provide supporting
functionality for the Berkeley DB environment:</p>
<div class="variablelist">
<dl>
<dt>
<span class="term">
<a href="../api_reference/C/db_archive.html" class="olink">db_archive utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_archive.html" class="olink">db_archive utility</a> 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.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_checkpoint.html" class="olink">db_checkpoint utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_checkpoint.html" class="olink">db_checkpoint utility</a> 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.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_deadlock.html" class="olink">db_deadlock utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_deadlock.html" class="olink">db_deadlock utility</a> 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.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_dump.html" class="olink">db_dump utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_dump.html" class="olink">db_dump utility</a> writes a copy of the database to a flat-text file in a portable format.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_hotbackup.html" class="olink">db_hotbackup utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_hotbackup.html" class="olink">db_hotbackup utility</a> creates "hot backup" or "hot failover"
snapshots of Berkeley DB database environments.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_load.html" class="olink">db_load utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_load.html" class="olink">db_load utility</a> reads the flat-text file produced by the <a href="../api_reference/C/db_load.html" class="olink">db_load utility</a> and loads it into a database file.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_printlog.html" class="olink">db_printlog utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_printlog.html" class="olink">db_printlog utility</a> displays the contents of Berkeley DB log files in a human-readable and parsable format.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_recover.html" class="olink">db_recover utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_recover.html" class="olink">db_recover utility</a> 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.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_sql.html" class="olink">db_sql utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_sql.html" class="olink">db_sql utility</a> translates a
schema description written in a SQL Data Definition Language dialect
into C code that implements the schema using Berkeley DB.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_stat.html" class="olink">db_stat utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_stat.html" class="olink">db_stat utility</a> displays statistics for databases and database
environments.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_upgrade.html" class="olink">db_upgrade utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_upgrade.html" class="olink">db_upgrade utility</a> provides a command-line interface for upgrading underlying database formats.</dd>
<dt>
<span class="term">
<a href="../api_reference/C/db_verify.html" class="olink">db_verify utility</a>
</span>
</dt>
<dd>The <a href="../api_reference/C/db_verify.html" class="olink">db_verify utility</a> provides a command-line interface for verifying the database format.</dd>
</dl>
</div>
<p>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.</p>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="arch_script.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="arch.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="env.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Scripting languages </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Chapter 9.
The Berkeley DB Environment
</td>
</tr>
</table>
</div>
</body>
</html>
|
