source: server/databases/db.xml@ 6d85d2c1

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts krejzi/svn lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition systemd-11177 systemd-13485 trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 6d85d2c1 was 6d85d2c1, checked in by Andrew Benton <andy@…>, 12 years ago

Bruce please check the book validates before you commit your changes

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@10109 af4574ff-66df-0310-9fd7-8a98e5e911e0
  • Property mode set to 100644
File size: 14.4 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY db-download-http
8 "http://download.oracle.com/berkeley-db/db-&db-version;.tar.gz">
9 <!ENTITY db-download-ftp "&gentoo-ftp-repo;/db-&db-version;.tar.gz">
10 <!ENTITY db-md5sum "5493fb5f7cc3915887c836b096f18773">
11 <!ENTITY db-size "33 MB">
12 <!ENTITY db-buildsize "264 MB (additional 100 MB to run parallel standard
13 test suite)">
14 <!ENTITY db-time "0.8 SBU (add an additional 145 SBU to run parallel
15 standard test suite)">
16]>
17
18<sect1 id="db" xreflabel="Berkeley DB-&db-version;">
19 <?dbhtml filename="db.html"?>
20
21 <sect1info>
22 <othername>$LastChangedBy$</othername>
23 <date>$Date$</date>
24 </sect1info>
25
26 <title>Berkeley DB-&db-version;</title>
27
28 <indexterm zone="db">
29 <primary sortas="a-Berkeley-DB">Berkeley DB</primary>
30 </indexterm>
31
32 <sect2 role="package">
33 <title>Introduction to Berkeley DB</title>
34
35 <para>
36 The <application>Berkeley DB</application> package contains programs and
37 utilities used by many other applications for database related functions.
38 </para>
39
40 &lfs71_checked;
41
42 <bridgehead renderas="sect3">Package Information</bridgehead>
43 <itemizedlist spacing="compact">
44 <listitem>
45 <para>
46 Download (HTTP): <ulink url="&db-download-http;"/>
47 </para>
48 </listitem>
49 <listitem>
50 <para>
51 Download (FTP): <ulink url="&db-download-ftp;"/>
52 </para>
53 </listitem>
54 <listitem>
55 <para>
56 Download MD5 sum: &db-md5sum;
57 </para>
58 </listitem>
59 <listitem>
60 <para>
61 Download size: &db-size;
62 </para>
63 </listitem>
64 <listitem>
65 <para>
66 Estimated disk space required: &db-buildsize;
67 </para>
68 </listitem>
69 <listitem>
70 <para>
71 Estimated build time: &db-time;
72 </para>
73 </listitem>
74 </itemizedlist>
75
76 <bridgehead renderas="sect3">Berkeley DB Dependencies</bridgehead>
77
78 <bridgehead renderas="sect4">Optional</bridgehead>
79 <para role="optional">
80 <xref linkend="tcl"/>,
81 <xref linkend="icedtea6"/><!-- or <xref linkend="jdk"/>-->, and
82 <xref linkend="sharutils"/> (for the <command>uudecode</command> command)
83 </para>
84
85 <para condition="html" role="usernotes">
86 User Notes: <ulink url="&blfs-wiki;/db"/>
87 </para>
88 </sect2>
89
90 <sect2 role="testing">
91 <title>Testing Berkeley DB</title>
92
93 <para>
94 If you can't wait 12 hours or so you may want to skip ahead to
95 <xref linkend="bdb-installation"/>. The test suite can take a long time
96 and has a few bugs causing a report of <quote>Regression tests
97 failed</quote>. However, running the test suite is a very exhaustive test
98 of your hardware, perhaps pushing your machine harder (especially disk
99 I/O) than it will ever see during production use. Note that you must have
100 <application>Tcl</application> installed to run the test suite.
101 </para>
102
103 <para>
104 Build for the <application>Berkeley DB</application> test by running the
105 following commands:
106 </para>
107
108<screen><userinput>cd build_unix &amp;&amp;
109../dist/configure --prefix=/usr \
110 --enable-test \
111 --enable-tcl \
112 --enable-dbm \
113 --with-tcl=/usr/lib &amp;&amp;
114make</userinput></screen>
115
116 <para>
117 To test the results, start <command>tclsh</command>:
118 </para>
119
120<screen><userinput>tclsh</userinput></screen>
121
122 <para>
123 From the <command>tclsh</command> prompt (<prompt>%&nbsp;</prompt>), run:
124 </para>
125
126<screen><userinput>source ../test/tcl/test.tcl
127run_parallel 5 run_std
128exit</userinput></screen>
129
130 <para>
131 Clean up the source tree with the following command:
132 </para>
133
134<screen><userinput>make realclean &amp;&amp;
135cd ..</userinput></screen>
136
137 <note><para>
138 Test127.f and Repmgr026.c are known to fail.
139 </para></note>
140
141 <para>
142 There are additional testing suites in the
143 <filename class="directory">test/c</filename> and
144 <filename class="directory">test/cxx</filename> directories. See the
145 <filename>README</filename> in each directory for instructions on how to
146 run the tests.
147 </para>
148 </sect2>
149
150 <sect2 role="installation" id="bdb-installation">
151 <title>Installation of Berkeley DB</title>
152
153 <note>
154 <para>
155 If you plan on installing <application>Berkeley DB</application> with
156 Java support, you should check the system for certain versions of
157 <!-- <xref linkend="jdk"/> and--> <xref linkend="gmime"/>. Specifically, if
158 <application>JDK</application>-6 Update X and the
159 <command>uudecode</command> program from the
160 <application>GMime</application> program is on the system, the build
161 will fail (unless you run the modified <command>./configure</command>
162 command shown below). You can run two commands
163 (<command>javac -version</command> and
164 <command>uudecode --version</command>) to determine what versions are
165 installed. You can also download and run a shell script from
166 <ulink url="&files-anduin;/jdk-uudecode-check.sh"/> that will alert you
167 to a non-working condition. If the identified programs exist on the
168 system, you must modify the <command>./configure</command> command as
169 shown below.
170 </para>
171
172<screen><userinput>uudecode="no" ../dist/configure --(use the parameters shown below)</userinput></screen>
173 </note>
174
175 <para>
176 Install <application>Berkeley DB</application> by running the following
177 commands:
178 </para>
179
180<screen><userinput>cd build_unix &amp;&amp;
181../dist/configure --prefix=/usr \
182 --enable-compat185 \
183 --enable-dbm \
184 --disable-static \
185 --enable-cxx &amp;&amp;
186make</userinput></screen>
187
188 <para>
189 Now, as the <systemitem class="username">root</systemitem> user:
190 </para>
191
192<screen role="root"><userinput>make docdir=/usr/share/doc/db-&db-version; install &amp;&amp;
193chown -v -R root:root \
194 /usr/bin/db_* \
195 /usr/include/db{,_185,_cxx}.h \
196 /usr/lib/libdb*.{so,la} \
197 /usr/share/doc/db-&db-version;</userinput></screen>
198 </sect2>
199
200 <sect2 role="commands">
201 <title>Command Explanations</title>
202
203 <para>
204 <command>cd build_unix &amp;&amp; ../dist/configure
205 --prefix=/usr...</command>: This replaces the normal
206 <command>./configure</command> command, as
207 <application>Berkeley DB</application> comes with various build
208 directories for different platforms.
209 </para>
210
211 <para>
212 <parameter>--enable-compat185</parameter>: This switch enables building
213 the DB-1.85 compatibility API.
214 </para>
215
216 <para>
217 <parameter>--enable-cxx</parameter>: This switch enables building C++ API
218 libraries.
219 </para>
220
221 <para>
222 <parameter>--enable-tcl --with-tcl=/usr/lib</parameter>: Enables
223 <application>Tcl</application> support in DB and creates the
224 <filename class="libraryfile">libdb_tcl</filename> libraries.
225 </para>
226
227 <para>
228 <parameter>--enable-dbm</parameter>: Enables legacy interface support
229 needed by some older packages.
230 </para>
231
232 <para>
233 <parameter>--enable-java</parameter>: Enables
234 <application>Java</application> support in DB and creates the
235 <filename class="libraryfile">libdb_java</filename> libraries.
236 </para>
237
238 <para>
239 <command>make docdir=/usr/share/doc/db-&db-version; install</command>:
240 This installs the documentation in the standard location instead of
241 <filename class="directory">/usr/docs</filename>.
242 </para>
243
244 <para>
245 <command>chown -v -R root:root ...</command>:This command changes the
246 ownership of various installed files from the uid:gid of the builder to
247 root:root.
248 </para>
249 </sect2>
250
251 <sect2 role="content">
252 <title>Contents</title>
253
254 <segmentedlist>
255 <segtitle>Installed Programs</segtitle>
256 <segtitle>Installed Libraries</segtitle>
257 <segtitle>Installed Directory</segtitle>
258
259 <seglistitem>
260 <seg>
261 db_archive, db_checkpoint, db_deadlock, db_dump, db_hotbackup,
262 db_load, db_log_verify, db_printlog, db_recover, db_replicate,
263 db_stat, db_tuner, db_upgrade and db_verify.
264 </seg>
265 <seg>
266 libdb.so, libdb_cxx.so, libdb_java.so, libdb_tcl.so and db.jar.
267 </seg>
268 <seg>/usr/share/doc/db-&db-version;</seg>
269 </seglistitem>
270 </segmentedlist>
271
272 <variablelist>
273 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
274 <?dbfo list-presentation="list"?>
275 <?dbhtml list-presentation="table"?>
276
277 <varlistentry id="db_archive">
278 <term><command>db_archive</command></term>
279 <listitem>
280 <para>
281 prints the pathnames of log files that are no longer in use.
282 </para>
283 <indexterm zone="db db_archive">
284 <primary sortas="b-db_archive">db_archive</primary>
285 </indexterm>
286 </listitem>
287 </varlistentry>
288
289 <varlistentry id="db_checkpoint">
290 <term><command>db_checkpoint</command></term>
291 <listitem>
292 <para>
293 is a daemon process used to monitor and checkpoint database logs.
294 </para>
295 <indexterm zone="db db_checkpoint">
296 <primary sortas="b-db_checkpoint">db_checkpoint</primary>
297 </indexterm>
298 </listitem>
299 </varlistentry>
300
301 <varlistentry id="db_deadlock">
302 <term><command>db_deadlock</command></term>
303 <listitem>
304 <para>
305 is used to abort lock requests when deadlocks are detected.
306 </para>
307 <indexterm zone="db db_deadlock">
308 <primary sortas="b-db_deadlock">db_deadlock</primary>
309 </indexterm>
310 </listitem>
311 </varlistentry>
312
313 <varlistentry id="db_dump">
314 <term><command>db_dump</command></term>
315 <listitem>
316 <para>
317 converts database files to a flat file format readable by
318 <command>db_load</command>.
319 </para>
320 <indexterm zone="db db_dump">
321 <primary sortas="b-db_dump">db_dump</primary>
322 </indexterm>
323 </listitem>
324 </varlistentry>
325
326 <varlistentry id="db_hotbackup">
327 <term><command>db_hotbackup</command></term>
328 <listitem>
329 <para>
330 creates "hot backup" or "hot failover" snapshots of Berkeley DB
331 databases.
332 </para>
333 <indexterm zone="db db_hotbackup">
334 <primary sortas="b-db_hotbackup">db_hotbackup</primary>
335 </indexterm>
336 </listitem>
337 </varlistentry>
338
339 <varlistentry id="db_load">
340 <term><command>db_load</command></term>
341 <listitem>
342 <para>
343 is used to create database files from flat files created with
344 <command>db_dump</command>.
345 </para>
346 <indexterm zone="db db_load">
347 <primary sortas="b-db_load">db_load</primary>
348 </indexterm>
349 </listitem>
350 </varlistentry>
351
352 <varlistentry id="db_log_verify">
353 <term><command>db_log_verify</command></term>
354 <listitem>
355 <para>verifies the log files of a database.</para>
356 <indexterm zone="db db_log_verify">
357 <primary sortas="b-db_log_verify">db_log_verify</primary>
358 </indexterm>
359 </listitem>
360 </varlistentry>
361
362 <varlistentry id="db_printlog">
363 <term><command>db_printlog</command></term>
364 <listitem>
365 <para>converts database log files to human readable text.</para>
366 <indexterm zone="db db_printlog">
367 <primary sortas="b-db_printlog">db_printlog</primary>
368 </indexterm>
369 </listitem>
370 </varlistentry>
371
372 <varlistentry id="db_recover">
373 <term><command>db_recover</command></term>
374 <listitem>
375 <para>
376 is used to restore a database to a consistent state after a failure.
377 </para>
378 <indexterm zone="db db_recover">
379 <primary sortas="b-db_recover">db_recover</primary>
380 </indexterm>
381 </listitem>
382 </varlistentry>
383
384 <varlistentry id="db_replicate">
385 <term><command>db_replicate</command></term>
386 <listitem>
387 <para>
388 is a daemon process that provides replication/HA services on a
389 transactional environment.
390 </para>
391 <indexterm zone="db db_replicate">
392 <primary sortas="b-db_replicate">db_replicate</primary>
393 </indexterm>
394 </listitem>
395 </varlistentry>
396
397 <varlistentry id="db_stat">
398 <term><command>db_stat</command></term>
399 <listitem>
400 <para>displays database environment statistics.</para>
401 <indexterm zone="db db_stat">
402 <primary sortas="b-db_stat">db_stat</primary>
403 </indexterm>
404 </listitem>
405 </varlistentry>
406
407 <varlistentry id="db_tuner">
408 <term><command>db_tuner</command></term>
409 <listitem>
410 <para>
411 analyzes the data in a btree database, and suggests a page size that
412 is likely to deliver optimal operation.
413 </para>
414 <indexterm zone="db db_tuner">
415 <primary sortas="b-db_tuner">db_tuner</primary>
416 </indexterm>
417 </listitem>
418 </varlistentry>
419
420 <varlistentry id="db_upgrade">
421 <term><command>db_upgrade</command></term>
422 <listitem>
423 <para>
424 is used to upgrade database files to a newer version of
425 <application>Berkeley DB</application>.
426 </para>
427 <indexterm zone="db db_upgrade">
428 <primary sortas="b-db_upgrade">db_upgrade</primary>
429 </indexterm>
430 </listitem>
431 </varlistentry>
432
433 <varlistentry id="db_verify">
434 <term><command>db_verify</command></term>
435 <listitem>
436 <para>is used to run consistency checks on database files.</para>
437 <indexterm zone="db db_verify">
438 <primary sortas="b-db_verify">db_verify</primary>
439 </indexterm>
440 </listitem>
441 </varlistentry>
442 </variablelist>
443 </sect2>
444</sect1>
Note: See TracBrowser for help on using the repository browser.