Errors when installing a Db2 database product as a non-root user to the default path on a system WPAR (AIX)
Various errors can occur if you install Db2 database products as a non-root user in the default installation path (/opt/IBM/db2/V9.7) on a system workload partition (WPAR) on AIX® 6.1. To avoid these problems, install Db2 database products on a file system that is accessible only to the WPAR.
Symptoms
If you install Db2 database products in the /usr or /opt directories on a system WPAR, various errors can occur depending on how you configured the directories. System WPARs can be configured to either share the /usr and /opt directories with the global environment (in which case the /usr and /opt directories will be readable but not write accessible from the WPAR) or to have a local copy of the /usr and /opt directories.
In the first scenario, if a Db2 database product is installed to the default path on the global environment, that installation will be visible in the system WPAR. This will give the appearance that Db2 is installed on the WPAR, however attempts to create a Db2 instance will result in this error: DBI1288E The execution of the program db2icrt failed. This program failed because you do not have write permission on the directory or file /opt/IBM/db2/V9.7/profiles.reg,/opt/IBM/db2/V9.7/default.env.
In the second scenario, if a Db2 database product is installed to the default path on the global environment then when the WPAR creates the local copy of the /usr and /opt directories the Db2 database product installation will also be copied. This can cause unexpected problems if a system administrator attempts to use the database system. Since the Db2 database product was intended for another system, inaccurate information might be copied over. For example, any Db2 instances originally created on the global environment will appear to be present in the WPAR. This can cause confusion for the system administrator with respect to which instances are actually installed on the system.
Causes
These problems are caused by installing Db2 database products in /usr or /opt directories on a system WPAR.
Resolving the problem
Do not install Db2 database products in the default path on the global environment.
Mount a file system that is accessible only to the WPAR and install the Db2 database product on that file system.