Encountered this issue updating our db2 user passwords.
The itmcmd config -A cq fails with this error.
Exceptions.ITMException KCIIN2205E Unable to create TEPS, return code = 3. Check the log file
/opt/IBM/TEPS/ITM/logs/db2prep.log for more information .: Exceptions.ITMException: Exceptions.ITMException KCIIN2205E
Unable to create TEPS, return code = 3. Check the log file /opt/IBM/TEPS/ITM/logs/db2prep.log for more information.
The db2prep log indicates a invalid password for the AdminPW user.
After troubleshooting determined that this was due to the = in the password
Issue is these lines in the kfwdb2prep.sh
KFW_DB2ADMIN_PW=$(grep adminPW $7|cut -f2 -d"=")
KFW_DB2USER_PW=$(grep DB2PW $7|cut -f2 -d"=")
As you can see the = delimiter for the cut command is causing it to drop everything after the first = in the password
$ cat pw
AdminPW=v, w"n*YvJ=hTniL2/yJQqJ@!pT&Xj~
$ KFW DB2ADMIN PW=$ (grep AdminPW pw| cut -f2 -d"=")
$ echo $KFW DB2ADMIN PW
V,w"n*YvJ
Any ITM Developers Reading this an extra - after the f2 looks like it would solve this issue
$ KFW_DB2ADMIN_PW=$ (grep AdminPW pw| cut -f2- -d"=")
$ echo $KFW_DB2ADMIN_PW
v,w"n*YvJ=hTniL2/yJQqJ@!pT&Xj~
There are a number of cases/technotes that come up when you search for these issues a couple of them mention special characters causing issues, but not what the characters are.
They also mention hardcoding the password in these lines in the script as a workaround,
It's not really ideal as unless you leave plaintext passwords in the scripts you have to redo it any time you want to run the itmcmd config -A cq. And probably after patching.
KCIIN0363E and KCIIN2205E during new configuration of TEPS
KCIIN0363E Failed to attach to the DB2 instance db2itm
Simplest workaround is just reset the password to something without a =.
(Or for IBM to fix the script)
------------------------------
BRAITHE MORRELL
------------------------------