Skip to main content

IBM License Information document


If You are licensing under the Authorized User charge metric, then in Hot Standby, You must license the Program for the number of Authorized Users associated with the processors attached or available to all the Hot Standby server(s) for which DB2 is installed. For example, consider an environment with two servers, one Primary server with DB2 installed on four processors and the other one is a Hot Standby server with DB2 installed on two processors. The Primary server must be licensed with a minimum of 25 Authorized Users for each of the four processors for which DB2 is installed or the total number of Authorized Users accessing the data server installed on the four processors, whichever is greater. For the Hot Standby server, this server must be licensed in the same manner as the Primary server; for example, a minimum of 25 Authorized Users for each of the two processors on the Hot Standby server or the total number of Authorized Users accessing the data server, whichever is greater.

4.2) Idle/Warm Standby

In an Idle/Warm Standby configuration, Idle/Warm Standby servers have the Program installed, however, they do not have the Program operational to service user transactions or query workloads. A server is considered Idle/Warm if the HADR Reads on Standby component is disabled and the server is used exclusively for administrative actions that assist in failover scenarios such as having a database in rollforward pending state to support log shipping, or in making a flash copy of a DB2 database and then performing a database backup of this copy on another server, or in keeping a standby database synchronized using the HADR component.

If You are licensing under the Processor Value Unit charge metric, then in Idle/Warm Standby, You must license the Program for 100 Processor Value Units per Idle/Warm Standby server only, regardless of the number of processors attached or available to the server. For example, consider an environment with two servers, one Primary server with four processors and one Idle/Warm Standby server with two processors. This environment must be licensed for the Processor Value Units that apply to the four processors on the Primary server plus an additional 100 Processor Value Units for the Idle/Warm Standby server.

If You are licensing under the Authorized User charge metric, then in Idle/Warm Standby, You must license the Program for 25 Authorized Users only, regardless of the number of processors attached or available to the server. For example, consider an environment with two servers, one Primary server with DB2 installed on four processors and one Idle/Warm Standby server with two processors. The Primary server must be licensed with a minimum of 25 Authorized Users for each of the four processors on which DB2 is installed, or the total number of Authorized Users accessing the data server installed on the four processors, whichever is greater. For the Idle/Warm Standby server, only 25 Authorized Users must be licensed.

4.3) Cold Standby

In a Cold Standby configuration, Cold Standby servers may have the Program installed, however, they do not have the Program powered on. A server is considered Cold if, to use it, You must run the command "db2start" to instantiate the DB2 data server.

There are no charges for the Program on Cold Standby servers.

5) Host Connections

Restrictions on the use of DB2 with mainframe and iSeries data sources:

5.1) DB2 connect component

The DB2 connect component included with the Program may be used only for connecting to a properly licensed DB2 data server on Linux, UNIX or Windows. The component is not licensed for use with DB2 for z/OS and OS/390, DB2 Server for VSE & VM, and DB2 for iSeries data servers. If users need to connect to any of the above mentioned DB2 data servers, a separate PoE for a DB2 Connect program must be acquired.

5.2) IBM Data Server Driver for JDBC and SQLJ

The IBM Data Server Driver for JDBC and SQLJ included with the Program may be used for connecting to a properly licensed DB2 data server on Linux, UNIX or Windows. The driver is not licensed for use with DB2 for z/OS and OS/390, DB2 Server for VSE & VM, and DB2 for iSeries data servers. If users need to connect to any of the above mentioned DB2 data servers, a separate PoE for a DB2 Connect program must be acquired.

6) Program Components

The Program contains components which are provided to support Your authorized use of the Program on server machines within Your organization. If You want to perform multiple installations and/or distribution of these components You must contact IBM or its reseller to obtain the appropriate licenses. The following are the exceptions:

6.1) DB2 clients and documentation

DB2 clients and documentation are provided with this Program. You may make copies of these clients and documentation in support of Your authorized use of the Program within Your organization.

6.2) DB2 application drivers

The IBM Data Server Driver for JDBC and SQLJ is provided with this Program. You may make copies of these drivers in support of Your authorized use of the Program within Your organization. When using these drivers to connect to DB2 for z/OS, DB2 for VSE and VM or DB2 for i5/OS, the use of these drivers must comply with the terms and conditions of the appropriate DB2 Connect product.

7) IBM Database Enterprise Developer Edition

If this Program is acquired through the IBM Database Enterprise Developer Edition, then the Program can be installed on one or more shared servers for use by all Authorized Users with valid IBM Database Enterprise Developer Edition licenses, up to the level of use authorized by the PoE. You may use all components of the Program only for the purposes of evaluating, demonstrating, testing, and developing application programs.

8) DB2 Health Advisor

The DB2 Health Advisor is provided with this Program. If You use the DB2 Health Advisor to collect and send information to IBM, the following terms apply:

The DB2 Health Advisor collects various information and data regarding Your system and installation and configuration of DB2, which may include, without limitation, information about Your computer system's operating environment, operating system, configuration, resources, concurrently-running processes, DB2 configuration and usage information, and other technical information relevant to the support and operation of DB2. Notwithstanding any other agreement You may have with IBM, You agree that IBM may store and use any information collected by the DB2 Health Advisor and provided by You to IBM, and any other information provided by You in connection with the DB2 Health Advisor, for IBM's business purposes, including, without limitation, for support, analysis, quality assurance, product development, sales and marketing, and IBM may share such information with its contractors who support IBM in these activities.

9) Additional Terms

9.1) Usage Restriction - IBM Tivoli System Automation for Multiplatforms

This DB2 Program includes a limited use version of IBM Tivoli System Automation for Multiplatforms ("SA MP"). Your use of SA MP is subject to the license terms which accompany it, as well as the following limitations. You are authorized to install and use SA MP only in association with Your licensed use of the DB2 Program and for the sole purpose of providing high availability for the DB2 program. Any other use of SA MP requires a full use authorization which may be obtained separately from IBM or its reseller. To the extent of a conflict between the license terms which accompany SA MP and these restricted use terms, these restricted use terms shall take precedence.

9.2) Usage Restriction - IBM WebSphere MQ

This Program includes portions of WebSphere MQ. You are authorized to install and use these components only with, and on the same machine as, the DB2 data server. Your use of WebSphere MQ is limited to use in support of Your licensed use of the Program, and is subject to the terms and conditions of the license agreement which accompanies WebSphere MQ, except as limited in this license. The WebSphere MQ program may not be used for any other purpose unless a full license for WebSphere MQ is purchased.

9.3) Usage Restriction - IBM Eclipse Help System

The following subset of Excluded Components and/or Separately Licensed Code was obtained from the Eclipse Foundation: Tomcat, MX4J, Lucene, Lucene HTML Parser, Eclipse Help System (herein collectively referred to as "Eclipse Code"). Notices and important information, including instructions for obtaining source code, for the Eclipse Code may be found in associated "about.html" files ("About Files") located in a directory for the Eclipse Code. These About Files are provided for informational purposes only, and notwithstanding anything to the contrary therein, the terms governing Your use of such Eclipse Code shall be as set forth above in the applicable Excluded Components or Separately Licensed Code section.

9.4) Usage Restriction - IBM InfoSphere Federation Server

This Program uses components from InfoSphere Federation Server. You are authorized to use these components only in conjunction with the Program for access to federated data in Oracle and DB2 LUW databases, excluding DB2 for z/OS and DB2 for i. Any other use requires that you acquire a fully licensed copy of an IBM InfoSphere Federation Server product.


D/N: L-VACA-88GMXX
P/N: L-VACA-88GMXX