A DB2® installation
process on a system WPAR is similar to any other installation, with
the additional benefit of using DB2 database
products in a global read-only installation path.
In AIX® 6.1 there are two
types of workload partitions (WPARs): system WPARs and application
WPARs. DB2 installation is only
supported on a system WPAR. System WPARs either share the /usr and /opt directories
with the global environment, and have a local copy of the /usr and /opt directories.
A DB2 database product can
be installed in a local file system on a system WPAR, or a DB2 database product can be installed
in a global environment with a DB2 copy
shared with other system WPARs. When a DB2 copy
is installed in a global environment under either the /usr or /opt directory,
which are shared with system WPARs, those system WPARs are able to
use the shared DB2 copy to setup DB2 instances.
Each system WPAR manages its own DB2 instances
and DAS related to the DB2 copy,
and can see only the DB2 instances
and DAS created specifically for the system WPAR. DAS and instances
created on one WPAR, or in a global environment, are not visible from
any other system (system WPAR or global environment).
When a DB2 copy is installed
in a global environment, DB2 instances
and DAS can be created and managed on each system WPAR sharing the
globally installed DB2 copy.
There are specific considerations when a DB2 copy is installed in a global environment:
- Installing the DB2 copy
- Installing a DB2 copy on
a system WPAR is similar to any other DB2 database
product installation, with the following exceptions. The following
cannot be installed on a system WPAR:
- IBM® Tivoli® System Automation for Multiplatforms
(SA MP)
- IBM Data Studio
- Uninstalling the DB2 copy
- Before uninstalling the DB2 copy
in a global environment, the AIX system
WPARs that shares the DB2 copy
with DB2 instances or DAS, must
be active. In addition, before uninstalling the DB2 copy, any system WPARs sharing the DB2 copy cannot have any related DB2 instances, or DAS associated
with, or in use by, that DB2 copy.
All instances and DAS must either be:
- dropped (using the db2idrop or dasdrop command),
or,
- updated the instance or DAS to another DB2 copy (using the db2iupdt or dasupdt command).
Note: The db2idrop and dasdrop command
must be run as the root user.
- Applying a fix pack to the DB2 copy
- Applying fix packs on a system WPAR is similar to any other DB2 database product update. However,
before applying a fix pack to a DB2 copy
in a global environment, the AIX system
WPARs that share the DB2 copy
must be active for the instances to be updated. In addition, before
applying a fix pack, any system WPARs sharing the DB2 copy cannot have any related DB2 instances or DAS running. All instances and
DAS related to the DB2 copy
to be updated must either be:
- stopped (using the db2stop command), or,
- run the installFixPack command with the -f
update parameter to bypass all the checking on DB2 library loading, instance and
DAS properly stopped or not. (However, this is not recommended.)
- Considerations when using the db2ls command
- When installing the DB2 copy
in a global environment, the directory containing the db2ls command
(/usr/local/bin) is linked to a DB2 copy in the global environment. The db2ls command,
is used to list the DB2 Version
9 (or higher) products installed on the system. On a system WPAR,
if the /usr directory is shared with the global
partition as read-only, the db2ls command running
on the system WPAR might not work unless the link target also exists
on the system WPAR, and, the related DB2 copy
is registered on the system WPAR. The db2ls command
can be found both in the DB2 installation
media and in a DB2 install copy
on the system, and can be run from either location.
DB2 10.5 for Linux, UNIX, and Windows