7.1.8 Client Upgrade Issue 2 Nodes; OS uses SSL but now DB2 api backup fails??

Aldini

ADSM.ORG Member
Joined
Jul 5, 2016
Messages
23
Reaction score
1
Points
0
Hello all
I have a secure SSL backup for the OS client node but for the node on the same server that is a DB2 backup it fails now. I read where you have to be careful about ssl. Perhaps this the issue - it needs to be disabled for the DSB2 node somehow?????
Much thanks for help
 
The OS node had no issues but the DB2 seems to want to use key encryptionn - since IBM (as opposed to other vendors) chooses to makes this cumbersome and complex can i use "ssl no" in dsm.sys to stop this problem:

Here is a DB2 log:
07/18/2019 21:00:23 ANS1579E GSKit function GSKKM_ImportKeys failed with 101: GSKKM_ERR_KEYDB_NOT_EXIST
07/18/2019 21:00:24 ANS1579E GSKit function GSKKM_ImportKeys failed with 101: GSKKM_ERR_KEYDB_NOT_EXIST
07/18/2019 21:00:27 ANS1579E GSKit function GSKKM_ImportKeys failed with 17: GSKKM_ERR_DATABASE_INVALID_FILE_TYPE
07/18/2019 21:00:27 ANS9020E A session could not be established with a TSM server or client agent. The return code is

Much thanks
 
Issue is both DB2 and tSM have GSK files

find / -name gsk8capicmd_64
/usr/local/ibm/gsk8_64/bin/gsk8capicmd_64
/bin/gsk8capicmd_64
/opt/ibm/db2/V10.5/gskit/bin/gsk8capicmd_64
/opt/ibm/db2/V10.5_FP7/gskit/bin/gsk8capicmd_64
/opt/ibm/db2/V10.5_FP8/gskit/bin/gsk8capicmd_64
/opt/ibm/db2/V11.1.3fp3a/gskit/bin/gsk8capicmd_64
[root@qdbedwr15 bin64]#
 
Back
Top