Chapter 1. Introduction to DB2 deployment 25
Requirements
These are the requirements of non-root installation on Windows platforms:
򐂰Non-Administrator user ID must belong to Power Users group.
򐂰VS2005 runtime library must be installed before attempting to install a DB2
product.
Limitations
These are the limitations of non-root installation on Windows platforms:
򐂰Services that would be automatically started are run as processes in
non-Administrator installs.
򐂰In DB2 Connect, some environment settings must be changed in
HKEY_CURRENT_USER.
򐂰After a non-Administrator has installed the DB2, no other user (including
Administrator) can install DB2 on same system. However, the Administrator
can uninstall and reinstall the DB2 product.
򐂰Non-Administrator users cannot uninstall a DB2 product.
Further information can be found in the DB2 Information Center:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/
com.ibm.db2.luw.qb.dbconn.doc/doc/c0008462.html
Table1-7 summarizes the key differences between root/Administrator
installations and non-root/non-Administrator installations.
Table 1-7 Key differences
The System Administrator and those involved with deployment planning should
weigh the pros and cons for particular scenarios before deciding on the non-root/
non-Administrator installation.
In this book, we concentrate on root/Administrator installation of the DB2 product
and deployment.
Criteria Root installations Non-root/non-Administrator
installations
User can select installation
directory Yes No. Db2 products are installed under the
user’s home directory
Number of DB2 instances
allowed Multiple One
Files deployed during
installation Program files only. Instances
must be created after installation. Program files and instance files. The DB2
product is ready for use immediately after
installation