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

 

HPDIA0119W Authentication mechanism is not available

HPDIA0119W Authentication mechanism is not available.

If you face this error during sso authentication
1 ) first check your registry server (LDAP..etc) that should be in running mode.
2 ) if issue does not resolve take once registry server restart.

HPDCO1056E Could not connect to the server Server1, on port 7135.

2015-12-06-20:18:49.533-08:00I----- 0x1354A420 pdadmin ERROR ivc socket mtsclient.cpp 2327 0x7f351688c720
HPDCO1056E   Could not connect to the server Server1, on port 7135.
Error: Could not connect to the server. (status 0x1354a426)

Fix: Steps:- 1 ) Check first Webseal logs, I found below error.
                          error coming due to ldap issue webseal unable to make connection with ldap So I took restart of ldap ,issue got fix.

HPDCO0205W   ------------------------------------------------
2015-12-06-20:17:21.766-08:00I----- 0x1354A420 webseald ERROR ivc socket mtsclient.cpp 2327 0x7eff040ba720
HPDCO1056E   Could not connect to the server Server1, on port 7135.
2015-12-06-20:17:21.802-08:00I----- 0x1354A420 webseald ERROR ivc socket mtsclient.cpp 2327 0x7eff040ba720
HPDCO1056E   Could not connect to the server Server1, on port 7135.

 hope this help..!!

Error: HPDIA0119W Authentication mechanism is not available. (status 0x13212077)

Fix :- This error comes due to ldap connection issue because Webseal is not able to reach the LDAP.
So do below steps.

1 ) First check the webseal logs , can easily find the exact error

/opt/IBM/tivoli/common/DPW/logs

read file msg__webseald-default.log

2 ) Check the LDAP service status in LDAP server, LDAP server should be in start status
ps -ef | grep ldapinstance  //instance as per environment

3 ) Check LDAP service is running on correct application user

4 ) Check LDAP service may run in config mode

5 ) Are you enabled SSL from LDAP end if yes check the ldap.conf and webseal conf file information from policy and webseal server end.

port killing command for centos

kill running port on Centos OS.

netstat -plten |grep java

Centos Virtual Machine GUI issue fix

GUI Mode issue Fix for CentOS vm.

if Centos VM machine is not coming up in GUI mode and throwing node link errors So in that situation use fsck command in command line mode for cleaning the corrupted link node after that reboot the VM machine. Surly VM will come up in GUI mode.

# fsck

CTGDIS810E handleException - cannot handle exception , initialize java.net.BindException: Address already in use: JVM_Bind

Assembly Line Error in Web Service Connector:-

09:34:17,721 ERROR - [processIdentityFeed] CTGDIS810E handleException - cannot handle exception , initialize

java.net.BindException: Address already in use: JVM_Bind

                at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:413)

                at java.net.ServerSocket.bind(ServerSocket.java:339)

                at java.net.ServerSocket.<init>(ServerSocket.java:205)

                at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:3)

                at com.ibm.di.server.ServerSocketFactoryEX.createServerSocket(ServerSocketFactoryEX.java:129)

                at com.ibm.di.server.ServerSocketFactoryEX.createServerSocket(ServerSocketFactoryEX.java:112)

                at com.ibm.di.server.ServerSocketFactoryEX.createServerSocket(ServerSocketFactoryEX.java:100)

                at com.ibm.di.connector.HTTPServerConnector.initialize(HTTPServerConnector.java:412)

                at com.ibm.di.connector.axis2.Axis2WSServerConnector.initializeServer(Axis2WSServerConnector.java:266)

                at com.ibm.di.connector.axis2.Axis2WSServerConnector.initialize(Axis2WSServerConnector.java:211)

                at com.ibm.di.server.AssemblyLineComponent.doInitialize(AssemblyLineComponent.java:1181)

                at com.ibm.di.server.AssemblyLineComponent.initialize(AssemblyLineComponent.java:1143)

                at com.ibm.di.server.AssemblyLine.executeWithALPool(AssemblyLine.java:4366)

                at com.ibm.di.server.AssemblyLine.run(AssemblyLine.java:1309)

