source: server/databases/db.xml@ 33c9d33

10.0 10.1 11.0 11.1 11.2 11.3 12.0 12.1 7.10 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind kea ken/TL2024 ken/inkscape-core-mods ken/tuningfonts lazarus lxqt nosym perl-modules plabs/newcss plabs/python-mods python3.11 qt5new rahul/power-profiles-daemon renodr/vulkan-addition trunk upgradedb xry111/intltool xry111/llvm18 xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 33c9d33 was 33c9d33, checked in by Bruce Dubbs <bdubbs@…>, 9 years ago

Tags

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