mirror of https://github.com/tLDP/LDP
Fix example response file. Move distributions to one distribution per page.
This commit is contained in:
dbs
parent
3e715f5e1b
commit
f87d105f34
|
|
@ -885,14 +885,12 @@ UDB:
|
|||
DAS_USERNAME = dasusr1
|
||||
DAS_GROUP_NAME = dasadm1
|
||||
DAS_HOME_DIRECTORY = /home/dasusr1
|
||||
DAS_PASSWORD = 235262333285355231346
|
||||
ENCRYPTED = DAS_PASSWORD
|
||||
DAS_PASSWORD = ******
|
||||
* Instance-owning user
|
||||
inst1.NAME = db2inst1
|
||||
inst1.GROUP_NAME = db2grp1
|
||||
inst1.HOME_DIRECTORY = /db2home/db2inst1
|
||||
inst1.PASSWORD = 235262333285355231346
|
||||
ENCRYPTED = inst1.PASSWORD
|
||||
inst1.PASSWORD = ******
|
||||
inst1.AUTOSTART = YES
|
||||
inst1.AUTHENTICATION = SERVER
|
||||
inst1.SVCENAME = db2c_db2inst1
|
||||
|
|
@ -903,8 +901,8 @@ inst1.MAX_LOGICAL_NODES = 4
|
|||
nst1.FENCED_USERNAME = db2fenc1
|
||||
inst1.FENCED_GROUP_NAME = db2fgrp1
|
||||
inst1.FENCED_HOME_DIRECTORY = /db2home/db2fenc1
|
||||
inst1.FENCED_PASSWORD = 235262333285355231346
|
||||
ENCRYPTED = inst1.FENCED_PASSWORD</programlisting>
|
||||
inst1.FENCED_PASSWORD = ******
|
||||
</programlisting>
|
||||
</para></listitem>
|
||||
<listitem><para>Manually using command line. To use this method, follow
|
||||
these steps:
|
||||
|
|
@ -991,7 +989,8 @@ user.</para></listitem>
|
|||
<para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Ensure that your system meets the installation, memory,
|
||||
and disk requirements outlined earlier.</para></listitem>
|
||||
and disk requirements outlined in <xref linkend='planning'/>.
|
||||
</para></listitem>
|
||||
<listitem><para>Review the installation considerations for IBM Developer
|
||||
Kit for Java 1.4.1.</para></listitem>
|
||||
<listitem><para>You require root authority to perform the
|
||||
|
|
@ -1200,15 +1199,15 @@ installation is finished the <guilabel>Setup Complete</guilabel> window indicate
|
|||
post-installation steps need to be taken, along with a status report of
|
||||
the installation. Click <guibutton>Finish</guibutton> to exit the DB2 UDB Setup
|
||||
wizard.</para></formalpara></sect2></sect1>
|
||||
<sect1 id='distros'><title>Distribution Specific Considerations</title>
|
||||
<para>In this part of the HOWTO, we will cover any tweaks, fixes or
|
||||
requirements that need to be made to get DB2 UDB running on specific
|
||||
Linux distributions.</para>
|
||||
<sect2 id='rhel3'><title>Red Hat Enterprise Linux (RHEL) 3</title>
|
||||
<sect1 id='rhel3'><title>Installing DB2 Version 8.2 on Red Hat Enterprise Linux (RHEL) 3</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>These installation notes are based on a single-partition
|
||||
installation using the 2.4.21–20 kernel (September 20,
|
||||
2004).</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>The pdksh package required for a multiple-partition environment
|
||||
setup is installed by default on Red Hat Enterprise Linux 3.</para>
|
||||
<para>RHEL 3 has backported the asynchronous I/O kernel capabilities of
|
||||
|
|
@ -1224,33 +1223,41 @@ Network account). Just run:
|
|||
up2date libaio</screen></para>
|
||||
<para>No Java package is installed by default, so there are no conflicts
|
||||
with the Java 2 SDK from IBM that DB2 UDB
|
||||
installs.</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
installs.</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>The installation on Red Hat Enterprise Linux 3 completed
|
||||
successfully, with no problems getting the GUI tools or installer
|
||||
working, and no errors during the install. This smooth installation
|
||||
isn't surprising, given that RHEL 3 is an officially supported platform
|
||||
for Version 8.2</para></sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
for Version 8.2</para></sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>Initialize the Asynchronous I/O so DB2 UDB can take advantage of
|
||||
this new kernel feature. As the instance owner:
|
||||
<screen>db2set DB2LINUXAIO=TRUE</screen></para></sect3></sect2>
|
||||
<sect2 id='rhel4'><title>Red Hat Enterprise Linux (RHEL) 4</title>
|
||||
<screen>db2set DB2LINUXAIO=TRUE</screen></para></sect2></sect1>
|
||||
<sect1 id='rhel4'><title>Installing DB2 Version 8.2 on Red Hat Enterprise Linux (RHEL) 4</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>These installation notes are based on a single-partition installation using the 2.6.9-5.0.5 EL kernel (April 20, 2005).</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>The pdksh package required for a multiple-partition environment
|
||||
setup is installed by default on Red Hat Enterprise Linux 4.</para>
|
||||
<para>The java-1.4.2-gcj-compat Java package is installed by default, but there are no conflicts with the Java 2 SDK from IBM that DB2 UDB installs.</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
<para>The java-1.4.2-gcj-compat Java package is installed by default, but there are no conflicts with the Java 2 SDK from IBM that DB2 UDB installs.</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>The installation on Red Hat Enterprise Linux 4 completed
|
||||
successfully, with no problems getting the GUI installer or tools working, and no errors during the install. This smooth installation
|
||||
isn't surprising, given that RHEL 4 is an officially supported platform
|
||||
for Version 8.2</para></sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
for Version 8.2</para></sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>Initialize the Asynchronous I/O so DB2 UDB can take advantage of
|
||||
this new kernel feature. As the instance owner:
|
||||
<screen>db2set DB2LINUXAIO=TRUE</screen></para></sect3></sect2>
|
||||
<sect2 id='sles9'><title>SuSE Linux Enterprise (SLES) 9</title>
|
||||
<screen>db2set DB2LINUXAIO=TRUE</screen></para></sect2></sect1>
|
||||
<sect1 id='sles9'><title>Installing DB2 Version 8.2 on SuSE Linux Enterprise (SLES) 9</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>SuSE Linux Enterprise Server 9 was released in August 2004 to
|
||||
great anticipation. It is currently the only Enterprise level Linux
|
||||
distribution certified by DB2 UDB that runs on the 2.6 kernel by
|
||||
|
|
@ -1258,7 +1265,7 @@ default.</para>
|
|||
<para>These notes are based on the 2.6.5-7 kernel (the SuSE Linux kernel
|
||||
update as of September 10, 2004), and installing a single-partition
|
||||
environment.</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>
|
||||
<orderedlist>
|
||||
<listitem><para>The pdksh package is installed in a default setup
|
||||
|
|
@ -1276,8 +1283,8 @@ installation:
|
|||
default max size of queue: 16384</screen></para></listitem>
|
||||
<listitem><para>Asynchronous I/O package (libaio) is also installed by
|
||||
default.</para></listitem>
|
||||
</orderedlist></para></sect3>
|
||||
<sect3><title>Installation Notes</title>
|
||||
</orderedlist></para></sect2>
|
||||
<sect2><title>Installation Notes</title>
|
||||
<para>I received an error during start up of the db2setup utility:
|
||||
<screen>/db2/ese/db2/linux/install/db2jinst:
|
||||
line 131: 3474 Segmentation fault
|
||||
|
|
@ -1289,8 +1296,8 @@ The solution here is to run
|
|||
from the
|
||||
terminal where you launched the db2setup utility, then run db2setup
|
||||
again. This change will only affect the Java installer, not the
|
||||
kernel performance.</para></sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
kernel performance.</para></sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>The kernel parameters (ipcs -l) after installation look like:
|
||||
<screen>
|
||||
max number of segments: 4096
|
||||
|
|
@ -1310,16 +1317,20 @@ SLES's installed Java 2 package. As the instance owner:
|
|||
</para>
|
||||
<para>Surprisingly, my installation didn't have Mozilla installed by
|
||||
default. To have the DB2 UDB help display properly, Mozilla should be
|
||||
installed using YaST.</para></sect3></sect2>
|
||||
<sect2 id='sles8'><title>SuSE Linux Enterprise (SLES) 8</title>
|
||||
installed using YaST.</para></sect2></sect1>
|
||||
<sect1 id='sles8'><title>Installing DB2 Version 8.2 on SuSE Linux Enterprise (SLES) 8</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>These installation notes are based on the 2.4.21 kernel (SLES
|
||||
kernel on September 20, 2004)</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>The pdksh package is installed in the default setup (required for
|
||||
multiple-partition and high availability installations).</para>
|
||||
<para>Also, SLES 8 installs the IBMJava2–SDK-1.3.1 rpm package in
|
||||
a typical installation.</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
a typical installation.</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>SuSE Linux Professional installs its own 1.3.1 Java JRE by default
|
||||
(the "IBMJava2-SDK-1.3.1" rpm package). During the DB2 UDB installation,
|
||||
this will cause a warning to be generated:
|
||||
|
|
@ -1349,20 +1360,24 @@ db2 UPDATE ADMIN CFG USING JDK_PATH /usr/lib/java</screen>
|
|||
</para></listitem>
|
||||
</orderedlist></para>
|
||||
<para>Other than that one minor issue, DB2 UDB installed cleanly and
|
||||
setup was problem free.</para></sect3></sect2>
|
||||
<sect2 id='suse91'><title>SuSE Linux Professional 9.1</title>
|
||||
setup was problem free.</para></sect2></sect1>
|
||||
<sect1 id='suse91'><title>Installing DB2 Version 8.2 on SuSE Linux Professional 9.1</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>Note that IBM does not officially support this distribution for
|
||||
DB2 UDB V8.2. Any problems you encounter using this distribution must be
|
||||
replicated on a supported distribution before IBM Support will help you
|
||||
resolve the issue.</para>
|
||||
<para>These notes are based on a single-partition installation on the
|
||||
2.4.21 kernel (September 20, 2004).</para>
|
||||
<sect3><title>Pre-installation
|
||||
<sect2><title>Pre-installation
|
||||
notes</title>
|
||||
<para>If you want to run a multiple-partition environment, you will need
|
||||
to install the pdksh package found on CD
|
||||
4.</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
4.</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>SuSE Linux Professional installs its own 1.4.2 Java JRE by default
|
||||
(the "java2–jre-1.4.2" package). During the DB2 UDB installation,
|
||||
this will cause a warning to be generated:
|
||||
|
|
@ -1391,8 +1406,12 @@ db2 UPDATE ADMIN CFG USING JDK_PATH /usr/lib/java</screen>
|
|||
</para></listitem>
|
||||
</orderedlist></para>
|
||||
<para>Other than that one minor issue, DB2 UDB installed cleanly and
|
||||
setup was problem free.</para></sect3></sect2>
|
||||
<sect2 id='susep'><title>SuSE Linux Personal 9.1</title>
|
||||
setup was problem free.</para></sect2></sect1>
|
||||
<sect1 id='susep'><title>Installing DB2 Version 8.2 on SuSE Linux Personal 9.1</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>Note that IBM does not officially support this distribution for
|
||||
DB2 UDB V8.2. Any problems you encounter using this distribution must be
|
||||
replicated on a supported distribution before IBM Support will help you
|
||||
|
|
@ -1400,21 +1419,25 @@ resolve the issue.</para>
|
|||
<para>These notes are based on the 2.6.4-52-default kernel and
|
||||
installing to a single-partition
|
||||
environment.</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>The pdksh package is not installed by default. If you want to
|
||||
install a multiple-partition environment on SuSE Linux Personal, you
|
||||
will have to install.</para>
|
||||
<para>The installer may complain about being unable to use the SMTP
|
||||
server even though postfix is installed and sendmail is available in the
|
||||
path. Make sure that postfix has been started before
|
||||
installation.</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
installation.</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>The usual trick of adding an xhost entry for localhost and then
|
||||
exporting the DISPLAY=localhost:0 when installing (so that the graphical
|
||||
utilities are displayed on a non-root user's desktop) didn't seem to
|
||||
work here. Instead, try executing ssh -X root@localhost and launch the
|
||||
utilities from there.</para></sect3></sect2>
|
||||
<sect2 id='fedora2'><title>Fedora Core 2</title>
|
||||
utilities from there.</para></sect2></sect1>
|
||||
<sect1 id='fedora2'><title>Installing DB2 Version 8.2 on Fedora Core 2</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>Note that IBM does not officially support this distribution for
|
||||
DB2 UDB V8.2. Any problems you encounter using this distribution must be
|
||||
replicated on a supported distribution before IBM Support will help you
|
||||
|
|
@ -1428,7 +1451,7 @@ future.</para>
|
|||
2.6.8-1 kernels (the Fedora Core 2 kernel update on September 13, 2004
|
||||
was 2.6.8-1), and installing to a single-partition
|
||||
environment.</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>The kernel parameters (ipcs -l) before DB2 UDB installation:
|
||||
<screen>
|
||||
max number of segments: 4096
|
||||
|
|
@ -1438,8 +1461,8 @@ environment.</para>
|
|||
default max size of queue: 16384</screen></para>
|
||||
<para>The asynchronous I/O package (libaio) is also required to take
|
||||
advantage of the 2.6 kernel improvements. Install the libaio package
|
||||
from the Fedora Core CD.</para></sect3>
|
||||
<sect3><title>Install
|
||||
from the Fedora Core CD.</para></sect2>
|
||||
<sect2><title>Install
|
||||
Notes</title>
|
||||
<para>The default 2.6.5 kernel had no installation issues with the
|
||||
db2setup GUI installer.</para>
|
||||
|
|
@ -1476,8 +1499,8 @@ on Fedora Core 2 using
|
|||
where db2ese.rsp is a
|
||||
slightly modified response file (the sample response files are found
|
||||
in the "db2/linux/samples/
|
||||
directory)</para></sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
directory)</para></sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>The kernel parameters (ipcs -l) after installation look like:
|
||||
<screen>
|
||||
max number of segments: 4096
|
||||
|
|
@ -1497,8 +1520,12 @@ owner, execute these commands:
|
|||
db2 UPDATE ADMIN CFG USING JDK_PATH /usr/java/jre1.5.0/</screen>
|
||||
With that update,
|
||||
the DB2 UDB Java-based tools will work
|
||||
properly.</para></sect3></sect2>
|
||||
<sect2 id='mand101'><title>Mandrake Linux 10.1 (Community)</title>
|
||||
properly.</para></sect2></sect1>
|
||||
<sect1 id='mand101'><title>Installing DB2 Version 8.2 on Mandrake Linux 10.1 (Community)</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>Note that IBM does not officially support this distribution for
|
||||
DB2 UDB V8.2. Any problems you encounter using this distribution must be
|
||||
replicated on a supported distribution before IBM Support will help you
|
||||
|
|
@ -1506,26 +1533,30 @@ resolve the issue.</para>
|
|||
<para>These notes are based on the 2.6.8.1–16mdk kernel and
|
||||
installing to a single-partition
|
||||
environment.</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>The pdksh package is not installed by default. If you want to
|
||||
install a multiple-partition environment on Mandrake Linux, you will
|
||||
have to install it using drakconf (it's on CD3). Also, no Java package
|
||||
is installed by default, so we don't have to worry about any conflicts
|
||||
arising from that.</para></sect3>
|
||||
<sect3><title>Installation
|
||||
arising from that.</para></sect2>
|
||||
<sect2><title>Installation
|
||||
notes</title>
|
||||
<para>The GUI based installation went smoothly, with no reported
|
||||
problems or issues. If you do experience a hang with the Java installer,
|
||||
try the Sun Java workaround described in the Fedora Core 2
|
||||
section.</para></sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
section.</para></sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>Be careful of the Mandrake Linux security "msec" utility –
|
||||
it can mess up DB2 UDB functionality by changing world readable
|
||||
directories (like /home/db2inst1/sqllib/) that are necessary to run DB2
|
||||
UDB to non-world readable. If you find that DB2 UDB is not working
|
||||
properly, investigate your
|
||||
security settings.</para></sect3></sect2>
|
||||
<sect2 id='gentoo'><title>Gentoo (2005-01-17)</title>
|
||||
security settings.</para></sect2></sect1>
|
||||
<sect1 id='gentoo'><title>Installing DB2 Version 8.2 on Gentoo (2005-01-17)</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>Note that IBM does not officially support this distribution for
|
||||
DB2 UDB V8.2. Any problems you encounter using this distribution must be
|
||||
replicated on a supported distribution before IBM Support will help you
|
||||
|
|
@ -1537,12 +1568,12 @@ instructions in the DB2 Information Center, we use the RPM method of
|
|||
installing DB2 UDB V8.2, through a modified <command>db2_install</command>
|
||||
script. This is just one of many ways you could accomplish this task, but this method
|
||||
has been tested (at least once) and it works.</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>Emerge the rpm package and any of its pre-requisites:
|
||||
<screen>emerge rpm</screen>
|
||||
If you want to run a multiple-partition environment, you will need to emerge either the pdksh or ksh package.
|
||||
</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>
|
||||
Gentoo uses the latest version of the GNU coreutils package of utilities, which
|
||||
includes the <command>tail</command> command. The DB2 install script
|
||||
|
|
@ -1617,7 +1648,7 @@ DB2.EXP
|
|||
<para>
|
||||
The DB2 installer will now install many RPM packages into the /opt/IBM/db2/V8.1/ directory.
|
||||
</para>
|
||||
<sect4><title>Installing DB2 UDB FixPaks on a non-RPM distribution</title>
|
||||
<sect3><title>Installing DB2 UDB FixPaks on a non-RPM distribution</title>
|
||||
<para>When installing a DB2 FixPak onto an existing DB2 installation, the RPM
|
||||
utility is used, which will cause problems on a distribution that does
|
||||
not use the RPM installation method by default. Since Gentoo is one of
|
||||
|
|
@ -1636,9 +1667,9 @@ The DB2 installer will now install many RPM packages into the /opt/IBM/db2/V8.1/
|
|||
rpm --force --nodeps --ivh ${fullfsname?}
|
||||
</screen>
|
||||
</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
</sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>Now that you have installed DB2, you need to create the groups, users,
|
||||
DB2 Administration Server instance, and database instance for your database.
|
||||
The following instructions create users and groups with the default names
|
||||
|
|
@ -1731,7 +1762,7 @@ the patch utility):
|
|||
</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
<sect4><title>
|
||||
<sect3><title>
|
||||
Enabling remote connections</title>
|
||||
<para>When you perform a manual install of DB2, the installer does not automatically
|
||||
set up the communication protocols for your DB2 server. To enable connections to your
|
||||
|
|
@ -1766,8 +1797,8 @@ db2start
|
|||
<para>
|
||||
You should now be able to catalog and connect to your Gentoo server from a remote client.
|
||||
</para>
|
||||
</sect4>
|
||||
<sect4><title>
|
||||
</sect3>
|
||||
<sect3><title>
|
||||
Running the DB2 Control Center and other DB2 GUI tools
|
||||
</title>
|
||||
<para>To run the DB2 Control Center or other DB2 GUI tools, you must install the IBM
|
||||
|
|
@ -1780,9 +1811,13 @@ rpm --force --nodeps -ivh db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0.i386.rpm
|
|||
</para><para>
|
||||
Log in as the db2inst1 and invoke the DB2 Control Center:
|
||||
<screen>db2cc</screen>
|
||||
</para></sect4>
|
||||
</sect3></sect2>
|
||||
<sect2 id='ubuntu504'><title>Ubuntu 5.0.4</title>
|
||||
</para></sect3>
|
||||
</sect2></sect1>
|
||||
<sect1 id='ubuntu504'><title>Installing DB2 Version 8.2 on Ubuntu 5.0.4</title>
|
||||
<para>
|
||||
Before proceeding, please ensure that you have read
|
||||
<xref linkend='planning'/> and <xref linkend='installing'/>.
|
||||
</para>
|
||||
<para>Note that IBM does not officially support this distribution for
|
||||
DB2 UDB V8.2. Any problems you encounter using this distribution must be
|
||||
replicated on a supported distribution before IBM Support will help you
|
||||
|
|
@ -1791,20 +1826,20 @@ resolve the issue.</para>
|
|||
Ubuntu 5.0.4. As Ubuntu uses .deb packages, we use the <command>alien</command>
|
||||
package conversion utility to convert and install the DB2 RPM packages directly.
|
||||
</para>
|
||||
<sect3><title>Pre-installation notes</title>
|
||||
<sect2><title>Pre-installation notes</title>
|
||||
<para>Ensure that you have installed <command>alien</command>:
|
||||
<screen>apt-get alien</screen>
|
||||
If you want to run a multiple-partition environment, you will need to emerge either the pdksh or ksh package.
|
||||
</para></sect3>
|
||||
<sect3><title>Installation notes</title>
|
||||
</para></sect2>
|
||||
<sect2><title>Installation notes</title>
|
||||
<para>
|
||||
To install the product into the /opt/IBM/db2/V8.1/ directory, change
|
||||
to the db2/linux/ directory of the CD or the extracted tarball
|
||||
and issue the following command as root:
|
||||
<screen># alien -d -i -c *.rpm</screen>
|
||||
<screen>alien -d -i -c *.rpm</screen>
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3><title>Post-installation notes</title>
|
||||
</sect2>
|
||||
<sect2><title>Post-installation notes</title>
|
||||
<para>Now that you have installed DB2, you need to create the groups, users,
|
||||
DB2 Administration Server instance, and database instance for your database.
|
||||
The following instructions create users and groups with the default names
|
||||
|
|
@ -1839,7 +1874,7 @@ useradd -u 1002 -g dasadm1 -m -d /home/dasusr1 dasusr1
|
|||
</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
<sect4><title>
|
||||
<sect3><title>
|
||||
Enabling remote connections</title>
|
||||
<para>When you perform a manual install of DB2, the installer does not automatically
|
||||
set up the communication protocols for your DB2 server. To enable connections to your
|
||||
|
|
@ -1874,8 +1909,8 @@ db2start
|
|||
<para>
|
||||
You should now be able to catalog and connect to your Ubuntu server from a remote client.
|
||||
</para>
|
||||
</sect4>
|
||||
<sect4><title>
|
||||
</sect3>
|
||||
<sect3><title>
|
||||
Running the DB2 Control Center and other DB2 GUI tools
|
||||
</title>
|
||||
<para>To run the DB2 Control Center or other DB2 GUI tools, you must install the IBM
|
||||
|
|
@ -1888,8 +1923,9 @@ alien -d -i -c db2/linux/Java-1.4/IBMJava2-SDK-1.4.1-2.0.i386.rpm
|
|||
</para><para>
|
||||
Log in as the db2inst1 and invoke the DB2 Control Center:
|
||||
<screen>db2cc</screen>
|
||||
</para></sect4>
|
||||
</sect3></sect2>
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
<sect1 id='help'><title id="help.title">Installing the DB2 UDB Information Center</title>
|
||||
<para>The new DB2 UDB Information Center is a new initiative from IBM to
|
||||
|
|
|
|||
Loading…
Reference in New Issue