09:34:17,731 ERROR - CTGDIS808E Problem encountered while running AssemblyLine Pool

09:34:17,731 INFO  - CTGDIS286I Waiting for AssemblyLine pool to terminate.

09:34:17,731 INFO  - CTGDIS080I Terminated successfully (2 errors).

Solution: - This error come due to multiple process running on same assembly line in TDI so kill the AL all process from Tdi after that run new one once again

Hope this will help.

CTGDIZ413E Entry Attribute 'xmlString' is missing

Web Service attribute Error:-

9:25:40,928 ERROR - [callws] CTGDIS810E handleException - cannot handle exception , functioncall

java.lang.Exception: CTGDIZ413E Entry Attribute 'xmlString' is missing.

                at com.ibm.di.fc.webservice.InvokeSoapWS.perform(InvokeSoapWS.java:343)

                at com.ibm.di.server.AssemblyLineComponent.executeOperation(AssemblyLineComponent.java:3336)

                at com.ibm.di.server.FunctionComponent.callreply(FunctionComponent.java:303)

                at com.ibm.di.server.AssemblyLine.msExecuteNextConnector(AssemblyLine.java:3750)

                at com.ibm.di.server.AssemblyLine.executeMainStep(AssemblyLine.java:3351)

                at com.ibm.di.server.AssemblyLine.executeMainLoop(AssemblyLine.java:2960)

                at com.ibm.di.server.AssemblyLine.executeMainLoop(AssemblyLine.java:2943)

                at com.ibm.di.server.AssemblyLine.executeAL(AssemblyLine.java:2912)

                at com.ibm.di.server.AssemblyLine.run(AssemblyLine.java:1311)

09:25:40,928 ERROR - CTGDIS266E Error in NextConnectorOperation. Exception occurred: java.lang.Exception: CTGDIZ413E Entry Attribute 'xmlString' is missing.

09:25:40,938 INFO  - CTGDIS100I Printing the Connector statistics.

09:25:40,938 INFO  -  [callws] Errors:1

09:25:40,938 INFO  - CTGDIS104I Total: Errors:2.

09:25:40,938 INFO  - CTGDIS101I Finished printing the Connector statistics.

09:25:40,938 ERROR - CTGDIS077I Failed with error: CTGDIZ413E Entry Attribute 'xmlString' is missing..

Solution:-  I did very simple mistake that I did not provide the value in 'xmlString' attribute in “invokeSoap web Service Function component”  so that’s why error coming so return some value in the 'xmlString' attribute after that it will surly call “Axis2 Web Service Server Connector”  

Hope this will help

LDAP data records iteration issue ( exceed limit error)

if getting this error during data records iterations from ldap by using TDI tool So can use this code in TDI for reseting connection then again TDI will continue the connection flow.
this error comes due to only configured exceed limit on LDAP. 

Use in Before initilaize hooks-

if (typeof(cnt) == "undefined") {
        // this is the first time so cnt is undefined. Init to 0.
        cnt = 0;
        // pageSize must be < the sizelimit
        pageSize = 100;
        // get the LDAP Connector interface
        cnctr = thisConnector.getConnector();
        // start by searching all
        cnctr.setParam("ldapSearchFilter","uid=*");
}

Use in After get next hooks -

// append "." to make it > than current value
uid = conn.getString("uid") + ".";
// increment cnt and test it
if (++cnt > pageSize) {
        // reset cnt
        cnt = 0;
        // debug display message (remove if you want)
        task.logmsg("...restart next time for uid >= " + uid);
        // with Startup = On Config Change, this forces re-init
        cnctr.setParam("ldapSearchFilter", "uid>="+uid);
}