{"id":260,"date":"2022-01-21T19:12:08","date_gmt":"2022-01-21T18:12:08","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=260"},"modified":"2022-04-06T08:27:01","modified_gmt":"2022-04-06T06:27:01","slug":"patching-an-ibm-db2-instance","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/","title":{"rendered":"Patching an IBM Db2 instance"},"content":{"rendered":"

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<\/a>. 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<\/a>, the downloads are here<\/a>. Lets go.<\/p>\n

<\/p>\n

I’ll use the installation from the last post<\/a>, which means this is a root installation. The current version of my Db2 instance is 11.5.6.0:<\/p>\n

\ndb2inst1@sles15-db2-root:~> db2ls\n\nInstall Path                       Level   Fix Pack   Special Install Number   Install Date                  Installer UID \n---------------------------------------------------------------------------------------------------------------------\n\/opt\/ibm\/db2\/V11.5               11.5.6.0        0                            Thu Jan 20 12:05:28 2022 CET             0 \n<\/pre>\n
After downloading the latest pack and putting it in the home directory of the root user it looks like this:<\/p>\n
\ndb2 => quit\nDB20000I  The QUIT command completed successfully.\ndb2inst1@sles15-db2-root:~> su -\nPassword: \nsles15-db2-root:~ $ ls -l\ntotal 1826112\n-rw------- 1 root root         61 Jan 20 13:14 .Xauthority\n-rw------- 1 root root       2376 Jan 20 15:25 .bash_history\ndrwx------ 1 root root          0 Mar  3  2021 .gnupg\n-rw------- 1 root root       1402 Jan 20 15:25 .viminfo\ndrwxr-xr-x 1 root root          0 Mar  3  2021 bin\ndrwxr-xr-x 1 root root         36 Jul  9  2021 inst-sys\n-rw-r--r-- 1 root root 1869925829 Jan 21 09:42 v11.5.7_linuxx64_server_dec.tar.gz\n<\/pre>\n
Not much different from the initial installation, once you extract that you’ll get the “server_dec” directory:<\/p>\n
\nsles15-db2-root:~ $ tar axf v11.5.7_linuxx64_server_dec.tar.gz \nsles15-db2-root:~ $ ls -l\ntotal 1826112\n-rw------- 1 root root         61 Jan 20 13:14 .Xauthority\n-rw------- 1 root root       2376 Jan 20 15:25 .bash_history\ndrwx------ 1 root root          0 Mar  3  2021 .gnupg\n-rw------- 1 root root       1402 Jan 20 15:25 .viminfo\ndrwxr-xr-x 1 root root          0 Mar  3  2021 bin\ndrwxr-xr-x 1 root root         36 Jul  9  2021 inst-sys\ndrwxr-xr-x 1 root root        240 Nov 22 19:36 server_dec\n-rw-r--r-- 1 root root 1869925829 Jan 21 09:42 v11.5.7_linuxx64_server_dec.tar.gz\nsles15-db2-root:~ $ rm v11.5.7_linuxx64_server_dec.tar.gz  \n<\/pre>\n
Inside this directory you’ll “installFixPack”, which is a plain shell script:<\/p>\n
\nsles15-db2-root:~ # cd server_dec\/\nsles15-db2-root:~\/server_dec # ls -l\ntotal 84\ndrwxr-xr-x 1 bin bin   112 Nov 22 19:36 db2\n-r-xr-xr-x 1 bin bin  5207 Nov 22 19:36 db2_deinstall\n-r-xr-xr-x 1 bin bin  5077 Nov 22 19:36 db2_install\n-r--r--r-- 1 bin bin 16809 Nov 22 19:36 db2checkCOL.tar.gz\n-r--r--r-- 1 bin bin  4987 Nov 22 19:36 db2checkCOL_readme.txt\n-r-xr-xr-x 1 bin bin  5254 Nov 22 19:36 db2ckupgrade\n-r-xr-xr-x 1 bin bin  5041 Nov 22 19:36 db2ls\n-r-xr-xr-x 1 bin bin  5059 Nov 22 19:36 db2prereqcheck\n-r-xr-xr-x 1 bin bin  5059 Nov 22 19:36 db2setup\n-r-xr-xr-x 1 bin bin  5095 Nov 22 19:36 installFixPack\n<\/pre>\n
The parameters<\/a> you need to pass to that script, are the current location of installation and a new directory where the pack gets installed. Lets try:<\/p>\n
\nsles15-db2-root:~\/server_dec $ .\/installFixPack -b \/opt\/ibm\/db2\/V11.5\/ -p \/opt\/ibm\/db2\/fixpack\/\nRequirement not matched for DB2 database \"Server\" . Version: \"11.5.7.0\". \n\nSummary of prerequisites that are not met on the current system: \n\nDBT3507E  The db2prereqcheck utility failed to find the following package or file: \"mksh\". \n\n\nDBT3619W  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. \n\n  Aborting the current installation ...\n  Run installation with the option \"-f sysreq\" parameter to force the installation.\n<\/pre>\n
Ok, apparently we need a KornShell<\/a> to install that:<\/p>\n
\nsles15-db2-root:~\/server_dec $ zypper in -y mksh ksh\n<\/pre>\n
Next try:<\/p>\n
\nsles15-db2-root:~\/server_dec $ .\/installFixPack -b \/opt\/ibm\/db2\/V11.5\/ -p \/opt\/ibm\/db2\/fixpack\/\nRead the license agreement file in the db2\/license directory.\n\n***********************************************************\nTo accept those terms, enter \"yes\". Otherwise, enter \"no\" to cancel the install process. [yes\/no]\nyes\nDBI1017I  installFixPack is updating the database products installed in\n      location \/opt\/ibm\/db2\/V11.5\/.\n\n\nDB2 installation is being initialized.\n\n Total number of tasks to be performed: 53 \nTotal estimated time for all tasks to be performed: 2552 second(s) \n\nTask #1 start\nDescription: Preparing the system \nEstimated time 120 second(s) \nTask #1 end \n\nTask #2 start\nDescription: Base Client Support for installation with root privileges \nEstimated time 3 second(s) \nTask #2 end \n\nTask #3 start\nDescription: Product Messages - English \nEstimated time 14 second(s) \nTask #3 end \n\nTask #4 start\nDescription: Base client support \nEstimated time 360 second(s) \nTask #4 end \n\nTask #5 start\nDescription: Java Runtime Support \nEstimated time 215 second(s) \nTask #5 end \n\nTask #6 start\nDescription: Java Help (HTML) - English \nEstimated time 7 second(s) \nTask #6 end \n\nTask #7 start\nDescription: Base server support for installation with root privileges \nEstimated time 6 second(s) \nTask #7 end \n\nTask #8 start\nDescription: Global Secure ToolKit \nEstimated time 76 second(s) \nTask #8 end \n\nTask #9 start\nDescription: Java support \nEstimated time 11 second(s) \nTask #9 end \n\nTask #10 start\nDescription: SQL procedures \nEstimated time 3 second(s) \nTask #10 end \n\nTask #11 start\nDescription: ICU Utilities \nEstimated time 59 second(s) \nTask #11 end \n\nTask #12 start\nDescription: Java Common files \nEstimated time 18 second(s) \nTask #12 end \n\nTask #13 start\nDescription: Base server support \nEstimated time 610 second(s) \nTask #13 end \n\nTask #14 start\nDescription: Control Center Help (HTML) - English \nEstimated time 13 second(s) \nTask #14 end \n\nTask #15 start\nDescription: Relational wrappers common \nEstimated time 3 second(s) \nTask #15 end \n\nTask #16 start\nDescription: DB2 data source support \nEstimated time 6 second(s) \nTask #16 end \n\nTask #17 start\nDescription: ODBC data source support \nEstimated time 260 second(s) \nTask #17 end \n\nTask #18 start\nDescription: Teradata data source support \nEstimated time 3 second(s) \nTask #18 end \n\nTask #19 start\nDescription: Spatial Extender server support \nEstimated time 21 second(s) \nTask #19 end \n\nTask #20 start\nDescription: Scientific Data Sources \nEstimated time 5 second(s) \nTask #20 end \n\nTask #21 start\nDescription: JDBC data source support \nEstimated time 185 second(s) \nTask #21 end \n\nTask #22 start\nDescription: IBM Software Development Kit (SDK) for Java(TM) \nEstimated time 49 second(s) \nTask #22 end \n\nTask #23 start\nDescription: DB2 LDAP support \nEstimated time 4 second(s) \nTask #23 end \n\nTask #24 start\nDescription: DB2 Instance Setup wizard \nEstimated time 23 second(s) \nTask #24 end \n\nTask #25 start\nDescription: Structured file data sources \nEstimated time 5 second(s) \nTask #25 end \n\nTask #26 start\nDescription: Integrated Flash Copy Support \nEstimated time 3 second(s) \nTask #26 end \n\nTask #27 start\nDescription: Oracle data source support \nEstimated time 4 second(s) \nTask #27 end \n\nTask #28 start\nDescription: Connect support \nEstimated time 3 second(s) \nTask #28 end \n\nTask #29 start\nDescription: Application data sources \nEstimated time 4 second(s) \nTask #29 end \n\nTask #30 start\nDescription: Spatial Extender client \nEstimated time 3 second(s) \nTask #30 end \n\nTask #31 start\nDescription: SQL Server data source support \nEstimated time 4 second(s) \nTask #31 end \n\nTask #32 start\nDescription: Communication support - TCP\/IP \nEstimated time 3 second(s) \nTask #32 end \n\nTask #33 start\nDescription: Base application development tools \nEstimated time 36 second(s) \nTask #33 end \n\nTask #34 start\nDescription: Parallel Extension \nEstimated time 3 second(s) \nTask #34 end \n\nTask #35 start\nDescription: EnterpriseDB code \nEstimated time 3 second(s) \nTask #35 end \n\nTask #36 start\nDescription: Replication tools \nEstimated time 60 second(s) \nTask #36 end \n\nTask #37 start\nDescription: Sample database source \nEstimated time 4 second(s) \nTask #37 end \n\nTask #38 start\nDescription: itlm \nEstimated time 3 second(s) \nTask #38 end \n\nTask #39 start\nDescription: DB2 Text Search \nEstimated time 108 second(s) \nTask #39 end \n\nTask #40 start\nDescription: Command Line Processor Plus \nEstimated time 8 second(s) \nTask #40 end \n\nTask #41 start\nDescription: Sybase data source support \nEstimated time 3 second(s) \nTask #41 end \n\nTask #42 start\nDescription: Informix data source support \nEstimated time 4 second(s) \nTask #42 end \n\nTask #43 start\nDescription: Federated Data Access Support \nEstimated time 3 second(s) \nTask #43 end \n\nTask #44 start\nDescription: First Steps \nEstimated time 3 second(s) \nTask #44 end \n\nTask #45 start\nDescription: Pacemaker \nEstimated time 100 second(s) \nTask #45 end \n\nTask #46 start\nDescription: Product Signature for DB2 Server Edition \nEstimated time 6 second(s) \nTask #46 end \n\nTask #47 start\nDescription: Guardium Installation Manager Client \nEstimated time 36 second(s) \nTask #47 end \n\nTask #48 start\nDescription: Setting DB2 library path \nEstimated time 180 second(s) \nTask #48 end \n\nTask #49 start\nDescription: Installing or updating Db2 resource agent scripts for Pacemaker \nEstimated time 20 second(s) \nTask #49 end \n\nTask #50 start\nDescription: Executing control tasks \nEstimated time 20 second(s) \nTask #50 end \n\nTask #51 start\nDescription: Updating global registry \nEstimated time 20 second(s) \nTask #51 end \n\nTask #52 start\nDescription: Updating the db2ls and db2greg link \nEstimated time 1 second(s) \nTask #52 end \n\nTask #53 start\nDescription: Registering DB2 licenses \nEstimated time 5 second(s) \nTask #53 end \n\nThe execution completed successfully.\n\nFor more information see the DB2 installation log at\n\"\/tmp\/installFixPack.log.4317\".\n<\/pre>\n
Very much the same output\/steps as in with the initial installation. All looks fine. This was the installation of all the files:<\/p>\n
\nsles15-db2-root:~\/server_dec $ cd \/opt\/ibm\/db2\/fixpack\/\nsles15-db2-root:\/opt\/ibm\/db2\/fixpack $ ls -l\ntotal 4\ndrwx--x--x 1 root root    30 Jan 21 09:53 .licbkup\ndrwxr-xr-x 1 root root  1696 Nov 22 19:31 .metadata\ndrwxr-xr-x 1 bin  bin      6 Nov 22 19:28 R\ndrwxr-xr-x 1 bin  bin    296 Nov 22 19:27 Readme\ndrwxr-xr-x 1 bin  bin     18 Nov 22 19:27 acs\ndrwxr-xr-x 1 bin  bin    734 Nov 22 19:29 adm\ndrwxr-xr-x 1 bin  bin     76 Nov 22 19:28 adsm\ndrwxr-xr-x 1 bin  bin   4368 Nov 22 19:28 bin\ndrwxr-xr-x 1 bin  bin   5024 Nov 22 19:28 bnd\ndrwxr-xr-x 1 bin  bin   1090 Jan 21 09:53 cfg\ndrwxr-xr-x 1 bin  bin     10 Nov 22 19:27 conv\ndrwxr-xr-x 1 bin  bin     92 Nov 22 19:28 das\ndrwxr-xr-x 1 bin  bin    156 Nov 22 19:28 dasfcn\ndrwxr-xr-x 1 bin  bin     48 Nov 22 19:29 db2tss\ndrwxr-xr-x 1 bin  bin     84 Nov 22 19:28 desktop\ndrwxr-xr-x 1 bin  bin     12 Nov 22 19:28 doc\ndrwxr-xr-x 1 bin  bin     52 Nov 22 19:28 federation\ndrwxr-xr-x 1 bin  bin    100 Nov 22 19:28 function\ndrwxr-xr-x 1 bin  bin     24 Nov 22 19:28 gse\ndrwxr-xr-x 1 bin  bin     64 Nov 22 19:28 gskit\ndrwxr-xr-x 1 bin  bin    548 Nov 22 19:28 guardium\ndrwxr-xr-x 1 bin  bin     34 Nov 22 19:28 ha\ndrwxr-xr-x 1 bin  bin   2786 Nov 22 19:27 include\ndrwxr-xr-x 1 bin  bin     54 Nov 22 19:29 infopop\ndrwxr-xr-x 1 bin  bin    156 Jan 21 09:53 install\ndrwxr-xr-x 1 bin  bin    722 Nov 22 19:28 instance\ndrwxr-xr-x 1 bin  bin    352 Nov 22 19:27 java\ndrwxr-xr-x 1 bin  bin     38 Nov 22 19:27 json\ndrwxr-xr-x 1 bin  bin   1564 Jan 21 09:52 lib32\ndrwxr-xr-x 1 bin  bin  10328 Jan 21 09:52 lib64\ndrwxr-xr-x 1 bin  bin    932 Jan 21 09:53 license\nlrwxrwxrwx 1 root root    12 Nov 22 19:27 logs -> install\/logs\ndrwxr-xr-x 1 bin  bin     66 Nov 22 19:28 map\ndrwxr-xr-x 1 bin  bin    746 Nov 22 19:28 misc\ndrwxr-xr-x 1 bin  bin     28 Nov 22 19:28 msg\ndrwxr-xr-x 1 bin  bin    246 Nov 22 19:28 pd\ndrwxr-xr-x 1 bin  bin     14 Nov 22 19:28 properties\ndrwxr-xr-x 1 bin  bin     30 Nov 22 19:28 python\ndrwxr-xr-x 1 bin  bin    368 Nov 22 19:28 samples\ndrwxr-xr-x 1 bin  bin     12 Nov 22 19:28 security32\ndrwxr-xr-x 1 bin  bin    108 Nov 22 19:28 security64\ndrwxr-xr-x 1 bin  bin   1796 Nov 22 19:28 tools\n<\/pre>\n
Now we need to patch the instance, this is done with db2iupdt<\/a> which is located in the “instance” directory:<\/p>\n
\nsles15-db2-root:\/opt\/ibm\/db2\/fixpack\/instance $ .\/db2iupdt -d db2inst1\nDBI1446I  The db2iupdt command is running.\n\n\nDB2 installation is being initialized.\n\n The DB2 installer detects that one or more DB2 instances \"db2inst1\" are still\nactive. Stop the active instances and rerun the command again.\n\nA major error occurred during the execution that caused this program to\nterminate prematurely. If the problem persists, contact your technical service\nrepresentative.\n\nFor more information see the DB2 installation log at \"\/tmp\/db2iupdt.log.13332\".\nDBI1264E  This program failed. Errors encountered during execution were\n      written to the installation log file. Program name:\n      db2iupdt. Log file name: \/tmp\/db2iupdt.log.13332.\n\nExplanation: \n\nThis message is returned when some processes and operations have failed.\nDetailed information about the error was written to the log file.\n\nUser response: \n\nContact IBM support to get assistance in resolving this issue. Keep the\nlog file intact as this file is an important reference for IBM support.\n\n\n   Related information:\n   Contacting IBM Software Support\n<\/pre>\n
I would have been surprised if you could update the instance without shutting it down before, so this is somehow expected:<\/p>\n
\ndb2inst1@sles15-db2-root:~> db2stop\n01\/21\/2022 09:57:39     0   0   SQL1064N  DB2STOP processing was successful.\nSQL1064N  DB2STOP processing was successful.\ndb2inst1@sles15-db2-root:~> ps -ef | grep db2\nroot      1051  1049  0 09:41 ?        00:00:00 sshd: db2inst1 [priv]\ndb2inst1  1055     1  0 09:41 ?        00:00:00 \/usr\/lib\/systemd\/systemd --user\ndb2inst1  1056  1055  0 09:41 ?        00:00:00 (sd-pam)\ndb2inst1  1063  1051  0 09:41 ?        00:00:00 sshd: db2inst1@pts\/0\ndb2inst1  1064  1063  0 09:41 pts\/0    00:00:00 -bash\ndb2inst1  1476     1  0 09:41 pts\/0    00:00:00 \/home\/db2inst1\/sqllib\/bin\/db2bp 1064A1004 5 A\nroot     14155     1  0 09:56 ?        00:00:00 \/opt\/ibm\/db2\/V11.5\/bin\/db2fmcd\ndb2inst1 14180 28023  0 09:57 pts\/1    00:00:00 ps -ef\ndb2inst1 14181 28023  0 09:57 pts\/1    00:00:00 grep --color=auto db2\nroot     27014  1049  0 09:52 ?        00:00:00 sshd: db2inst1 [priv]\ndb2inst1 27995 27014  0 09:52 ?        00:00:00 sshd: db2inst1@pts\/1\ndb2inst1 28023 27995  0 09:52 pts\/1    00:00:00 -bash\n<\/pre>\n
Next try:<\/p>\n
\nsles15-db2-root:\/opt\/ibm\/db2\/fixpack\/instance $ .\/db2iupdt -d db2inst1\nDBI1446I  The db2iupdt command is running.\n\n\nDB2 installation is being initialized.\n\n Total number of tasks to be performed: 4 \nTotal estimated time for all tasks to be performed: 309 second(s) \n\nTask #1 start\nDescription: Setting default global profile registry variables \nEstimated time 1 second(s) \nTask #1 end \n\nTask #2 start\nDescription: Initializing instance list \nEstimated time 5 second(s) \nTask #2 end \n\nTask #3 start\nDescription: Configuring DB2 instances \nEstimated time 300 second(s) \nTask #3 end \n\nTask #4 start\nDescription: Updating global profile registry \nEstimated time 3 second(s) \nTask #4 end \n\nThe execution completed successfully.\n\nFor more information see the DB2 installation log at \"\/tmp\/db2iupdt.log.14194\".\nDBI1070I  Program db2iupdt completed successfully.\n<\/pre>\n
All seems to be fine, so lets start it up and check the version:<\/p>\n
\ndb2inst1@sles15-db2-root:~> db2start\n01\/21\/2022 09:58:44     0   0   SQL1063N  DB2START processing was successful.\nSQL1063N  DB2START processing was successful.\ndb2inst1@sles15-db2-root:~> db2ls\n\nInstall Path                       Level   Fix Pack   Special Install Number   Install Date                  Installer UID \n---------------------------------------------------------------------------------------------------------------------\n\/opt\/ibm\/db2\/V11.5               11.5.6.0        0                            Thu Jan 20 12:05:28 2022 CET             0 \n\/opt\/ibm\/db2\/fixpack             11.5.7.0        0                            Fri Jan 21 09:53:04 2022 CET             0 \n\n\n\ndb2inst1@sles15-db2-root:~> db2\n(c) Copyright IBM Corporation 1993,2007\nCommand Line Processor for DB2 Client 11.5.7.0\n\nYou can issue database manager commands and SQL statements from the command \nprompt. For example:\n    db2 => connect to sample\n    db2 => bind sample.bnd\n\nFor general help, type: ?.\nFor command help, type: ? command, where command can be\nthe first few keywords of a database manager command. For example:\n ? CATALOG DATABASE for help on the CATALOG DATABASE command\n ? CATALOG          for help on all of the CATALOG commands.\n\nTo exit db2 interactive mode, type QUIT at the command prompt. Outside \ninteractive mode, all commands must be prefixed with 'db2'.\nTo list the current command option settings, type LIST COMMAND OPTIONS.\n\nFor more detailed help, refer to the Online Reference Manual.\n<\/pre>\n
Looks good. Finally you should update the catalogs in your databases:<\/p>\n
\ndb2inst1@sles15-db2-root:~> db2updv115 -d db1\n\n\n_________________________________________________________________________     \n                                                                              \n                    _____   DB2 Service Tools   _____                         \n                                                                              \n                            I      B      M                                   \n                                                                              \n                               db2updv115                                      \n                                                                              \n   This tool is a service utility designed to update a DB2 Version 11.5       \n   database to the current fix pack level.                                    \n                                                                              \n_________________________________________________________________________     \n\n\nDB2 Universal Database Version 11.5, 5622-044 (c) Copyright IBM Corp. 2019\nLicensed Material - Program Property of IBM\nIBM DATABASE 2 Database update to current fix pack tool\n\ndb2updv115 completed successfully for database 'db1'. \n<\/pre>\n
Looking back at the output of db2ls I wondered why I have two lines in there:<\/p>\n
\ndb2inst1@sles15-db2-root:~> db2ls\n\nInstall Path                       Level   Fix Pack   Special Install Number   Install Date                  Installer UID \n---------------------------------------------------------------------------------------------------------------------\n\/opt\/ibm\/db2\/V11.5               11.5.6.0        0                            Thu Jan 20 12:05:28 2022 CET             0 \n\/opt\/ibm\/db2\/fixpack             11.5.7.0        0                            Fri Jan 21 09:53:04 2022 CET             0 \n<\/pre>\n
Checking the open files of one of the processes gives this:<\/p>\n
\nsles15-db2-root:~\/server_dec $ ps -ef | grep db2 | grep db2ckpwd\nroot      2809 32564  0 10:58 pts\/0    00:00:00 grep --color=auto db2ckpwd\nroot     30065 30057  0 09:58 pts\/1    00:00:00 db2ckpwd 0\nroot     30066 30057  0 09:58 pts\/1    00:00:00 db2ckpwd 0\nroot     30067 30057  0 09:58 pts\/1    00:00:00 db2ckpwd 0\nsles15-db2-root:~\/server_dec $ lsof -p 30065\nCOMMAND    PID USER   FD   TYPE DEVICE  SIZE\/OFF     NODE NAME\ndb2syscr 30065 root  cwd    DIR   0,46       156      256 \/\ndb2syscr 30065 root  rtd    DIR   0,46       156      256 \/\ndb2syscr 30065 root  txt    REG  253,3    197000 12583070 \/home\/db2inst1\/sqllib\/adm\/db2syscr\ndb2syscr 30065 root  DEL    REG    0,1                  7 \/SYSV276cac61\ndb2syscr 30065 root  DEL    REG    0,1                  8 \/SYSV00000000\ndb2syscr 30065 root  DEL    REG    0,1                  6 \/SYSV276cac74\ndb2syscr 30065 root  mem    REG   0,46    340640    45411 \/usr\/lib\/locale\/en_US.utf8\/LC_CTYPE\ndb2syscr 30065 root  mem    REG   0,46        54    45152 \/usr\/lib\/locale\/en_US.utf8\/LC_NUMERIC\ndb2syscr 30065 root  mem    REG   0,46   2586930    45146 \/usr\/lib\/locale\/en_US.utf8\/LC_COLLATE\ndb2syscr 30065 root  mem    REG   0,46     41240    40191 \/lib64\/libnss_compat-2.31.so\ndb2syscr 30065 root  mem    REG   0,46    235576     1702 \/usr\/lib64\/liblzma.so.5.2.3\ndb2syscr 30065 root  mem    REG   0,46     92216    40244 \/lib64\/libz.so.1.2.11\ndb2syscr 30065 root  mem    REG   0,46    112624     1859 \/usr\/lib64\/libaudit.so.1.0.0\ndb2syscr 30065 root  mem    REG   0,56   1932400    10339 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuucdb2.so.55.1\ndb2syscr 30065 root  mem    REG   0,56   1629408    10336 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuucdb2.so.44.2\ndb2syscr 30065 root  mem    REG   0,56   1542960    10337 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuucdb2.so.38.1\ndb2syscr 30065 root  mem    REG   0,56   1232064     8885 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuucdb2.so.32.1\ndb2syscr 30065 root  mem    REG   0,56     72528    10320 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculxdb2.so.55.1\ndb2syscr 30065 root  mem    REG   0,56     73632    10341 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculxdb2.so.44.2\ndb2syscr 30065 root  mem    REG   0,56     72096    10342 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculxdb2.so.38.1\ndb2syscr 30065 root  mem    REG   0,56     55680     8830 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculxdb2.so.32.1\ndb2syscr 30065 root  mem    REG   0,56    462224    10316 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculedb2.so.55.1\ndb2syscr 30065 root  mem    REG   0,56    315536    10335 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculedb2.so.44.2\ndb2syscr 30065 root  mem    REG   0,56    296344    10311 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculedb2.so.38.1\ndb2syscr 30065 root  mem    REG   0,56    312096     8889 \/opt\/ibm\/db2\/fixpack\/lib64\/libiculedb2.so.32.1\ndb2syscr 30065 root  mem    REG   0,56     71192    10338 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuiodb2.so.55.1\ndb2syscr 30065 root  mem    REG   0,56     65936    10328 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuiodb2.so.44.2\ndb2syscr 30065 root  mem    REG   0,56     65576    10331 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuiodb2.so.38.1\ndb2syscr 30065 root  mem    REG   0,56     65600     8903 \/opt\/ibm\/db2\/fixpack\/lib64\/libicuiodb2.so.32.1\ndb2syscr 30065 root  mem    REG   0,56   3148400    10321 \/opt\/ibm\/db2\/fixpack\/lib64\/libicui18ndb2.so.55.1\ndb2syscr 30065 root  mem    REG   0,56   2354488    10310 \/opt\/ibm\/db2\/fixpack\/lib64\/libicui18ndb2.so.44.2\ndb2syscr 30065 root  mem    REG   0,56   1648208    10322 \/opt\/ibm\/db2\/fixpack\/lib64\/libicui18ndb2.so.38.1\ndb2syscr 30065 root  mem    REG   0,56   1507104     8900 \/opt\/ibm\/db2\/fixpack\/lib64\/libicui18ndb2.so.32.1\ndb2syscr 30065 root  mem    REG   0,56  20194496    10334 \/opt\/ibm\/db2\/fixpack\/lib64\/libicudatadb2.so.55.1\ndb2syscr 30065 root  mem    REG   0,56  11048128    10317 \/opt\/ibm\/db2\/fixpack\/lib64\/libicudatadb2.so.44.2\ndb2syscr 30065 root  mem    REG   0,56   6980792    10325 \/opt\/ibm\/db2\/fixpack\/lib64\/libicudatadb2.so.38.1\ndb2syscr 30065 root  mem    REG   0,56   9780656     8866 \/opt\/ibm\/db2\/fixpack\/lib64\/libicudatadb2.so.32.1\ndb2syscr 30065 root  mem    REG   0,56    612696     8875 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2sdbin.so.1\ndb2syscr 30065 root  mem    REG   0,56    156632     8878 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2locale.so.1\ndb2syscr 30065 root  mem    REG   0,56    228488     8854 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2genreg.so.1\ndb2syscr 30065 root  mem    REG   0,56    657544    10852 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2dstf.so.1\ndb2syscr 30065 root  mem    REG   0,56   5850192     8890 \/opt\/ibm\/db2\/fixpack\/lib64\/libDB2xslt4c.so.112.0\ndb2syscr 30065 root  mem    REG   0,56    536376     8919 \/opt\/ibm\/db2\/fixpack\/lib64\/libDB2xml4c-depdom.so.58.0\ndb2syscr 30065 root  mem    REG   0,56   4259416     8868 \/opt\/ibm\/db2\/fixpack\/lib64\/libDB2xml4c.so.58.0\ndb2syscr 30065 root  mem    REG   0,56     46920     8837 \/opt\/ibm\/db2\/fixpack\/lib64\/libDB2xalanMsg.so.112.0\ndb2syscr 30065 root  mem    REG   0,46     48288    62219 \/usr\/lib64\/libnuma.so.1.0.0\ndb2syscr 30065 root  mem    REG   0,46   1473368     2648 \/usr\/lib64\/libxml2.so.2.9.7\ndb2syscr 30065 root  mem    REG   0,46     64232    45768 \/lib64\/libpam.so.0.84.2\ndb2syscr 30065 root  mem    REG   0,46     40240    40205 \/lib64\/librt-2.31.so\ndb2syscr 30065 root  mem    REG   0,46     17840    40183 \/lib64\/libdl-2.31.so\ndb2syscr 30065 root  mem    REG   0,46    202736     1810 \/usr\/lib64\/libcrypt.so.1.1.0\ndb2syscr 30065 root  mem    REG   0,46      5608     1874 \/lib64\/libaio.so.1.0.1\ndb2syscr 30065 root  mem    REG   0,56   8316600     8839 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2g11n.so.1\ndb2syscr 30065 root  mem    REG   0,46   2163888    40181 \/lib64\/libc-2.31.so\ndb2syscr 30065 root  mem    REG   0,46    101024    40311 \/lib64\/libgcc_s.so.1\ndb2syscr 30065 root  mem    REG   0,46   1419880    40185 \/lib64\/libm-2.31.so\ndb2syscr 30065 root  mem    REG   0,46   2161776    40439 \/usr\/lib64\/libstdc++.so.6.0.29\ndb2syscr 30065 root  mem    REG   0,56   6207992     8842 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2osse.so.1\ndb2syscr 30065 root  mem    REG   0,56 302123664    10859 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2e.so.1\ndb2syscr 30065 root  mem    REG   0,56   4327000    10870 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2thrift.so.1\ndb2syscr 30065 root  mem    REG   0,46    147304    40201 \/lib64\/libpthread-2.31.so\ndb2syscr 30065 root  mem    REG   0,46    192696    40173 \/lib64\/ld-2.31.so\ndb2syscr 30065 root  mem    REG   0,46      3284    45155 \/usr\/lib\/locale\/en_US.utf8\/LC_TIME\ndb2syscr 30065 root  mem    REG   0,46       286    45150 \/usr\/lib\/locale\/en_US.utf8\/LC_MONETARY\ndb2syscr 30065 root  mem    REG   0,46        57    45149 \/usr\/lib\/locale\/en_US.utf8\/LC_MESSAGES\/SYS_LC_MESSAGES\ndb2syscr 30065 root  mem    REG   0,46        34    45153 \/usr\/lib\/locale\/en_US.utf8\/LC_PAPER\ndb2syscr 30065 root  mem    REG   0,46        77    45151 \/usr\/lib\/locale\/en_US.utf8\/LC_NAME\ndb2syscr 30065 root  mem    REG   0,56     22360     8899 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2install.so.1\ndb2syscr 30065 root  mem    REG   0,56     16976    10919 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2encr.so.1\ndb2syscr 30065 root  mem    REG   0,56    125184     8887 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2dascmn.so.1\ndb2syscr 30065 root  mem    REG   0,56     17080    10900 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2compr_encr.so.1\ndb2syscr 30065 root  mem    REG   0,56     20504    10868 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2compr.so.1\ndb2syscr 30065 root  mem    REG   0,56    485200     8844 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2cftrace.so.1\ndb2syscr 30065 root  mem    REG   0,56    532336     8881 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2cf_api.so.1\ndb2syscr 30065 root  mem    REG   0,56     70488     8857 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2trcapi.so.1\ndb2syscr 30065 root  mem    REG   0,56    576944     8880 \/opt\/ibm\/db2\/fixpack\/lib64\/libdb2osse_db2.so.1\ndb2syscr 30065 root  mem    REG   0,46       167    45145 \/usr\/lib\/locale\/en_US.utf8\/LC_ADDRESS\ndb2syscr 30065 root  mem    REG   0,46        59    45154 \/usr\/lib\/locale\/en_US.utf8\/LC_TELEPHONE\ndb2syscr 30065 root  mem    REG   0,46        23    45148 \/usr\/lib\/locale\/en_US.utf8\/LC_MEASUREMENT\ndb2syscr 30065 root  mem    REG   0,46     26988    45412 \/usr\/lib64\/gconv\/gconv-modules.cache\ndb2syscr 30065 root  mem    REG   0,46       369    45147 \/usr\/lib\/locale\/en_US.utf8\/LC_IDENTIFICATION\ndb2syscr 30065 root    0u   CHR    1,3       0t0     9522 \/dev\/null\ndb2syscr 30065 root    1u   CHR    1,3       0t0     9522 \/dev\/null\ndb2syscr 30065 root    2u   CHR    1,3       0t0     9522 \/dev\/null\n<\/pre>\n
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.<\/p>\n","protected":false},"excerpt":{"rendered":"
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 […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[56],"type_dbi":[],"class_list":["post-260","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-db2"],"acf":[],"yoast_head":"\nPatching an IBM Db2 instance - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Patching an IBM Db2 instance\" \/>\n<meta property=\"og:description\" content=\"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 […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-01-21T18:12:08+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-04-06T06:27:01+00:00\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Patching an IBM Db2 instance\",\"datePublished\":\"2022-01-21T18:12:08+00:00\",\"dateModified\":\"2022-04-06T06:27:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/\"},\"wordCount\":358,\"commentCount\":1,\"keywords\":[\"DB2\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/\",\"name\":\"Patching an IBM Db2 instance - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2022-01-21T18:12:08+00:00\",\"dateModified\":\"2022-04-06T06:27:01+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/patching-an-ibm-db2-instance\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Patching an IBM Db2 instance\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\\\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\\\/\\\/x.com\\\/westermanndanie\"],\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/daniel-westermann\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Patching an IBM Db2 instance - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/","og_locale":"en_US","og_type":"article","og_title":"Patching an IBM Db2 instance","og_description":"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 […]","og_url":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/","og_site_name":"dbi Blog","article_published_time":"2022-01-21T18:12:08+00:00","article_modified_time":"2022-04-06T06:27:01+00:00","author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Patching an IBM Db2 instance","datePublished":"2022-01-21T18:12:08+00:00","dateModified":"2022-04-06T06:27:01+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/"},"wordCount":358,"commentCount":1,"keywords":["DB2"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/","url":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/","name":"Patching an IBM Db2 instance - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2022-01-21T18:12:08+00:00","dateModified":"2022-04-06T06:27:01+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/patching-an-ibm-db2-instance\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Patching an IBM Db2 instance"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/260","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=260"}],"version-history":[{"count":5,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/260\/revisions"}],"predecessor-version":[{"id":718,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/260\/revisions\/718"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=260"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=260"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=260"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=260"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}