Following on from my earlier posts: -
Following the script - installing IBM DB2 UDB using a response file ( silent installation )
Validating a successful DB2 UDB installation
I've also run through the process to automate the deployment of the 9.7.0.2 fix pack ( other fix packs are available ).
Unpack the fixpack
$ mkdir /tmp/fixpack
$ cd /tmp/fixpack
$ tar xvzf ~/v9.7fp2_linuxx64_universal_fixpack.tar.gz
Check the installed level
$ /tmp/fixpack/universal/db2ls
Install Path Level Fix Pack Special Install Number Install Date Installer UID
---------------------------------------------------------------------------------------------------------------------
/opt/ibm/db2/V9.7 9.7.0.1 1 Mon Jun 4 20:03:18 2012 BST 0
$ /opt/ibm/db2/V9.7/bin/db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09071"
with level identifier "08020107".
Informational tokens are "DB2 v9.7.0.1", "s091114", "IP23034", and Fix Pack
"1".
Product is installed at "/opt/ibm/db2/V9.7".
Install the fix pack
$ /tmp/fixpack/universal/installFixPack -b /opt/ibm/db2/V9.7
The execution completed successfully.
For more information see the DB2 installation log at
"/tmp/installFixPack.log.5821".
$ cat /tmp/installFixPack.log.5821
...
Updating DB2 file sets :.......Success
Setting DB2 library path :.......Success
Executing control tasks :.......Success
Updating global registry :.......Success
Starting DB2 Fault Monitor :.......Success
Updating the db2ls link :.......Success
Updating the DB2 Administration Server :.......Success
The instance "db2inst1" has been updated successfully.
The following instances were successfully updated: db2inst1
Updating existing DB2 instances :.......Success
...
Check the installed level
$ /tmp/fixpack/universal/db2ls
Install Path Level Fix Pack Special Install Number Install Date Installer UID
---------------------------------------------------------------------------------------------------------------------
/opt/ibm/db2/V9.7 9.7.0.2 2 Wed Jun 6 21:58:30 2012 BST 0
$ /opt/ibm/db2/V9.7/bin/db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09072"
with level identifier "08030107".
Informational tokens are "DB2 v9.7.0.2", "s100514", "IP23089", and Fix Pack
"2".
Product is installed at "/opt/ibm/db2/V9.7".
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Note to self - use kubectl to query images in a pod or deployment
In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
1 comment:
Cheers Dave, I was using ./installFixPack -b /opt/IBM/db2/db2inst1/sqllib/ which was failing.
Post a Comment