This task describes how to install DB2® database products, components, and features
from DB2 payload files. This
method is not recommended for DB2 product
installation. It is recommended that you use the DB2 Setup wizard
or the response file method. This method does not support DB2 pureScale® installation types.
Before you begin
Before
you deploy DB2 payload files:
- Review the installation prerequisites and ensure that the requirements
are met.
- Ensure that DB2 dependencies
are met. Review the installation prerequisites, and make note of any DB2 database products that must
be installed with each other. Ensure to deploy the tar.gz file
for a product and, any of the tar.gz files for
required products.
- Get the payload files, which are contained on the DB2 database product DVD or can be downloaded
from IBM® Passport Advantage®: http://www.ibm.com/software/howtobuy/passportadvantage/.
About this task
Restrictions
You
cannot manually install a DB2 database
product, component, or feature using an operating system's native
installation utility such as rpm, SMIT, swinstall or pkgadd.
Procedure
To install DB2 database
products, components, and features from DB2 payload
files:
- For root installations, log on as a root user. For non-root
installations, log on with the user ID that is to own the DB2 installation.
- Insert and mount the appropriate DVD or access the file
system where the installation image is stored.
- Locate the DB2 component
that you want to install. Each DB2 database
product DVD provides a file that lists the components available for
installation. The component list is in a file that is called ComponentList.htm and
is located at /db2/platform directory
on your DVD, where platform is the platform that
you are installing on.
- Uncompress the payload file.
Note: For DB2 database products and components to work
together, they must be installed to a single path. This is not to be confused with the ability to
install DB2 database products to multiple paths. But, for
products and components to work together, they must be installed to the same path, and must be at
the same release level. If a component has prerequisites, look in the
DB2DIR/.metadata/COMPONENT/prereqs file
inside each payload to see what the prerequisites are. If any required components are missing, that
functionality does not work.
When you
uncompress the
tar.gz files, do not uncompress the following files that are
related to DB2
pureScale environment:
- For AIX®:
- PURESCALE_10.5.0.3_aix64_ppc.tar.gz
- CF_10.5.0.3_aix64_ppc.tar.gz
- For Linux:
- PURESCALE_10.5.0.3_linuxamd64_x86_64.tar.gz
- CF_10.5.0.3_linuxamd64_x86_64.tar.gz
Do not uncompress any tar.gz files with file names that start with
"GSKNOINST". These files are only for installations without encryption support.
To uncompress the payload file, run the appropriate
command:
where - DB2DIR is the full path name where you are installing:
- dvd represents the mount point of the DB2 DVD.
- filename is the name of the DB2
component you are installing.
- To ensure the embedded library search path on each DB2 executable and library file
uses the installation path, run the following command:
DB2DIR/install/db2chgpath
where DB2DIR is
the full path name where you are installing. - Important notes:
- After you run the db2chgpath command, program
files cannot be moved.
- If you install additional features to the same path at a subsequent
time, you must run the db2stop command, and rerun
the db2chgpath command.
- For root installations, you can now create a DB2 instance using the db2icrt command. If you do not want to create an instance, you must at least
run the db2ilist command. You must now run either
the db2icrt command or the db2ilist command,
because a side-effect of running either command is that the installation
is registered with the global registry.
- For non-root installations, run $HOME/sqllib/db2nrcfg to
configure the non-root instance.
- Set up the db2ls utility. The db2ls utility
allows you to query information about installed DB2 copies. To set up the db2ls utility:
- Determine which DB2 copy
is the most updated copy by running the following command:
db2greg -dump
Output
such as the following displays:S,DB2,10.1.0.0,/opt/ibm/copy1,-,,0,,,1159464765,0
S,DB2,10.1.0.1,/opt/ibm/copy2,,,1,0,,1159466596,0
In the
sample output, 10.1.0.1 in the second line indicates that copy2 is
at a higher level than copy1, which is at 10.1.0.0.
- Check /usr/local/bin to see whether
a link to db2ls exists. If it exists, check which DB2 copy it points to.
- If either of the following conditions are true, create
a link to /opt/ibm/latest_copy/install/db2ls in
the /usr/local/bin directory (where latest_copy is
the DB2 copy with the highest
level):
- /usr/local/bin/db2ls does not exist
- /usr/local/bin/db2ls exists, but points to
an installed DB2 copy that is
not the most updated copy on the system
- Set up the DB2 fault
monitor in /etc/inittab by running the db2fmcu command,
which is available in a server installation. For example:
DB2DIR/bin/db2fmcu -u -p /etc/inittab
where DB2DIR is
the full path name where you are installing.
- For non-root installations, after the DB2 database product is installed, you must open
a new login session to use the non-root DB2 instance.
Alternatively, you can use the same login session if you set up the DB2 instance environment with $HOME/sqllib/db2profile (for
Bourne shell and Korn shell users) or $HOME/sqllib/db2chsrc (for
C shell users), where $HOME is
the non-root user's home directory.
What to do next
After
payload deployment, there are further manual configuration tasks that
must be completed.
Refer to the Related tasks
for details.