You
can install DB2® products on
an NFS server and share the installed DB2 products
on its NFS client machines. If you use a non-root installation, you
cannot install your DB2 product in an NFS-mounted directory.
If your DB2 product is installed on an NFS-mounted file system, you
must verify that Network File System (NFS) is running on each machine.
Setup for shared DB2 on NFS
will require a few additional considerations including:
- Licensing (When DB2 product
installation is shared by several NFS client systems, manual validation
is needed to make sure any systems using the shared DB2 copy have the entitlement).
- Ensuring that the mount point for the DB2 product installation is mounted on the appropriate
install path before starting to use the shared DB2.
- Confirming if the link /usr/local/bin/db2ls from
the related DB2 installation
path, which lists installed DB2 products
and features, is set up and maintained properly to detect DB2 products and features.
- Performing some manual steps to handle DB2 registries on machines sharing the installed DB2.
For detailed instructions on setting up NFS, see www.ibm.com/developerworks/data/library/long/dm-0609lee .
Note: Starting from DB2 V9.7,
the handling of DB2 registries
in shared DB2 environment is
simplified. In the section C of "Setting Up DB2 Registries" of the white paper mentioned
previously, you only need to handle the global profile registry "DB2SYSTEM"
on the NFS client machines. The profiles.reg (listing the instance
names related to the DB2 copy)
and default.env (storing the global profile registries) are removed
from the DB2 installation path.
The profiles.reg is not needed any more. The global profile registry
repository is moved from default.env to the global.reg. With this
change, any steps needed on NFS client systems for profiles.reg and
default.env files in the white paper can be ignored. The IBM® DB2 pureScale® Feature does
not support shared DB2 installation.