The commands are run as follows in Figure 11.36 to unpack the Db2 Fix Pack:
Figure 11.36: The commands are run to copy and unpack the Db2 Fix Pack
After unpacking we can check the requirements using the command:
./db2prereqcheck -s -i
[root@ECMUKDEMO22 server_dec]# ./db2prereqcheck -s -i
Requirement not matched for DB2 database
“
Server
“
.
Version:
“
11.5.7.0
“
.
Summary of prerequisites that are not met on the current system: DBT3507E The db2prereqcheck utility failed to find the following package or file:
“
mksh
“
.
DBT3619W The db2prereqcheck utility detected that ksh is not linked to ksh or ksh93.
This is required for Db2 High Availability Feature with Tivoli SA MP.
We needed to update Linux packages as follows:
[root@ECMUKDEMO22 server_dec]# yum install gcc-c++
[root@ECMUKDEMO22 server_dec]# yum install ksh
[root@ECMUKDEMO22 server_dec]# yum install mksh
[root@ECMUKDEMO22 server_dec]# yum install xterm
[root@ECMUKDEMO22 server_dec]# yum install libstdc++.so.6
[root@ECMUKDEMO22 server_dec]# yum install pam.i686
Next we run the ./db2setup command to give the splash screen as shown in Figure 11.37:
Figure 11.37: We run the ./db2setup command to give the splash screen
The IBM DB2 Welcome screen is displayed to show the New Install button as shown in Figure 11.38:
Figure 11.38: The IBM DB2 Welcome screen is displayed to show the New Install command button
Select DB2 Version 11.5.7.0 Server Editions option and click Next, shown in Figure 11.39:
Figure 11.39: Select DB2 Version 11.5.7.0 Server Editions option and click Next
We select the Typical installation option as shown in Figure 11.40:
Figure 11.40: Select the “Typical” Installation option
The Instance Owner defaults (User db2inst1 with Group db2iadm1) is selected and the password entered as shown in Figure 11.41 and Next clicked:
Figure 11.41 :The defaults (User db2inst1 with Group db2iadm1) is selected, and the password entered
The Fenced User defaults (User db2fenc1 with Group db2fadm1) is selected, and the password entered as shown in Figure 11.42 and Next clicked:
Figure 11.42: The Fenced User defaults (User db2fenc1 with Group db2fadm1) is selected, and the password entered
The Finish button is selected with the default Install option as shown in Figure 11.43:
Figure 11.43: The Finish command is selected with the default Install option
The installation progress is shown in Figure 11.44:
Figure 11.44: The Installation progress is shown
The Post-install steps button is selected after the setup install has completed, as shown in Figure 11.45:
Figure 11.45: The Post-install steps command button is selected after the Setup install has completed
After installation we need to perform the following steps:
- To start using DB2 we have to login as the DB2 instance user, db2inst1 (set up in our default installation).
- The port number 25010 must be opened in the Firewall for connection to the DB2 instance db2inst1 we created:
firewall-cmd –zone=public –permanent –add-port=25010/tcp
firewall-cmd –reload
We can validate the installation files, instance, and database functionality, by running the Validation Tool using the command as shown in Figure 11.46:
/opt/ibm/db2/V11.5/bin/db2val
Figure 11.46: Validate the installation files, instance, and database functionality, by running the Validation Tool
Each DB2 product requires a license certificate file (also referred to as a license key) that is distributed as an activation file.
To verify the license using the command shown in Figure 11.47, use the command as follows:
/opt/ibm/db2/V11.5/adm/db2licm -l
Figure 11.47: Verify the license using the command /opt/ibm/db2/V11.5/adm/db2licm -l