The next task in my journey with DB2 is to apply a patch. In the world of DB2 there are Modification Packs and Fix packs. As far as I understand it, Modifications Packs come with new features, while Fix Packs come with bug fixes only. Keeping your database installations up to date is important, that applies to all products. As my system is running 11.5 the page which gives me all the information is this, the downloads are here. Lets go.
I’ll use the installation from the last post, which means this is a root installation. The current version of my Db2 instance is 11.5.6.0:
db2inst1@sles15-db2-root:~> db2ls Install Path Level Fix Pack Special Install Number Install Date Installer UID --------------------------------------------------------------------------------------------------------------------- /opt/ibm/db2/V11.5 11.5.6.0 0 Thu Jan 20 12:05:28 2022 CET 0
After downloading the latest pack and putting it in the home directory of the root user it looks like this:
db2 => quit DB20000I The QUIT command completed successfully. db2inst1@sles15-db2-root:~> su - Password: sles15-db2-root:~ $ ls -l total 1826112 -rw------- 1 root root 61 Jan 20 13:14 .Xauthority -rw------- 1 root root 2376 Jan 20 15:25 .bash_history drwx------ 1 root root 0 Mar 3 2021 .gnupg -rw------- 1 root root 1402 Jan 20 15:25 .viminfo drwxr-xr-x 1 root root 0 Mar 3 2021 bin drwxr-xr-x 1 root root 36 Jul 9 2021 inst-sys -rw-r--r-- 1 root root 1869925829 Jan 21 09:42 v11.5.7_linuxx64_server_dec.tar.gz
Not much different from the initial installation, once you extract that you’ll get the “server_dec” directory:
sles15-db2-root:~ $ tar axf v11.5.7_linuxx64_server_dec.tar.gz sles15-db2-root:~ $ ls -l total 1826112 -rw------- 1 root root 61 Jan 20 13:14 .Xauthority -rw------- 1 root root 2376 Jan 20 15:25 .bash_history drwx------ 1 root root 0 Mar 3 2021 .gnupg -rw------- 1 root root 1402 Jan 20 15:25 .viminfo drwxr-xr-x 1 root root 0 Mar 3 2021 bin drwxr-xr-x 1 root root 36 Jul 9 2021 inst-sys drwxr-xr-x 1 root root 240 Nov 22 19:36 server_dec -rw-r--r-- 1 root root 1869925829 Jan 21 09:42 v11.5.7_linuxx64_server_dec.tar.gz sles15-db2-root:~ $ rm v11.5.7_linuxx64_server_dec.tar.gz
Inside this directory you’ll “installFixPack”, which is a plain shell script:
sles15-db2-root:~ # cd server_dec/ sles15-db2-root:~/server_dec # ls -l total 84 drwxr-xr-x 1 bin bin 112 Nov 22 19:36 db2 -r-xr-xr-x 1 bin bin 5207 Nov 22 19:36 db2_deinstall -r-xr-xr-x 1 bin bin 5077 Nov 22 19:36 db2_install -r--r--r-- 1 bin bin 16809 Nov 22 19:36 db2checkCOL.tar.gz -r--r--r-- 1 bin bin 4987 Nov 22 19:36 db2checkCOL_readme.txt -r-xr-xr-x 1 bin bin 5254 Nov 22 19:36 db2ckupgrade -r-xr-xr-x 1 bin bin 5041 Nov 22 19:36 db2ls -r-xr-xr-x 1 bin bin 5059 Nov 22 19:36 db2prereqcheck -r-xr-xr-x 1 bin bin 5059 Nov 22 19:36 db2setup -r-xr-xr-x 1 bin bin 5095 Nov 22 19:36 installFixPack
The parameters you need to pass to that script, are the current location of installation and a new directory where the pack gets installed. Lets try:
sles15-db2-root:~/server_dec $ ./installFixPack -b /opt/ibm/db2/V11.5/ -p /opt/ibm/db2/fixpack/ 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. Aborting the current installation ... Run installation with the option "-f sysreq" parameter to force the installation.
Ok, apparently we need a KornShell to install that:
sles15-db2-root:~/server_dec $ zypper in -y mksh ksh
Next try:
sles15-db2-root:~/server_dec $ ./installFixPack -b /opt/ibm/db2/V11.5/ -p /opt/ibm/db2/fixpack/
Read the license agreement file in the db2/license directory.
***********************************************************
To accept those terms, enter "yes". Otherwise, enter "no" to cancel the install process. [yes/no]
yes
DBI1017I installFixPack is updating the database products installed in
location /opt/ibm/db2/V11.5/.
DB2 installation is being initialized.
Total number of tasks to be performed: 53
Total estimated time for all tasks to be performed: 2552 second(s)
Task #1 start
Description: Preparing the system
Estimated time 120 second(s)
Task #1 end
Task #2 start
Description: Base Client Support for installation with root privileges
Estimated time 3 second(s)
Task #2 end
Task #3 start
Description: Product Messages - English
Estimated time 14 second(s)
Task #3 end
Task #4 start
Description: Base client support
Estimated time 360 second(s)
Task #4 end
Task #5 start
Description: Java Runtime Support
Estimated time 215 second(s)
Task #5 end
Task #6 start
Description: Java Help (HTML) - English
Estimated time 7 second(s)
Task #6 end
Task #7 start
Description: Base server support for installation with root privileges
Estimated time 6 second(s)
Task #7 end
Task #8 start
Description: Global Secure ToolKit
Estimated time 76 second(s)
Task #8 end
Task #9 start
Description: Java support
Estimated time 11 second(s)
Task #9 end
Task #10 start
Description: SQL procedures
Estimated time 3 second(s)
Task #10 end
Task #11 start
Description: ICU Utilities
Estimated time 59 second(s)
Task #11 end
Task #12 start
Description: Java Common files
Estimated time 18 second(s)
Task #12 end
Task #13 start
Description: Base server support
Estimated time 610 second(s)
Task #13 end
Task #14 start
Description: Control Center Help (HTML) - English
Estimated time 13 second(s)
Task #14 end
Task #15 start
Description: Relational wrappers common
Estimated time 3 second(s)
Task #15 end
Task #16 start
Description: DB2 data source support
Estimated time 6 second(s)
Task #16 end
Task #17 start
Description: ODBC data source support
Estimated time 260 second(s)
Task #17 end
Task #18 start
Description: Teradata data source support
Estimated time 3 second(s)
Task #18 end
Task #19 start
Description: Spatial Extender server support
Estimated time 21 second(s)
Task #19 end
Task #20 start
Description: Scientific Data Sources
Estimated time 5 second(s)
Task #20 end
Task #21 start
Description: JDBC data source support
Estimated time 185 second(s)
Task #21 end
Task #22 start
Description: IBM Software Development Kit (SDK) for Java(TM)
Estimated time 49 second(s)
Task #22 end
Task #23 start
Description: DB2 LDAP support
Estimated time 4 second(s)
Task #23 end
Task #24 start
Description: DB2 Instance Setup wizard
Estimated time 23 second(s)
Task #24 end
Task #25 start
Description: Structured file data sources
Estimated time 5 second(s)
Task #25 end
Task #26 start
Description: Integrated Flash Copy Support
Estimated time 3 second(s)
Task #26 end
Task #27 start
Description: Oracle data source support
Estimated time 4 second(s)
Task #27 end
Task #28 start
Description: Connect support
Estimated time 3 second(s)
Task #28 end
Task #29 start
Description: Application data sources
Estimated time 4 second(s)
Task #29 end
Task #30 start
Description: Spatial Extender client
Estimated time 3 second(s)
Task #30 end
Task #31 start
Description: SQL Server data source support
Estimated time 4 second(s)
Task #31 end
Task #32 start
Description: Communication support - TCP/IP
Estimated time 3 second(s)
Task #32 end
Task #33 start
Description: Base application development tools
Estimated time 36 second(s)
Task #33 end
Task #34 start
Description: Parallel Extension
Estimated time 3 second(s)
Task #34 end
Task #35 start
Description: EnterpriseDB code
Estimated time 3 second(s)
Task #35 end
Task #36 start
Description: Replication tools
Estimated time 60 second(s)
Task #36 end
Task #37 start
Description: Sample database source
Estimated time 4 second(s)
Task #37 end
Task #38 start
Description: itlm
Estimated time 3 second(s)
Task #38 end
Task #39 start
Description: DB2 Text Search
Estimated time 108 second(s)
Task #39 end
Task #40 start
Description: Command Line Processor Plus
Estimated time 8 second(s)
Task #40 end
Task #41 start
Description: Sybase data source support
Estimated time 3 second(s)
Task #41 end
Task #42 start
Description: Informix data source support
Estimated time 4 second(s)
Task #42 end
Task #43 start
Description: Federated Data Access Support
Estimated time 3 second(s)
Task #43 end
Task #44 start
Description: First Steps
Estimated time 3 second(s)
Task #44 end
Task #45 start
Description: Pacemaker
Estimated time 100 second(s)
Task #45 end
Task #46 start
Description: Product Signature for DB2 Server Edition
Estimated time 6 second(s)
Task #46 end
Task #47 start
Description: Guardium Installation Manager Client
Estimated time 36 second(s)
Task #47 end
Task #48 start
Description: Setting DB2 library path
Estimated time 180 second(s)
Task #48 end
Task #49 start
Description: Installing or updating Db2 resource agent scripts for Pacemaker
Estimated time 20 second(s)
Task #49 end
Task #50 start
Description: Executing control tasks
Estimated time 20 second(s)
Task #50 end
Task #51 start
Description: Updating global registry
Estimated time 20 second(s)
Task #51 end
Task #52 start
Description: Updating the db2ls and db2greg link
Estimated time 1 second(s)
Task #52 end
Task #53 start
Description: Registering DB2 licenses
Estimated time 5 second(s)
Task #53 end
The execution completed successfully.
For more information see the DB2 installation log at
"/tmp/installFixPack.log.4317".
Very much the same output/steps as in with the initial installation. All looks fine. This was the installation of all the files:
sles15-db2-root:~/server_dec $ cd /opt/ibm/db2/fixpack/ sles15-db2-root:/opt/ibm/db2/fixpack $ ls -l total 4 drwx--x--x 1 root root 30 Jan 21 09:53 .licbkup drwxr-xr-x 1 root root 1696 Nov 22 19:31 .metadata drwxr-xr-x 1 bin bin 6 Nov 22 19:28 R drwxr-xr-x 1 bin bin 296 Nov 22 19:27 Readme drwxr-xr-x 1 bin bin 18 Nov 22 19:27 acs drwxr-xr-x 1 bin bin 734 Nov 22 19:29 adm drwxr-xr-x 1 bin bin 76 Nov 22 19:28 adsm drwxr-xr-x 1 bin bin 4368 Nov 22 19:28 bin drwxr-xr-x 1 bin bin 5024 Nov 22 19:28 bnd drwxr-xr-x 1 bin bin 1090 Jan 21 09:53 cfg drwxr-xr-x 1 bin bin 10 Nov 22 19:27 conv drwxr-xr-x 1 bin bin 92 Nov 22 19:28 das drwxr-xr-x 1 bin bin 156 Nov 22 19:28 dasfcn drwxr-xr-x 1 bin bin 48 Nov 22 19:29 db2tss drwxr-xr-x 1 bin bin 84 Nov 22 19:28 desktop drwxr-xr-x 1 bin bin 12 Nov 22 19:28 doc drwxr-xr-x 1 bin bin 52 Nov 22 19:28 federation drwxr-xr-x 1 bin bin 100 Nov 22 19:28 function drwxr-xr-x 1 bin bin 24 Nov 22 19:28 gse drwxr-xr-x 1 bin bin 64 Nov 22 19:28 gskit drwxr-xr-x 1 bin bin 548 Nov 22 19:28 guardium drwxr-xr-x 1 bin bin 34 Nov 22 19:28 ha drwxr-xr-x 1 bin bin 2786 Nov 22 19:27 include drwxr-xr-x 1 bin bin 54 Nov 22 19:29 infopop drwxr-xr-x 1 bin bin 156 Jan 21 09:53 install drwxr-xr-x 1 bin bin 722 Nov 22 19:28 instance drwxr-xr-x 1 bin bin 352 Nov 22 19:27 java drwxr-xr-x 1 bin bin 38 Nov 22 19:27 json drwxr-xr-x 1 bin bin 1564 Jan 21 09:52 lib32 drwxr-xr-x 1 bin bin 10328 Jan 21 09:52 lib64 drwxr-xr-x 1 bin bin 932 Jan 21 09:53 license lrwxrwxrwx 1 root root 12 Nov 22 19:27 logs -> install/logs drwxr-xr-x 1 bin bin 66 Nov 22 19:28 map drwxr-xr-x 1 bin bin 746 Nov 22 19:28 misc drwxr-xr-x 1 bin bin 28 Nov 22 19:28 msg drwxr-xr-x 1 bin bin 246 Nov 22 19:28 pd drwxr-xr-x 1 bin bin 14 Nov 22 19:28 properties drwxr-xr-x 1 bin bin 30 Nov 22 19:28 python drwxr-xr-x 1 bin bin 368 Nov 22 19:28 samples drwxr-xr-x 1 bin bin 12 Nov 22 19:28 security32 drwxr-xr-x 1 bin bin 108 Nov 22 19:28 security64 drwxr-xr-x 1 bin bin 1796 Nov 22 19:28 tools
Now we need to patch the instance, this is done with db2iupdt which is located in the “instance” directory:
sles15-db2-root:/opt/ibm/db2/fixpack/instance $ ./db2iupdt -d db2inst1
DBI1446I The db2iupdt command is running.
DB2 installation is being initialized.
The DB2 installer detects that one or more DB2 instances "db2inst1" are still
active. Stop the active instances and rerun the command again.
A major error occurred during the execution that caused this program to
terminate prematurely. If the problem persists, contact your technical service
representative.
For more information see the DB2 installation log at "/tmp/db2iupdt.log.13332".
DBI1264E This program failed. Errors encountered during execution were
written to the installation log file. Program name:
db2iupdt. Log file name: /tmp/db2iupdt.log.13332.
Explanation:
This message is returned when some processes and operations have failed.
Detailed information about the error was written to the log file.
User response:
Contact IBM support to get assistance in resolving this issue. Keep the
log file intact as this file is an important reference for IBM support.
Related information:
Contacting IBM Software Support
I would have been surprised if you could update the instance without shutting it down before, so this is somehow expected:
db2inst1@sles15-db2-root:~> db2stop 01/21/2022 09:57:39 0 0 SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. db2inst1@sles15-db2-root:~> ps -ef | grep db2 root 1051 1049 0 09:41 ? 00:00:00 sshd: db2inst1 [priv] db2inst1 1055 1 0 09:41 ? 00:00:00 /usr/lib/systemd/systemd --user db2inst1 1056 1055 0 09:41 ? 00:00:00 (sd-pam) db2inst1 1063 1051 0 09:41 ? 00:00:00 sshd: db2inst1@pts/0 db2inst1 1064 1063 0 09:41 pts/0 00:00:00 -bash db2inst1 1476 1 0 09:41 pts/0 00:00:00 /home/db2inst1/sqllib/bin/db2bp 1064A1004 5 A root 14155 1 0 09:56 ? 00:00:00 /opt/ibm/db2/V11.5/bin/db2fmcd db2inst1 14180 28023 0 09:57 pts/1 00:00:00 ps -ef db2inst1 14181 28023 0 09:57 pts/1 00:00:00 grep --color=auto db2 root 27014 1049 0 09:52 ? 00:00:00 sshd: db2inst1 [priv] db2inst1 27995 27014 0 09:52 ? 00:00:00 sshd: db2inst1@pts/1 db2inst1 28023 27995 0 09:52 pts/1 00:00:00 -bash
Next try:
sles15-db2-root:/opt/ibm/db2/fixpack/instance $ ./db2iupdt -d db2inst1 DBI1446I The db2iupdt command is running. DB2 installation is being initialized. Total number of tasks to be performed: 4 Total estimated time for all tasks to be performed: 309 second(s) Task #1 start Description: Setting default global profile registry variables Estimated time 1 second(s) Task #1 end Task #2 start Description: Initializing instance list Estimated time 5 second(s) Task #2 end Task #3 start Description: Configuring DB2 instances Estimated time 300 second(s) Task #3 end Task #4 start Description: Updating global profile registry Estimated time 3 second(s) Task #4 end The execution completed successfully. For more information see the DB2 installation log at "/tmp/db2iupdt.log.14194". DBI1070I Program db2iupdt completed successfully.
All seems to be fine, so lets start it up and check the version:
db2inst1@sles15-db2-root:~> db2start
01/21/2022 09:58:44 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
db2inst1@sles15-db2-root:~> db2ls
Install Path Level Fix Pack Special Install Number Install Date Installer UID
---------------------------------------------------------------------------------------------------------------------
/opt/ibm/db2/V11.5 11.5.6.0 0 Thu Jan 20 12:05:28 2022 CET 0
/opt/ibm/db2/fixpack 11.5.7.0 0 Fri Jan 21 09:53:04 2022 CET 0
db2inst1@sles15-db2-root:~> db2
(c) Copyright IBM Corporation 1993,2007
Command Line Processor for DB2 Client 11.5.7.0
You can issue database manager commands and SQL statements from the command
prompt. For example:
db2 => connect to sample
db2 => bind sample.bnd
For general help, type: ?.
For command help, type: ? command, where command can be
the first few keywords of a database manager command. For example:
? CATALOG DATABASE for help on the CATALOG DATABASE command
? CATALOG for help on all of the CATALOG commands.
To exit db2 interactive mode, type QUIT at the command prompt. Outside
interactive mode, all commands must be prefixed with 'db2'.
To list the current command option settings, type LIST COMMAND OPTIONS.
For more detailed help, refer to the Online Reference Manual.
Looks good. Finally you should update the catalogs in your databases:
db2inst1@sles15-db2-root:~> db2updv115 -d db1
_________________________________________________________________________
_____ DB2 Service Tools _____
I B M
db2updv115
This tool is a service utility designed to update a DB2 Version 11.5
database to the current fix pack level.
_________________________________________________________________________
DB2 Universal Database Version 11.5, 5622-044 (c) Copyright IBM Corp. 2019
Licensed Material - Program Property of IBM
IBM DATABASE 2 Database update to current fix pack tool
db2updv115 completed successfully for database 'db1'.
Looking back at the output of db2ls I wondered why I have two lines in there:
db2inst1@sles15-db2-root:~> db2ls Install Path Level Fix Pack Special Install Number Install Date Installer UID --------------------------------------------------------------------------------------------------------------------- /opt/ibm/db2/V11.5 11.5.6.0 0 Thu Jan 20 12:05:28 2022 CET 0 /opt/ibm/db2/fixpack 11.5.7.0 0 Fri Jan 21 09:53:04 2022 CET 0
Checking the open files of one of the processes gives this:
sles15-db2-root:~/server_dec $ ps -ef | grep db2 | grep db2ckpwd root 2809 32564 0 10:58 pts/0 00:00:00 grep --color=auto db2ckpwd root 30065 30057 0 09:58 pts/1 00:00:00 db2ckpwd 0 root 30066 30057 0 09:58 pts/1 00:00:00 db2ckpwd 0 root 30067 30057 0 09:58 pts/1 00:00:00 db2ckpwd 0 sles15-db2-root:~/server_dec $ lsof -p 30065 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME db2syscr 30065 root cwd DIR 0,46 156 256 / db2syscr 30065 root rtd DIR 0,46 156 256 / db2syscr 30065 root txt REG 253,3 197000 12583070 /home/db2inst1/sqllib/adm/db2syscr db2syscr 30065 root DEL REG 0,1 7 /SYSV276cac61 db2syscr 30065 root DEL REG 0,1 8 /SYSV00000000 db2syscr 30065 root DEL REG 0,1 6 /SYSV276cac74 db2syscr 30065 root mem REG 0,46 340640 45411 /usr/lib/locale/en_US.utf8/LC_CTYPE db2syscr 30065 root mem REG 0,46 54 45152 /usr/lib/locale/en_US.utf8/LC_NUMERIC db2syscr 30065 root mem REG 0,46 2586930 45146 /usr/lib/locale/en_US.utf8/LC_COLLATE db2syscr 30065 root mem REG 0,46 41240 40191 /lib64/libnss_compat-2.31.so db2syscr 30065 root mem REG 0,46 235576 1702 /usr/lib64/liblzma.so.5.2.3 db2syscr 30065 root mem REG 0,46 92216 40244 /lib64/libz.so.1.2.11 db2syscr 30065 root mem REG 0,46 112624 1859 /usr/lib64/libaudit.so.1.0.0 db2syscr 30065 root mem REG 0,56 1932400 10339 /opt/ibm/db2/fixpack/lib64/libicuucdb2.so.55.1 db2syscr 30065 root mem REG 0,56 1629408 10336 /opt/ibm/db2/fixpack/lib64/libicuucdb2.so.44.2 db2syscr 30065 root mem REG 0,56 1542960 10337 /opt/ibm/db2/fixpack/lib64/libicuucdb2.so.38.1 db2syscr 30065 root mem REG 0,56 1232064 8885 /opt/ibm/db2/fixpack/lib64/libicuucdb2.so.32.1 db2syscr 30065 root mem REG 0,56 72528 10320 /opt/ibm/db2/fixpack/lib64/libiculxdb2.so.55.1 db2syscr 30065 root mem REG 0,56 73632 10341 /opt/ibm/db2/fixpack/lib64/libiculxdb2.so.44.2 db2syscr 30065 root mem REG 0,56 72096 10342 /opt/ibm/db2/fixpack/lib64/libiculxdb2.so.38.1 db2syscr 30065 root mem REG 0,56 55680 8830 /opt/ibm/db2/fixpack/lib64/libiculxdb2.so.32.1 db2syscr 30065 root mem REG 0,56 462224 10316 /opt/ibm/db2/fixpack/lib64/libiculedb2.so.55.1 db2syscr 30065 root mem REG 0,56 315536 10335 /opt/ibm/db2/fixpack/lib64/libiculedb2.so.44.2 db2syscr 30065 root mem REG 0,56 296344 10311 /opt/ibm/db2/fixpack/lib64/libiculedb2.so.38.1 db2syscr 30065 root mem REG 0,56 312096 8889 /opt/ibm/db2/fixpack/lib64/libiculedb2.so.32.1 db2syscr 30065 root mem REG 0,56 71192 10338 /opt/ibm/db2/fixpack/lib64/libicuiodb2.so.55.1 db2syscr 30065 root mem REG 0,56 65936 10328 /opt/ibm/db2/fixpack/lib64/libicuiodb2.so.44.2 db2syscr 30065 root mem REG 0,56 65576 10331 /opt/ibm/db2/fixpack/lib64/libicuiodb2.so.38.1 db2syscr 30065 root mem REG 0,56 65600 8903 /opt/ibm/db2/fixpack/lib64/libicuiodb2.so.32.1 db2syscr 30065 root mem REG 0,56 3148400 10321 /opt/ibm/db2/fixpack/lib64/libicui18ndb2.so.55.1 db2syscr 30065 root mem REG 0,56 2354488 10310 /opt/ibm/db2/fixpack/lib64/libicui18ndb2.so.44.2 db2syscr 30065 root mem REG 0,56 1648208 10322 /opt/ibm/db2/fixpack/lib64/libicui18ndb2.so.38.1 db2syscr 30065 root mem REG 0,56 1507104 8900 /opt/ibm/db2/fixpack/lib64/libicui18ndb2.so.32.1 db2syscr 30065 root mem REG 0,56 20194496 10334 /opt/ibm/db2/fixpack/lib64/libicudatadb2.so.55.1 db2syscr 30065 root mem REG 0,56 11048128 10317 /opt/ibm/db2/fixpack/lib64/libicudatadb2.so.44.2 db2syscr 30065 root mem REG 0,56 6980792 10325 /opt/ibm/db2/fixpack/lib64/libicudatadb2.so.38.1 db2syscr 30065 root mem REG 0,56 9780656 8866 /opt/ibm/db2/fixpack/lib64/libicudatadb2.so.32.1 db2syscr 30065 root mem REG 0,56 612696 8875 /opt/ibm/db2/fixpack/lib64/libdb2sdbin.so.1 db2syscr 30065 root mem REG 0,56 156632 8878 /opt/ibm/db2/fixpack/lib64/libdb2locale.so.1 db2syscr 30065 root mem REG 0,56 228488 8854 /opt/ibm/db2/fixpack/lib64/libdb2genreg.so.1 db2syscr 30065 root mem REG 0,56 657544 10852 /opt/ibm/db2/fixpack/lib64/libdb2dstf.so.1 db2syscr 30065 root mem REG 0,56 5850192 8890 /opt/ibm/db2/fixpack/lib64/libDB2xslt4c.so.112.0 db2syscr 30065 root mem REG 0,56 536376 8919 /opt/ibm/db2/fixpack/lib64/libDB2xml4c-depdom.so.58.0 db2syscr 30065 root mem REG 0,56 4259416 8868 /opt/ibm/db2/fixpack/lib64/libDB2xml4c.so.58.0 db2syscr 30065 root mem REG 0,56 46920 8837 /opt/ibm/db2/fixpack/lib64/libDB2xalanMsg.so.112.0 db2syscr 30065 root mem REG 0,46 48288 62219 /usr/lib64/libnuma.so.1.0.0 db2syscr 30065 root mem REG 0,46 1473368 2648 /usr/lib64/libxml2.so.2.9.7 db2syscr 30065 root mem REG 0,46 64232 45768 /lib64/libpam.so.0.84.2 db2syscr 30065 root mem REG 0,46 40240 40205 /lib64/librt-2.31.so db2syscr 30065 root mem REG 0,46 17840 40183 /lib64/libdl-2.31.so db2syscr 30065 root mem REG 0,46 202736 1810 /usr/lib64/libcrypt.so.1.1.0 db2syscr 30065 root mem REG 0,46 5608 1874 /lib64/libaio.so.1.0.1 db2syscr 30065 root mem REG 0,56 8316600 8839 /opt/ibm/db2/fixpack/lib64/libdb2g11n.so.1 db2syscr 30065 root mem REG 0,46 2163888 40181 /lib64/libc-2.31.so db2syscr 30065 root mem REG 0,46 101024 40311 /lib64/libgcc_s.so.1 db2syscr 30065 root mem REG 0,46 1419880 40185 /lib64/libm-2.31.so db2syscr 30065 root mem REG 0,46 2161776 40439 /usr/lib64/libstdc++.so.6.0.29 db2syscr 30065 root mem REG 0,56 6207992 8842 /opt/ibm/db2/fixpack/lib64/libdb2osse.so.1 db2syscr 30065 root mem REG 0,56 302123664 10859 /opt/ibm/db2/fixpack/lib64/libdb2e.so.1 db2syscr 30065 root mem REG 0,56 4327000 10870 /opt/ibm/db2/fixpack/lib64/libdb2thrift.so.1 db2syscr 30065 root mem REG 0,46 147304 40201 /lib64/libpthread-2.31.so db2syscr 30065 root mem REG 0,46 192696 40173 /lib64/ld-2.31.so db2syscr 30065 root mem REG 0,46 3284 45155 /usr/lib/locale/en_US.utf8/LC_TIME db2syscr 30065 root mem REG 0,46 286 45150 /usr/lib/locale/en_US.utf8/LC_MONETARY db2syscr 30065 root mem REG 0,46 57 45149 /usr/lib/locale/en_US.utf8/LC_MESSAGES/SYS_LC_MESSAGES db2syscr 30065 root mem REG 0,46 34 45153 /usr/lib/locale/en_US.utf8/LC_PAPER db2syscr 30065 root mem REG 0,46 77 45151 /usr/lib/locale/en_US.utf8/LC_NAME db2syscr 30065 root mem REG 0,56 22360 8899 /opt/ibm/db2/fixpack/lib64/libdb2install.so.1 db2syscr 30065 root mem REG 0,56 16976 10919 /opt/ibm/db2/fixpack/lib64/libdb2encr.so.1 db2syscr 30065 root mem REG 0,56 125184 8887 /opt/ibm/db2/fixpack/lib64/libdb2dascmn.so.1 db2syscr 30065 root mem REG 0,56 17080 10900 /opt/ibm/db2/fixpack/lib64/libdb2compr_encr.so.1 db2syscr 30065 root mem REG 0,56 20504 10868 /opt/ibm/db2/fixpack/lib64/libdb2compr.so.1 db2syscr 30065 root mem REG 0,56 485200 8844 /opt/ibm/db2/fixpack/lib64/libdb2cftrace.so.1 db2syscr 30065 root mem REG 0,56 532336 8881 /opt/ibm/db2/fixpack/lib64/libdb2cf_api.so.1 db2syscr 30065 root mem REG 0,56 70488 8857 /opt/ibm/db2/fixpack/lib64/libdb2trcapi.so.1 db2syscr 30065 root mem REG 0,56 576944 8880 /opt/ibm/db2/fixpack/lib64/libdb2osse_db2.so.1 db2syscr 30065 root mem REG 0,46 167 45145 /usr/lib/locale/en_US.utf8/LC_ADDRESS db2syscr 30065 root mem REG 0,46 59 45154 /usr/lib/locale/en_US.utf8/LC_TELEPHONE db2syscr 30065 root mem REG 0,46 23 45148 /usr/lib/locale/en_US.utf8/LC_MEASUREMENT db2syscr 30065 root mem REG 0,46 26988 45412 /usr/lib64/gconv/gconv-modules.cache db2syscr 30065 root mem REG 0,46 369 45147 /usr/lib/locale/en_US.utf8/LC_IDENTIFICATION db2syscr 30065 root 0u CHR 1,3 0t0 9522 /dev/null db2syscr 30065 root 1u CHR 1,3 0t0 9522 /dev/null db2syscr 30065 root 2u CHR 1,3 0t0 9522 /dev/null
This confirms that the files of the new location of the Fix Pack are used, and not anymore those of the initial installation. I probably should have chosen a better naming for the directory, as “fixpack” really is not a good choice here.
Cet article Patching an IBM Db2 instance est apparu en premier sur Blog dbi services.