dnf install <package-name> 
             or
zypper install <package-name>

RPM Installation vs Traditional Installation

RPM-based installation introduces a simplified and standardized approach to deploying Db2 on Linux by leveraging native operating system package management. This does not replace traditional installation methods, which remain fully supported; instead, it provides an additional option for environments that prefer consistent, package-based deployment.

One of the key advantages of RPM-based installation is dependency management. RPM packages define explicit dependencies, allowing common libraries and shared components to be installed through dependent packages rather than being bundled within the Db2 product package itself. This reduces package size, minimizes duplication, and ensures that shared components are managed centrally at the system level.

In addition, RPM-based installation integrates with the Linux package database, enabling complete visibility into installed software. Administrators can use commands such as rpm -qa to retrieve a full, queryable list of installed packages, along with metadata such as version, installation date, vendor, and license information. This supports operational tracking and compliance requirements.

By comparison, traditional tarball-based installations do not register with the operating system package manager, which means there is no centralized audit trail of installed components at the OS level. This can make inventory tracking, patch management, and compliance reporting more manual and less consistent.

Installation Considerations

In summary, RPM-based installation focuses on simplicity, automation, and consistency, while traditional installation continues to provide full control and flexibility for complex deployment scenarios.

Step-by-Step Installation Walkthrough

Let’s walk through the installation process using RPM packages.

1. Kick-off the Installation

Install Db2 using your system package manager.

Recommended: Using a Local Repository

Using a local repository is recommended for RPM-based installation to ensure controlled access to Db2 packages and streamlined deployment.

A local repository can be created using standard Linux tools such as createrepo and served via HTTP or a local filesystem. For setup instructions, refer to:

• Creating a Yum/DNF repository using Apache
• Managing custom software repositories (Red Hat documentation)

Install Db2 from the configured repository:

dnf install db2-ese-<version>.rpm

Only the Db2 product RPM package needs to be specified, as required dependencies such as db2-common are automatically resolved and installed by the package manager.

Alternative: Direct RPM Installation 

dnf install db2-ese-<version>.rpm db2-common-<version>.rpm

Use this approach when installing directly from downloaded RPM files.

The installer resolves dependencies and installs the required components. 

2. Choose Installation Method

Select the approach that best fits your environment:

• Quick Install – automated setup
• Regular Install – manual control

2.1. Quick Install – Automatic Instance Creation

Quick Install mode automatically creates and configures a Db2 instance during RPM installation, providing the fastest path to a working Db2 environment. When the DB2RPMQUICKINSTALL=1 option is set and the RPM installation is initiated, the Db2 instance is created and started automatically as part of the installation process. Manual instance creation is not required.

Quick Install creates a default instance (db2inst1) and fenced user (db2fenc1) during installation. Securely generated passwords are assigned automatically. These default credentials must be changed after installation for security purposes.

To initiate Quick Install, set the environment variable:

export DB2RPMQUICKINSTALL=1

The instance is created automatically during the RPM installation when Quick Install mode is enabled.The instance creation logs are written to the /tmp directory. The log file name format is db2icrt.log.<PID>.

Expected results

• Installation fails if an instance with the default name (db2inst1) already exists
• An error message is displayed indicating an instance conflict

Resolution options

• Remove (drop) the existing instance before installation
• Use Regular Install mode 

Verify the instance

db2 get instance

Note: Quick Install uses the default instance name (db2inst1). Ensure that no instance with this name already exists before proceeding.

Example installation and installed location:

export DB2RPMQUICKINSTALL=1
dnf install db2-ese-12.1.5.s2607031024.el9-1-1.x86_64

 Db2 is installed under the default RPM installation directory as shown below:  /opt/ibm/db2/V{VRM}_{PRODUCT}_{LEVEL}

2.2. Regular Install – Full Control

Regular Install mode performs a standard Db2 software installation without creating an instance. This option is used when you require full control over instance creation, configuration, or when updating an existing instance to a new Db2 copy.

To initiate Regular Install, install the Db2 product RPM using the native Linux package manager:

dnf install db2-ese-<version>.rpm

In this mode, only the Db2 software is installed. No instance is created during installation, allowing you to define and manage the instance independently based on your requirements.

After completing the installation, navigate to the Db2 instance directory to create or update the instance as required:

cd /opt/ibm/db2/V{VRM}_{LEVEL}/instance

From this point onward, the process is identical to a traditional Db2 installation. You can create a new instance or update an existing instance using standard Db2 commands such as db2icrt or db2iupdt.

Note: Regular Install does not create or start any instance. Instance creation and configuration must be performed manually after installation.

3. Verify Installation

Verify that Db2 is installed and available.

rpm -qa | grep db2 (run as root): Lists all installed Db2 RPM packages to verify product installation at the OS level.

db2ilist (run as root): Displays all Db2 instances configured on the system.

db2level (run as instance user): Shows the Db2 version and fix pack level for the active installation.

These commands confirm that Db2 packages are installed and the instance is available.

4. Start Using Db2

Start the Db2 instance and create a sample database.

su - db2inst1
db2start
db2sampl

This confirms that Db2 is running and ready for use.

Video Walkthrough

Checkout this video for a sleek walkthrough of the Quick Install flow.

Checkout this video for a sleek walkthrough of the Regular Install flow.

Wrapping Up

Db2 RPM installation provides a simplified and efficient way to deploy Db2 on Linux. With both Quick Install and Regular Install options, you can choose between rapid setup and full configuration control based on your requirements.

About the Authors

Ancy C is a Software Developer in the Db2 Deployment team at IBM based in Kochi, Kerala. She focuses on improving installation and deployment experiences, with a particular emphasis on modern packaging approaches like RPM. With a strong interest in system reliability and platform enablement, she contributes to simplifying complex workflows and enhancing usability for Db2 customers.

Balanarayan K is a Senior Software Developer in the Db2 Deployment team at IBM based in Kochi, Kerala. He focuses on streamlining Db2 installation workflows and enhancing deployment experiences across platforms. A seasoned technologist, he brings experience from diverse domains like IoT, Embedded Systems and Automotive. With a strong foundation in engineering and a passion for knowledge sharing, he brings a unique blend of technical depth and practical insights to every project he undertakes. He is also known for his contributions to internal and collaborative technical enablement.

Neethu Jojo is a Software Developer in the Db2 Deployment team at IBM based in Kochi, Kerala. She works on enhancing Db2 deployment and installation processes, focusing on reliability, automation, and ease of use. With a keen interest in improving user experience, she contributes to initiatives that simplify setup and enable smoother adoption of Db2 across environments.