If you have acquired your Db2 license from SAP (so-called application-specifc license or ASL), see SAP Note 816773 to install the license. For multi-partition databases: Install the license on each database host. If you purchased Db2 directly from IBM, contact your IBM sales representative. In the DB2 Setup Launchpad, click Install a Product. Click Install New for DB2 Version 11.1 Workgroup, Enterprise and Advanced Editions. Note: If you do not see the DB2 Setup program, it is probably running in the background. Look for a blinking icon in the Windows taskbar and click it. Installing IBM data server clients and drivers (Windows). To install any client software on a Windows operating system: Log on to the system with the user account that is part of the Administrators group; Optional: Shut down other programs that are running on the computer. IBM #DB2 #Installation on #WindowsIn this Tutorial we are installing #IBM #DB2 Developer Edition on #Windows 10This would be helpful for #Database #Developer. In this tutorial, we will teach you how to install db2.DB2 falls in the family of relational database management system (RDBMS) products from IBM that are wo.

Last Update: 17 June 2021
Product: SQDR Plus
Version: 4.2 & later
Article ID: SQV00PL035

Abstract

In the four tier StarQuest Data Replication architecture, SQDR Plus runs on Tier 2 and uses a local IBM Db2 for Linux, UNIX & Windows (aka Db2 LUW) database as the control and staging database for each Staging Agent.

StarQuest originally recommended the use of Db2 Express 10.5, followed by Db2 Workgroup 11.1 or Db2 Standard 11.5.0 or 11.5.4. StarQuest now recommends using Db2 11.5.5fp1.

Existing users with Db2 10.5 should be aware that IBM ended support for 10.5 in April 2020. IBM will end support fo Db2 11.1 in April 2022.

SQDR Plus 5.21 and later ships with Db2 template images in 11.5.5 format, so all new installations of SQDR Plus must be using Db2 11.5.5 or later. If you are currently using SQDR Plus with an earlier version of Db2 (10.5, 11.1, or 11.5.0), you can continue to use existing agents, or create new agents using existing staging databases, but will not be able to create new staging databases. In any case, we recommend updating to Db2 11.5.5fp1 at your earliest convenience.

If you are using SQDR Plus 5.20 or earlier, you can create new agent databases while using Db2 11.5.5, but creation of those new databases will require extra time for conversion from 10.5 format.

This document describes the process for upgrading to Db2 11.5.5fp1.

It also includes information about updating to the latest fixpack (e.g. to 11.5.5fp1 from 11.5.5).

In most cases, you can update in place directly to 11.5.5fp1, without first uninstalling the existing version of Db2. If uninstalling and reinstalling is recommended, refer to Reinstalling Db2.

For additional guidance in working with Db2 as used by SQDR Plus, see the technical document Troubleshooting Tips for the SQDR Plus Db2 LUW Staging Database.

Solution

The procedure consists of these major tasks:

Preparation

Before stopping the SQDR and SQDR Plus services, use Task Manager or other tools to record your typical RAM usage. In some cases, Db2 11.x may have slightly higher memory requirements than 10.5; if you have a large number of agents and your memory usage is high, be prepared to add more memory to the system.
Examine the disk usage of the drive where the Db2 logs reside; this is the drive listed as 'Local database directory' when you run db2 list db directory. Using the recommended increase of LOGFILSIZ from 4096 to 8192, the amount of disk space used by Db2 logs will double. Confirm that the drive is large enough to handle the increase, or increase LOGFILSIZ selectively - i.e. make this change only for databases that will benefit from the change.
Verify that you know the credentials used for the Db2 services (typically .db2admin or Local System Account on Windows, and db2inst1, dasusr1, and db2fenc1 on Linux ), or delete the service users and recreate them during the reinstall of Db2. Removing Db2 on Windows will prompt whether or not you want to remove .db2admin.
On the Tier 3 system (running the SQDR service), Use Data Replicator Manager to pause the I/R group and delete any connections to the staging system. If SQDR is using Db2 (database SQDRC) for its control database, set the SQDRSVC service to Disabled.

On the Tier 2 system (running SQDR Plus):

If you will be creating a precautionary backup, verify that you have adequate available disk space in the temporary directory where you will store a backup file. Be sure that there are no older backup images of your database in the temporary directory. In our example, we are using the D: drive for both.
Identify the Db2 databases in use by SQDR Plus (e.g. SQDRP0, etc) by selecting the top level (system) in SQDR Control Center; the Control DB will be listed in the right panel.. You can also run the command db2 list database directory to list all databases; note the location of the database directory (e.g. L::).
Use the process described in the technical document Detecting and Cleaning up Unused Db2 Databases to avoid checking and upgrading databases that are no longer needed.
Stop and disable the SQDR Plus Derby services from the Services control panel (Windows) or /etc/init.d and using chkconfig (Linux); this will also stop the other SQDR Plus services. We do not want these services to start automatically after a reboot until we have finished the upgrade.
Use the db2 list applications command to verify that there are no active connections to Db2.
Optional: Back up the Db2 database to a temporary location (the compress argument is optional).

db2 backup database SQDRP0 to D:temp compress

Download & expand the Db2 installer image

Download the Db2 installer image using the URL supplied by StarQuest support. The image is over 1gb in size and should be downloaded in advance. You may also want to download the installers for IBM Data Studio client and Db2 Management Console or Data Server Manager.
Also download and expand db2update.zip.
Right-click and select Properties of the downloaded images; unblock if necessary.
Expand the installer images.

Run db2ckupgrade

Except in the case of updating from an earlier version of 11.5.x, run the db2ckupgrade utility from the db2Windowsutilities directory of the Db2 11.5.5 installer media or from a local copy to verify that the databases can be updated to 11.5.5; perform corrective actions as directed if necessary.

This can be done using db2list.bat and ckupgrade.bat scripts supplied in the db2update.zip package. These scripts do the following:

db2list creates a list of local databases using the following

setlocal enableDelayedExpansion
for /f 'tokens=4' %%x in ('db2 list database directory ^| find 'Database name') do (
echo %%x
)

Edit the resulting list (removing remote databases and appending a caret symbol at the end of each line) and paste it in to the ckupgrade script. Save this list of datdabases for later.

ckupgrade does the following:

Deactivate the database

Run db2ckupgrade i.e.

C> db2ckupgrade SQDRP0 -l SQDRP0.log -u adminuser -p password

Install

Run setup.exe to start the Db2 Setup Launchpad
Select Install a Product from the left panel.
You will see several possible products to install, and Install New and Work with Existing buttons for each product.
Choose Work with Existing for Db2 Version 11.x.x.x Server Editions
The next panel (Select the Db2 copy to work with) will display your existing (default name DB2COPY1) with the available action Upgrade.
Select DB2COPY1 and Launch Db2 Setup wizard
Select Installation type: Custom
You will receive several warnings about the need to reboot after installation.
You may be prompted for the db2admin credentials. If you are using a local db2admin user and the dropdown for the domain field does not show the local system as an option, enter a blank line for the domain.
On Enable operating system security for Db2 objects, unselect the checkbox Enable operating system security.
On completion of the up

Install Db2 11.1 On Windows 10