Installing IBM Db2 for i2 Analyze
LocationIf you are creating a production deployment, you can install Db2® in any location. When you install Db2, record the location of the installation directory because you must specify this location in the deployment toolkit before you can deploy i2® Analyze.
- For Windows™: C:\Program Files\IBM\SQLLIB
- For Linux®: /opt/ibm/db2/Db2_version
Features and languageIn all deployments, you must ensure that the following features are installed:
- Spatial Extender server support
- Spatial Extender client
When you deploy i2 Analyze with the Information Store, you must install Db2 with the product interface language set to English only. Additionally, if you install Db2 on Red Hat® Enterprise Linux, you must use an English version of Red Hat Enterprise Linux. For more information, see Changing the Db2 interface language (Linux and UNIX®) and Changing the Db2 product interface language (Windows).
deployments, if you are deploying with a schema
that contains non-English characters, ensure that
the operating system's
environment variable is set to the locale of the
DB2_WORKLOADenvironment variable is not set and the database is row-organized. If you have an existing Db2 instance where
DB2_WORKLOADis set or the database is column-organized, you must create a Db2 instance with the supported configuration and deploy i2 Analyze with it. For more information about the
DB2_WORKLOADenvironment variable, see System environment. For more information about column-organized databases, see Setting the default table organization.
UsersOn Windows, Db2 creates a Windows user account (
db2admin), and two Windows groups (
DB2USERS). To work successfully with Db2, ensure that your Windows user account is a member of the
On Linux, Db2 creates an
Administration Server user (
dasusr1) and group
dasadm1), an instance-owning user (
and group (
db2iadm1), and a fenced user (
and group (
db2fadm1). To work successfully with Db2, ensure that the user that runs the deployment script is a
member of the
Make a note of any user names and passwords that are specified during the installation process.
- On the command line, navigate to the SQLLIB\bin directory of your Db2 installation. On Linux, navigate to the db2inst1/sqllib/bin directory.
- To enable the administrative task scheduler, run the following
- To set the code page for UTF-8 encoding, run the following
If you installed IBM Db2 on Linux, ensure that the operating system user process resource limits (ulimits) meet the Db2 recommended values. For more information about the recommended ulimits, see Operating system user limit requirements (Linux and UNIX).
Remote Db2 database storageIf you plan to deploy i2 Analyze with remote database storage, you must install Db2 on your database server, and Db2 or IBM® Data Server Client on the application server. Install Db2 according to the previous instructions; if you are using IBM Data Server Client, also ensure that Spatial Extender client support is installed. For more information about IBM Data Server Client, see Installing IBM Data Server drivers and clients.
The instance of Db2 or IBM Data Server Client on the application server must be the same version level as the instance of Db2 on the database server. For example, if the instance of Db2 on your database server is version 11.1, the instance of Db2 or IBM Data Server Client on the application server must also be version 11.1.
When you install Db2 in a deployment that uses HADR, the following must be true:
- The version of Db2 installed on the primary and standby servers must be the same.
- Install Db2 on all servers according to the previous information
- Db2 must be installed with the same bit size (32 or 64 bit) for both the primary and standby servers.
- The primary and standby databases must have the same database name.
- The primary and standby databases must be in difference instances.
- The amount of space allocated for log files must be the same on both the primary and standby databases.