Right, the next instalment of the exciting series: -
Following the script - installing IBM HTTP Server using a response file ( silent installation )
Following the script - installing and using IBM WebSphere Update Installer using a response file ( silent installation )
Following the script - installing IBM Tivoli Directory Integrator using a response file ( silent installation )
is to install DB2 UDB 9.7 using a response file.
For some reason, DB2 doesn't ship with any sample response files on disk, so I needed to run through the GUI installation, and generate a response file. Thankfully, the GUI doesn't actually perform the installation, but merely generates the file - this is of use when installing onto multiple server nodes, especially where there's no GUI available.
So here is the response file in all its glory: -
LIC_AGREEMENT = ACCEPT
PROD = ENTERPRISE_SERVER_EDITION
FILE = /opt/ibm/db2/V9.7
INSTALL_TYPE = CUSTOM
COMP = COMMUNICATION_SUPPORT_TCPIP
COMP = JDK
COMP = JAVA_SUPPORT
COMP = BASE_DB2_ENGINE
COMP = REPL_CLIENT
COMP = LDAP_EXPLOITATION
COMP = SQL_PROCEDURES
COMP = DB2_DATA_SOURCE_SUPPORT
COMP = BASE_CLIENT
COMP = CONNECT_SUPPORT
DAS_CONTACT_LIST = LOCAL
DAS_USERNAME = dasusr1
DAS_GROUP_NAME = dasadm1
DAS_HOME_DIRECTORY = /home/dasusr1
DAS_PASSWORD = 547728531534502455097246316284412703433439576433541379526367333363795314025447185737070
ENCRYPTED = DAS_PASSWORD
INSTANCE = inst1
inst1.TYPE = ese
inst1.NAME = db2inst1
inst1.GROUP_NAME = db2iadm1
inst1.HOME_DIRECTORY = /home/db2inst1
inst1.PASSWORD = 547728531534502455097246316284412703433439576433541379526367333363795314025447185737070
ENCRYPTED = inst1.PASSWORD
inst1.AUTOSTART = YES
inst1.SVCENAME = db2c_db2inst1
inst1.PORT_NUMBER = 50000
inst1.FCM_PORT_NUMBER = 60000
inst1.MAX_LOGICAL_NODES = 4
inst1.CONFIGURE_TEXT_SEARCH = NO
inst1.FENCED_USERNAME = db2fenc1
inst1.FENCED_GROUP_NAME = db2fadm1
inst1.FENCED_HOME_DIRECTORY = /home/db2fenc1
inst1.FENCED_PASSWORD = 560741752337471467346923905234405983312332393347245601931143497330598141735228590035459
ENCRYPTED = inst1.FENCED_PASSWORD
LANG = EN
INSTALL_TSAMP = NO
Note that the generated response file has encrypted passwords. To overcome this, we change the file as follows: -
LIC_AGREEMENT = ACCEPT
PROD = ENTERPRISE_SERVER_EDITION
FILE = /opt/ibm/db2/V9.7
INSTALL_TYPE = CUSTOM
COMP = COMMUNICATION_SUPPORT_TCPIP
COMP = JDK
COMP = JAVA_SUPPORT
COMP = BASE_DB2_ENGINE
COMP = REPL_CLIENT
COMP = LDAP_EXPLOITATION
COMP = SQL_PROCEDURES
COMP = DB2_DATA_SOURCE_SUPPORT
COMP = BASE_CLIENT
COMP = CONNECT_SUPPORT
DAS_CONTACT_LIST = LOCAL
DAS_USERNAME = dasusr1
DAS_GROUP_NAME = dasadm1
DAS_HOME_DIRECTORY = /home/dasusr1
DAS_PASSWORD = passw0rd
INSTANCE = inst1
inst1.TYPE = ese
inst1.NAME = db2inst1
inst1.GROUP_NAME = db2iadm1
inst1.HOME_DIRECTORY = /home/db2inst1
inst1.PASSWORD = passw0rd
inst1.AUTOSTART = YES
inst1.SVCENAME = db2c_db2inst1
inst1.PORT_NUMBER = 50000
inst1.FCM_PORT_NUMBER = 60000
inst1.MAX_LOGICAL_NODES = 4
inst1.CONFIGURE_TEXT_SEARCH = NO
inst1.FENCED_USERNAME = db2fenc1
inst1.FENCED_GROUP_NAME = db2fadm1
inst1.FENCED_HOME_DIRECTORY = /home/db2fenc1
inst1.FENCED_PASSWORD = passw0rd
LANG = EN
INSTALL_TSAMP = NO
In other words, we explicitly set the passwords, and remove the lines: _
ENCRYPTED = inst1.PASSWORD
ENCRYPTED = DAS_PASSWORD
ENCRYPTED = inst1.FENCED_PASSWORD
(a) Unpack the product
$ cd /tmp
$ tar xvf /mnt/Products/DB297/db297linux64.tar
(b) Place the response file in a suitable location - I chose /root
(c) Install the product
$ cd /tmp/ese
$ ./db2setup -r /root/db2ese.rsp
(d) Wait a bit - my installation took ~22 minutes
DB2 Setup log file started at: Mon Jun 4 19:52:43 2012 BST
DB2 Setup log file finished at: Mon 04 Jun 2012 20:14:00 BST BST
(e) Check the log
$ cat /tmp/db2setup.log
...
Installing DB2 file sets :.......Success
Setting DB2 library path :.......Success
Executing control tasks :.......Success
Updating global registry :.......Success
The installation of IBM Tivoli Monitoring for Databases has completed. The log
file can be found at /opt/ibm/db2/V9.7/itma/logs/itm_install.log.
Starting DB2 Fault Monitor :.......Success
Updating the db2ls link :.......Success
Registering DB2 licenses :.......Success
Setting default global profile registry variables :.......Success
Creating the DB2 Administration Server :.......Success
Initializing instance list :.......Success
Command to be run: "cd /opt/ibm/db2/V9.7/;/opt/ibm/db2/V9.7/instance/db2icrt -a server -s ese -u db2fenc1 -p db2c_db2inst1 db2inst1".
The instance "db2inst1" has been created successfully.
The value "SVCENAME=db2c_db2inst1" was set in the DBM CFG file for the
"db2inst1" instance.
The value "DB2AUTOSTART=YES" was set in the Profile Registry for the "db2inst1"
instance.
Configuring DB2 instances :.......Success
Configuring the DB2 Administration Server :.......Success
Updating global profile registry :.......Success
...
(f) Check the product's version
$ /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".
I'll cover the 9.7.0.2 fix pack installation at a later date, once I've downloaded the 600 MB file from here :-)
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...
No comments:
Post a Comment