Db2 for LUW (Linux®, UNIX, and Windows) prerequisites
Learn about the prerequisite software for creating the Db2® for LUW databases.
Important:
- A single instance of Db2
LUW Server can be used for multiple ADDI Server instances when the following conditions are met:
- When you configure ADDI by using the IBM ADDI Configuration Wizard, make sure that the names of Annotations, Audit, and Cross Analysis databases for each ADDI environment are unique in all environments and specific to a certain server installation instance, such as Audit_Install_A or Cross_Server_X. For more information, see Configuring by using IBM ADDI Configuration Wizard.
- Under normal usage conditions, since there are multiple different environments, the project names cannot be duplicated between the multiple ADDI environments.
- Make sure that only IBM® Data Server Client V11.5.9 or a higher version is installed as the Db2 driver. If multiple variations of Db2 drivers are installed on the IBM ADDI virtual machine, the IBM ADDI Build Client might be unusable.
IBM Db2 for LUW Server Configurations
On workstations where IBM
ADDI Build Client is
installed, Data Server Client V11.5.9, which contains IBM Data Server Provider for .NET, must be installed. The
mentioned package is part of the Db2 Connect™ V11.5.9
product. Starting from IBM
ADDI 6.1.4, the required DB2 Driver - IBM Data Server Client
11.5.9 is packaged with the ADDI installer. It can be
used from there and does not need to be licensed.
Note: .NET framework 4.5.1 or higher is a
prerequisite for IBM
ADDI Build Client.
To see which version is
installed on the Build Client machine, run the following
command:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v versionIf the IBM
ADDI Build Client is intended to be used by
a standard user, with no administration privileges, make sure that during the Db2 Connect V11.5.9 installation process the
Enable operating system security check box is selected.
Note: If you selected
the Enable operating system security check box, you now have to add users to
the DB2ADMNS or the DB2USERS groups for users that need to run
IBM
ADDI Build Client. For more information, see Adding your user ID to the DB2ADMNS and DB2USERS user
groups.
Prerequisite software for automatically creating the Db2 for LUW databases
For Cross Applications and Annotations database, the following prerequisites need to be installed
on the machine where IBM
ADDI Servers and Services is installed:
- IBM Data Server Client V11.5.9. Starting from IBM ADDI 6.1.4, the required DB2 Driver - IBM Data Server Client 11.5.9 is packaged with the ADDI installer. It can be used from there and does not need to be licensed.
- Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 (for Windows only).
User permissions
In the IBM
ADDI application, an operating system user
account (Authentication ID) is used to work with the Db2
for LUW repository. The user account must have the
SYSCTRL authority to be able to create databases and to perform actions on the
created databases. For more information, see the System control authority (SYSCTRL) topic.
If providing SYSCTRL authority level is not an option for an ADDI
Db2 user ID, apply the troubleshooting solution that is
explained in Creating Db2 for LUW Database Using DDL Script.
Important: If Db2 Authentication ID is a part
of a domain, be aware that the default value of DB2_GRP_LOOKUP is NULL. Make sure
to assess the Db2 user ID and provide the proper values
for DB2_GRP_LOOKUP.
For example, the Db2 user ID is a part of a domain that is added to the local
OS Admin Group from the VM where Db2 server is installed. In this case, even if the user ID has
the
SYSCTRL authority, the user ID cannot be recognized by the Db2 server in this type of user configuration
(<domainname>\<userID>), and some errors might occur. - For more information about DB2_GRP_LOOKUP, see DB2_GRP_LOOKUP.
- For an example of an error that is caused by the improper value for
DB2_GRP_LOOKUP, see DB2 log file error: SQL1092N
USERID does not have the authority to perform the requested command or operation
.