Question & Answer
Question
T he configuration of the TEPS after installation of FixPack_7 breaks with the information KCIIN0363E Failed to attach to the DB2 instance db2itm. How can this problem be analysed ?
Answer
Error:
============================================
============================================
db2prep.log
-------------------------------------------
-------------------------------------------
The following command failed: /itmteps/bin/kfwdb2prep.sh db2itm db2itm
WW_TEPST teps US /itmteps/logs/db2prep.log /tmp/.itm228281327955966902.tmp
WW_TEPST teps US /itmteps/logs/db2prep.log /tmp/.itm228281327955966902.tmp
-------------------------------------------
itm_config.trc
-------------------------------------------
020-03-19 11:34:54.816+01:00 ITMinstall.CandleConfigAgent main __ERROR__ (traceKey:1584614094816)
Exceptions.ITMException: Exceptions.ITMException KCIIN2205E Unable to create WW_TEPST, return code = 3.
Check the log file /itmteps/logs/db2prep.log for more information.: Exceptions.ITMException:
Exceptions.ITMException KCIIN2205E Unable to create WW_TEPST, return code = 3.
Check the log file /itmteps/logs/db2prep.log for more information.
at ITMinstall.CandleConfigAgent.configAgent(CandleConfigAgent.java:407)
Exceptions.ITMException: Exceptions.ITMException KCIIN2205E Unable to create WW_TEPST, return code = 3.
Check the log file /itmteps/logs/db2prep.log for more information.: Exceptions.ITMException:
Exceptions.ITMException KCIIN2205E Unable to create WW_TEPST, return code = 3.
Check the log file /itmteps/logs/db2prep.log for more information.
at ITMinstall.CandleConfigAgent.configAgent(CandleConfigAgent.java:407)
-------------------------------------------
============================================
============================================
============================================
============================================
Questions:/Recommendations
============================================
can you please double check the
a:) IBM KCIIN2205E Unable to create TEPS, return code =3 - United States
https://www.ibm.com/support/pages/node/253221
https://www.ibm.com/support/pages/node/253221
b:) => Review the db2diag.log
c:) => run the installation with the root account
============================================
============================================
============================================
Diagnose:
============================================
============================================
can you please double check the
a:) IBM KCIIN2205E Unable to create TEPS, return code =3 - United States
https://www.ibm.com/support/pages/node/253221
https://www.ibm.com/support/pages/node/253221
b:) => Review the db2diag.log
c:) => run the installation with the root account
d:) =>
------------------------------------
------------------------------------
Modify the $CANDLEHOME/bin/kfwdb2prep.sh script
Change the line:
KFW_DB2ADMIN_PW=$(grep adminPW $7|cut -f2 -d"=")
to
KFW_DB2ADMIN_PW="<INSERT YOUR PASSWORD HERE>"
Save the kfwdb2prep.sh script and then launch the configuration tool again.
--------------------------------------
--------------------------------------
e:) KCIIN0363E and KCIIN2205E during new configuration of TEPS
Diagnosing The Problem
Diagnosing The Problem
https://www.ibm.com/support/pages/kciin0363e-and-kciin2205e-during-new-configuration-teps
--------------------------------------
--------------------------------------
Check /opt/IBM/ITM/logs/kfwdb2prep_db2inst1.log
or
/opt/IBM/ITM/logs/db2prep.log /tmp/.itmnnnnnnnnnnnn.tmp
or
/opt/IBM/ITM/logs/db2prep.log /tmp/.itmnnnnnnnnnnnn.tmp
KFWDB2PREP Starting on ...
Command issued:
db2 ATTACH TO db2inst1 USER db2inst1 USING [PASSWORD] 2>&1
Failed to attach to the db2 instance
Command issued:
db2 ATTACH TO db2inst1 USER db2inst1 USING [PASSWORD] 2>&1
Failed to attach to the db2 instance
Please check the followings:
Check the existence of the db2inst1 instance.
Check the instance is started and running.
Check the Admin User db2inst1 is defined.
Check the Admin User password is correct.
Check the existence of the db2inst1 instance.
Check the instance is started and running.
Check the Admin User db2inst1 is defined.
Check the Admin User password is correct.
Based on fact that invoking the command in standalone mode, the cause may be a permissions issue.
Try changing the permissions (chmod 777) of the $candlehome/logs/kfwdb2* files. Test and check results.
2. Troubleshooting by modifying the $CANDLEHOME/bin/kfwdb2prep.shscript
Within the script comment out the lines that remove the generated temp files.
Try changing the permissions (chmod 777) of the $candlehome/logs/kfwdb2* files. Test and check results.
2. Troubleshooting by modifying the $CANDLEHOME/bin/kfwdb2prep.shscript
Within the script comment out the lines that remove the generated temp files.
Comment out these lines:
rm -rf $tmpFile1
rm -rf $tmpFile2
rm -rf $tmpFile3
Save the kfwdb2prep.shscript and launch the TEPS configuration again. Step through the configuration as usual.
rm -rf $tmpFile1
rm -rf $tmpFile2
rm -rf $tmpFile3
Save the kfwdb2prep.shscript and launch the TEPS configuration again. Step through the configuration as usual.
If the configuration fails gather the following:
> PDCOLLECT gathered using the command 'tacmd pdcollect -o nohist'
> $CANDLEHOME/bin/kfwdb2prep.sh
> The configuration will also generate files in the /tmp directory. The files will appear as /tmp/<PID>-1.tmp
/tmp/<PID>-2.tmp
/tmp/<PID>-3.tmp
> $CANDLEHOME/bin/kfwdb2prep.sh
> The configuration will also generate files in the /tmp directory. The files will appear as /tmp/<PID>-1.tmp
/tmp/<PID>-2.tmp
/tmp/<PID>-3.tmp
Where <PID> is the PID associated with the configuration.
Obtain the file(s) from the /tmp directory.
Obtain the file(s) from the /tmp directory.
NOTE: The /tmp directory may not contain all 3 files, the existence of all 3 files depends on where the kfwdb2prep.sh script failed.
It's possible, the password used to attach to the DB2 instance contains special characters which cause a problem for the kfwdb2prep.sh.
3. In reported case(s), it does appear that the correct and same password entered in the command natively matches what's in the /tmp file:
ATTACH TO db2inst1 USER db2inst1 USING ‘db2inst1'
This is unexpected if it works via the command and not via the shell and if the permissions were granted as described earlier. Therefore, try the following:
Modify the shell script as follows:
Change (line 41 in reported case) from:
print "ATTACH TO ${KFW_DB2INST_ID} USER ${KFW_DB2ADMIN_ID} USING '${KFW_DB2ADMIN_PW}'" > $tmpFile1
to
print "ATTACH TO ${KFW_DB2INST_ID} USER ${KFW_DB2ADMIN_ID} USING 'db2inst1'" > $tmpFile
We are basically hardcoding the password within the attach command above, inside the shell script instead of pulling it from variable defined as
KFW_DB2ADMIN_PW=$(grep adminPW $7|cut -f2 -d"=")
KFW_DB2ADMIN_PW=$(grep adminPW $7|cut -f2 -d"=")
IF this gets passed the stage where the ATTACH is successful, then I expect the next logical step to CONNECT to it will fail (line 83 in the script). IF this is the case, we can then hardcode the value there too.
============================================
============================================
============================================
Example:
TEPS
============================================
User: teps Groups: itr3 ts4 db2asgrp db2iadm
Host name : tepshost Installer Lvl:06.30.07.00
CandleHome: /itmteps
AIX 7200-04-01
cq Tivoli Enterprise Portal Server
aix536 06.30.07.00
run as teps user
============================================
User: teps Groups: itr3 ts4 db2asgrp db2iadm
Host name : tepshost Installer Lvl:06.30.07.00
CandleHome: /itmteps
AIX 7200-04-01
cq Tivoli Enterprise Portal Server
aix536 06.30.07.00
run as teps user
============================================
----------------------
Problem description:
-----------------------
the configuration of the TEPS after installation of FixPack_7 breaks with the information
KCIIN0363E Failed to attach to the DB2 instance db2itm
The pdcollect will be sent to you asap.
KCIIN0363E Failed to attach to the DB2 instance db2itm
The pdcollect will be sent to you asap.
-------------------------------------------------------------------------------------------
Solution:
============================================
============================================
There have been 2 Problems with passwords :
1) One password contained special characters.
2) The script tried to login to DB2 with the TEPS user and expected a password change at the 1st login. So the configuration script run failed.
2) The script tried to login to DB2 with the TEPS user and expected a password change at the 1st login. So the configuration script run failed.
Solution :
1) created new password without special characters
2) avoid password change at 1st login by the commands ( as user root )
2) avoid password change at 1st login by the commands ( as user root )
passwd USER ; pwdadm -c USER
So the TEPS configuration script could run until the end.
============================================
============================================
============================================
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCTLMK","label":"ITM Tivoli Enterprise Portal V6"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
07 July 2020
UID
ibm16115948