gsk7cmd utility Certificates db management errors

Error: 215
Please refer to the GSKCapiCmd User's Guide
for the meaning of the error.

Fix :- This error comes if given password is not strong for the db because we used "-strong" parameter in the command
example:-

gsk7capicmd -keydb -create -db test100.db -pw 02K+>]]X+ -type cms -expire 111 -stash -fips –strong


Error: 9
Please refer to the GSKCapiCmd User's Guide
for the meaning of the error.

Fix :- This come if Databse already exist with the same name

Error: 16Please refer to the GSKCapiCmd User's Guide
for the meaning of the error.

Fix :- This error comes due to invalid database password was encountered.

Error: 101
Please refer to the GSKCapiCmd User's Guide
for the meaning of the error.

Fix : - database does not exist , check test.db is created or not

CTGIMK001E The IBM container cannot be found

<Trace Level="MIN">
 <Time Millis="1450689571546"> 2015.12.21 01:19:31.546-08:00</Time>
 <Server Format="IP">localhost</Server>
 <ProductId>CTGIM</ProductId>
 <Component>com.ibm.itim.apps.ejb.migration</Component>
 <ProductInstance>server1</ProductInstance>
 <LogText><![CDATA[CTGIMK001E  The ABCD container cannot be found.]]></LogText>
 <Source FileName="com.ibm.itim.apps.ejb.migration.DifferencePlan" Method="execute"/>
 <Thread>SIBJMSRAThreadPool : 0</Thread>
 <Exception><![CDATA[com.ibm.itim.sdo.SDOException: CTGIMK001E  The dtag container cannot be found.
    at com.ibm.itim.sdo.store.DifferenceOperation.validateContainers(DifferenceOperation.java:148)
    at com.ibm.itim.sdo.store.DifferenceOperation.getDifferences(DifferenceOperation.java:91)
    at com.ibm.itim.apps.ejb.migration.DifferencePlan.execute(DifferencePlan.java:106)
    at com.ibm.itim.apps.ejb.migration.MigrationManagerBean.onMessage(MigrationManagerBean.java:238)
    at com.ibm.itim.apps.ejb.migration.EJSRemoteStatefulwf_ejb_enroleejb_MigrationManage_437e53dd.onMessage(Unknown Source)
    at

I faced this error during  jar import in ISIM and fix found that organization name was different-different  in jar & ISIM

Steps : - 1 ) Check ISIM trace.log
              2 ) Check the Organization name that should be the same in jar & ISIM

HPDAA0257E

HPDAA0257E   Could not contact the Security Access Manager policy server.  Possible causes are:

This error occurs during java run time configuration from ISIM to ISAM so do the mentioned steps for fix.

Fix: - 1 ) Firstly check /etc/hosts entry in the environment , host entry should be updated correctly ISIM &    ISAM
         2 )  Check ISAM  hostname & port number during java run time configuration from ISIM to ISAM that should be correct

TDI V7.1 Fix pack installation

1 ) Download latest TDI fixpack
2 ) copy UpdateInstaller.jar from the fixpack package to TDI_install_dir/maintenance directory
3 ) execute command for window
    TDI_install_dir\bin\applyUpdates.bat -update TDI-7.1-FP0008.zip
    execute command for linux
   TDI_install_dir/bin/applyUpdates.sh -update TDI-7.1-FP008.zip

4 ) verify fix pack installation

Windows OS : TDI_install_dir\bin\applyUpdates.bat -queryreg
Unix OS: TDI_install_dir/bin/applyUpdates.sh -queryreg

SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.

Fix : 1 ) First of all check the db2 product logs from below path , Can easily find the exact error.

/home/db2admin/sqllib/log

2 ) Check hostname if there is different hostname, Set the correct hostname

3 ) Again restart the Db2 product
    #Db2start

SQL1025N The database manager was not stopped because databases are still active

Use command :
1 . db2 list application show detail
2.  db2 force application all
3.  db2stop
4. db2start

could not start webseal Server

# pdweb restart
could not start webseal Server

Fix Steps : - 1 ) first of all check webseal logs

2 ) After that check webseald-default.conf file owership. file should be own by the ivmgr user.
 File will present on path (/opt/pdweb/etc)

I found file ownership was different in my case so change ownership to ivmgr user


 2 ) chown ivmgr:ivmgr webseald-default.conf



3 ) again restart the webseal

pdweb restart