LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-09-25 16:24:41 +00:00
parent c2ceb8c9fd
commit 9f31200171
3 changed files with 205 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

222
LDP/howto/docbook/DB2-HOWTO.sgml
View File

@ -8,6 +8,13 @@
<author><firstname>Dan</firstname><surname>Scott</surname></author>
<authorinitials>dbs</authorinitials>
<revhistory>
<revision>
<revnumber>1.2</revnumber>
<date>September 25, 2000</date>
<authorinitials>dbs</authorinitials>
<revremark>IBM JDK 1.3 works! More troubleshooting.
</revremark>
</revision>
<revision>
<revnumber>1.1</revnumber>
<date>July 28, 2000</date>
@ -134,17 +141,18 @@ TurboLinux 6.0
</para>
<para>
For Debian, I have included <emphasis>very</emphasis> basic installation
instructions in <xref linkend="xfactor">. If you have any
For Debian and Slackware, I have included <emphasis>very</emphasis> basic installation
instructions or links to other resources in <xref linkend="xfactor">. If you have any
other installation success stories, please forward me the details
and I'll try to expand the section. As time permits, I plan to try
to duplicate and confirm these installation instructions.
</para>
<para>
If you plan to install DB2 Version 6.1 on Linux, I'll try to track down
some references for you, but I don't include any DB2 Version 6.1
information here. If you plan to install DB2 Version 5.2 on Linux,
If you install DB2 Version 6.1 for Linux and DB2 hangs on the
<command>db2start</command> command, see
<ulink url="http://www-1.ibm.com/servlet/support/manager?rt=0&amp;rs=0&amp;org=swg&amp;doc=852568E5006F0CC68525693E00535FB3">db2start hangs on Linux distributions built with glibc 2.1</ulink>. I don't include any other DB2 Version 6.1
information in this document. If you plan to install DB2 Version 5.2 on Linux,
<emphasis>don't</emphasis>! (Have I emphasized that point enough?
All right, I'll stop now.) The Personal Developer's Edition
of DB2 Version 7.1 is available as a free (beer) download from IBM, at the
@ -369,7 +377,7 @@ without using RPM, see <xref linkend="xfactor">.
<term>Java</term>
<listitem>
<para>
The IBM Developer Kit for Java <literal>1.1.8</literal> is an
The IBM Developer Kit for Java, <literal>1.1.8</literal> or <literal>1.3</literal>, is an
optional component, but is required to:
<itemizedlist>
<listitem>
@ -391,9 +399,18 @@ and user-defined functions
As of this writing, the minimum required level of the
IBM Developer Kit for Java is the March 22, 2000 release.
You can get the IBM Developer Kit and Runtime Environment
for Linux, Java Technology Edition, Version <literal>1.1.8</literal>, at the
<ulink url="http://www.ibm.com/java/jdk/118/linux/">IBM Java Developer Kit downloads</ulink>
web site.
for Linux, Java Technology Edition, from the IBM Java Developer Kit
downloads web site as follows:
<itemizedlist>
<listitem>
<para><ulink url="http://www.ibm.com/java/jdk/118/linux/">Version <literal>1.1.8</literal></ulink>
</para>
</listitem>
<listitem>
<para><ulink url="http://www.ibm.com/java/jdk/linux130/">Version <literal>1.3</literal></ulink>
</para>
</listitem>
</itemizedlist>
</para>
<para>
@ -1213,6 +1230,10 @@ into formats supported by Debian (<literal>dpkg</literal>), Stampede
(<literal>slp</literal>), and Slackware (<literal>slp</literal>).
</para>
<variablelist>
<varlistentry>
<term>Debian</term>
<listitem>
<para>
Susan Williams reported success in installing DB2 Version 7.1 on Debian using
the following script as root:
@ -1228,7 +1249,6 @@ done
</programlisting>
</example>
</para>
<!-- Future work -->
<para>
This script installs every DB2 package on the CD-ROM. In a future iteration of
@ -1244,6 +1264,25 @@ To create a DB2 instance, issue the <filename>/usr/ibmdb2/v7.1/instance/<command
command as root. To get the correct syntax for either command, use the <literal>-h</literal> flag.
</para>
<para>
Further information on installing DB2 on Debian is available from Tiago Antao's page,
<ulink url="http://tiago.org/db2-4-linux.html">Agnostic DB2 V7.1 for GNU/Linux</ulink>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Slackware</term>
<listitem>
<para>
Thorough information on installing DB2 on Slackware 7.1 using <command>RPM</command> is available
from James Phillips' page, <ulink url="http://www.webdaemons.com/db2install.html">Installing DB2 on Slackware Linux</ulink>.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="db2instance">
@ -2007,6 +2046,23 @@ when you use a DB2 database.
<indexterm><primary>kernel</primary><secondary>optimizing parameters</secondary></indexterm>
<qandaset>
<qandaentry>
<question>
<para><emphasis>I installed DB2 Version 6.1 and <command>db2start</command> just hangs.</emphasis></para>
</question>
<answer>
<para>
Hey! I said I wasn't going to include any DB2 Version 6.1 information! Oh well, this is
one of the most frequently asked questions about 6.1, so here's a short answer: you need to install
a recent DB2 FixPack. The initial release of DB2 Version 6.1 ran into incompatibilities
with distributions built on <literal>glibc 2.1</literal>. For a full description of the
problem, and the correct install procedure, refer to IBM Support document 1000814:
<ulink url="http://www-1.ibm.com/servlet/support/manager?rt=0&amp;rs=0&amp;org=swg&amp;doc=852568E5006F0CC68525693E00535FB3">db2start hangs on Linux distributions built with glibc 2.1</ulink>.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para><emphasis>I'm running out of connections for my DB2 server.</emphasis></para>
@ -2236,6 +2292,67 @@ because no local DB2 Administration Server can be available.
</answer>
</qandaentry>
<indexterm><primary>Control Center</primary><secondary>troubleshooting</secondary></indexterm>
<qandaentry>
<question>
<para><emphasis>When I try to start the DB2 Control Center, I get the following message
at the console: <computeroutput>Xlib: connection to "localhost:0.0" refused by server</computeroutput>
</emphasis</para>
</question>
<answer>
<para>
This normally indicates an X permissions problem that occurs when you log on as one user, then
<command>su</command> to the DB2 instance owner so that you can start the DB2 Control Center.
By default, most X servers do not recognize 'localhost' as a client that is allowed to initiate
an X app on your display; it will only recognize your real hostname. If <command>xauth</command>
is set up, then it will complain if a user ID other than the one that started X tries to invoke
an X application.There are a few things you can try:
<itemizedlist>
<listitem>
<para>
Before su'ing to the DB2 instance owner, issue the command <userinput>bash$ xhost +localhost</userinput>:
this tells your X server that 'localhost' is allowed to start X apps on your display. Then <command>su</command>
to the DB2 instance owner and start the Control Center.
</para>
</listitem>
<listitem>
<para>
Log out completely, then log on directly as the DB2 instance owner and start the Control Center.
You may still have to issue the command <userinput>bash$ xhost +localhost</userinput> before the
Control Center will start--recent distributions have added this extra level of security.
</para>
</listitem>
<listitem>
<para>
Look into the <command>xauth</command> command and add your primary user ID's
<filename>~/.Xauthority</filename> file to your DB2 instance owner's <literal>xauth</literal>
authority database. I believe it's the <command>xauth merge</command> command that you want.
</para>
</listitem>
</itemizedlist>
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para><emphasis>When I start the DB2 Control Center, I get a message box with the
error <computeroutput>SQL1042C An unexpected system error occurred.</computeroutput>
</emphasis></para>
</question>
<answer>
<para>
On most systems, this error occurs only the first time you start the Control Center. Note that
the message box may be mostly covered up by the pretty DB2 splash screen;
if this is the case, you have to move the error message window down
and press the "Close" button. The Control Center then starts correctly, and you should
not get the error message again.
</para>
</answer>
</qandaentry>
<indexterm><primary>Control Center</primary><secondary>troubleshooting</secondary></indexterm>
@ -2254,13 +2371,17 @@ the appropriate groups. For more information, see <xref linkend="calderauid">.
</answer>
<answer>
<para>
Ensure that you have installed the IBM Developer Kit for Java 1.1.8, and that
the <filename class="directory">/usr/jdk118/bin</filename> directory is
in your path. If you issue the command <programlisting>bash&dollar; java -fullversion</programlisting>,
Ensure that you have installed the IBM Developer Kit for Java, and that
the directory containing the <filename>jre</filename> or <filename>java</filename>
executable is in your path. If you issue the command <programlisting>bash&dollar; java -fullversion</programlisting>,
you should get a response like this:
<computeroutput>
java full version "JDK 1.1.8 IBM build l118-20000325 (JIT enabled: jitc)"
</computeroutput>
or, for the IBM JDK 1.3:
<computeroutput>
java full version "J2RE 1.3.0 IBM build cx130-20000623"
</computeroutput>
Java virtual machines from other sources may not work.
For a quick guide to installing the IBM Developer Kit for Java, see
<xref linkend="jdkinstall">.
@ -2302,24 +2423,23 @@ login. For instructions on how to remove or modify this output, see
<para>
This section gives you quick and dirty instructions on how to install the
IBM Developer Kit for Java, version <literal>1.1.8</literal>. You need this version to run
the DB2 Control Center or Java applications or applets that connect to DB2.
IBM Developer Kit for Java, version <literal>1.1.8</literal> or <literal>1.3</literal>.
You need the IBM Developer Kit for Java to run the DB2 Control Center
or Java applications or applets that connect to DB2.
Note that these instructions are not meant to replace the documentation
supplied with the IBM Developer Kit for Java.
<warning>
<para>
For DB2 Version 7.1, you cannot use other versions of Java. Versions
of the Java Virtual Machine (<acronym>JVM</acronym>) supplied by other
software organizations are not supported, and even later versions of the
IBM Developer Kit for Java, such as JDK <literal>1.3.x</literal>, are
not supported.
software organizations are not supported.
</para>
</warning>
</para>
<procedure>
<title>Installing the IBM Developer Kit for Java</title>
<title>Installing the IBM Developer Kit for Java, Version 1.1.8</title>
<step>
<para>
@ -2357,6 +2477,70 @@ configuring the IBM Developer Kit for Java on Caldera OpenLinux.
</procedure>
<procedure>
<title>Installing the IBM Developer Kit for Java, Version 1.3</title>
<step>
<para>
Download the IBM Developer Kit for Java, version 1.3, from the
<ulink url="http://www.ibm.com/java/jdk/linux130/">IBM Java
Developer's Kit downloads web site</ulink>. I'll assume that you
download the <acronym>RPM</acronym> package of the IBM Developer Kit for Java.
</para>
</step>
<step>
<para>
Install the IBM Developer Kit for Java by issuing the following command as root:
<programlisting>bash# rpm -ivh IBMJava2-SDK-1.3-1.1-i386.rpm</programlisting>
</para>
</step>
<step>
<para>
Add the following lines to your <filename>/etc/profile</filename> file to set
up the Java environment for all users:
<programlisting>
export PATH=$PATH:/opt/IBMJava2-13/bin
</programlisting>
<note>
<para>
Caldera users should see <xref linkend="calderapreinstall"> for instructions on
configuring the IBM Developer Kit for Java on Caldera OpenLinux.
</para>
</note>
</para>
</step>
<step>
<para>
IBM JDK 1.3 does away with the <command>jre</command> command, even if you
install the the IBM JRE 1.3 package.
However, the <command>db2cc</command> script calls the
<command>jre</command> command. The easiest solution is to create a link
called <command>jre</command> to the <command>java</command> executable
in the <filename class="directory">/opt/IBMJava2-13/bin</filename> directory
by issuing the following command as root.
<programlisting>
bash# ln -sf /opt/IBMJava2-13/jre/bin/java /opt/IBMJava2-13/jre/bin/jre
</programlisting>
</para>
</step>
<step>
<para>
The <command>db2cc</command> script calls the <command>jre</command> command
with the <literal>-nojit</literal> argument, which is not supported in IBM JDK 1.3.
Remove the option by changing line 44 of <filename>/usr/IBMdb2/V7.1/bin/db2cc</filename>
to the following:
<programlisting>
JRE_OPTIONS="-ss256k -mx128m -Ddb2path=$DB2PATH"
</programlisting>
</para>
</step>
</procedure>
</sect1>
<appendix id="references">
<title>Resources</title>

2
LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
View File

@ -409,7 +409,7 @@ locale standards such as keyboard, font, paper-size etc. </Para>
DB2-HOWTO</ULink>,
<CiteTitle>DB2 Version 7.1 for Linux HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: July 2000</CiteTitle>.
<CiteTitle>Updated: September 2000</CiteTitle>.
Explicit instructions on installing DB2 Universal Database Version 7.1
for Linux on the following Intel x86-based distributions: Caldera
OpenLinux 2.4, Debian, Red Hat Linux 6.2, SuSE Linux 6.2 and 6.3,

2
LDP/howto/docbook/HOWTO-INDEX/programmSect.sgml
View File

@ -459,7 +459,7 @@ Control System, under Linux. </Para>
DB2-HOWTO</ULink>,
<CiteTitle>DB2 Version 7.1 for Linux HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: July 2000</CiteTitle>.
<CiteTitle>Updated: September 2000</CiteTitle>.
Explicit instructions on installing DB2 Universal Database Version 7.1
for Linux on the following Intel x86-based distributions: Caldera
OpenLinux 2.4, Debian, Red Hat Linux 6.2, SuSE Linux 6.2 and 6.3,