Monday, October 13, 2014

Migration IBM initiate V9 to IBM MDM v11 - Application and Algo

Steps:
1.Import from v9 HUB to MDM v11 workspace(RAD v8.5).
2.Using RAD upgrade the Project(under Master Data Management menu bar option available) the all application.
3.Most of error related to Algo.( all filed name are madatary for v11  i.e error in v9 , put the proper name it will working fine )
4.clean & Build
5.Start WAS server in u r workspace.
6.Deploy the project including weight & all other configuration.It will take some time to complete.

IF error come like Unable to JMX connection.
Check the IVT pass/fail ? If Pass then  the stop WAS server and change Envernoment JRE.( Double click on WAS server in RAD and one page will be open , u can find the JRE )
Check DB Schema as per below.
IF u r using Oracle DB then proper DB Schema below
/**************************************************/

ALTER SYSTEM SET db_4k_cache_size=128M;
ALTER SYSTEM SET db_16k_cache_size=128M;

CREATE TABLESPACE "DATSPACE"
    DATAFILE 'D:\oraclexe\app\oracle\oradata\XE\DATSPACE.dbf'
    SIZE 512M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;

CREATE TABLESPACE "EMESPACE1"
    DATAFILE 'D:\oraclexe\app\oracle\oradata\XEEMESPACE1.dbf'
    SIZE 512M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;
   
CREATE TABLESPACE "IDXSPACE"
    DATAFILE 'D:\oraclexe\app\oracle\oradata\XEIDXSPACE.dbf'
    SIZE 512M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;
   
CREATE TABLESPACE "EMESPACE2"
    DATAFILE 'D:\oraclexe\app\oracle\oradata\XEEMESPACE2.dbf'
    SIZE 512M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;

CREATE TABLESPACE "LOBSPACE"
    DATAFILE 'D:\oraclexe\app\oracle\oradata\XELOBSPACE.dbf'
    SIZE 1024M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;

CREATE TABLESPACE "TBS4K" NOLOGGING
      DATAFILE 'D:\oraclexe\app\oracle\oradata\XETBS4K.dbf'
      SIZE 512M blocksize 4k EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
     
CREATE TABLESPACE "TBS8K"
    DATAFILE 'D:\oraclexe\app\oracle\oradata\XETBS8K.dbf'
    SIZE 512M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;    



CREATE TABLESPACE "TBS16K" NOLOGGING
      DATAFILE 'D:\oraclexe\app\oracle\oradata\XETBS16K.dbf'
      SIZE 512M blocksize 16k EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

CREATE USER MDMUSER IDENTIFIED BY mdmuser DEFAULT TABLESPACE DATSPACE TEMPORARY TABLESPACE TEMP;
GRANT CREATE SESSION TO MDMUSER;

GRANT UNLIMITED TABLESPACE TO MDMUSER;
GRANT CREATE SEQUENCE TO MDMUSER;
GRANT CREATE ANY SYNONYM TO MDMUSER;
ALTER USER MDMUSER QUOTA UNLIMITED ON DATSPACE;
ALTER USER MDMUSER QUOTA UNLIMITED ON IDXSPACE;
ALTER USER MDMUSER QUOTA UNLIMITED ON EMESPACE1;
ALTER USER MDMUSER QUOTA UNLIMITED ON EMESPACE2;
ALTER USER MDMUSER QUOTA UNLIMITED ON LOBSPACE;
ALTER USER MDMUSER QUOTA UNLIMITED ON TBS4K;
ALTER USER MDMUSER QUOTA UNLIMITED ON TBS8K;
ALTER USER MDMUSER QUOTA UNLIMITED ON TBS16K;
ALTER SYSTEM SET open_cursors = 1500 SCOPE=BOTH;
ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR SCOPE=BOTH;
GRANT CREATE TABLE TO MDMUSER;
GRANT CREATE TRIGGER TO MDMUSER;
GRANT CREATE PROCEDURE TO MDMUSER;
GRANT CREATE SEQUENCE TO MDMUSER;
GRANT CREATE TYPE TO MDMUSER;
GRANT CREATE VIEW TO MDMUSER;
GRANT SELECT ANY TABLE TO MDMUSER;
GRANT IMP_FULL_DATABASE TO MDMUSER;
GRANT SELECT ANY DICTIONARY TO MDMUSER;
GRANT RESOURCE TO MDMUSER;
GRANT CONNECT TO MDMUSER;
GRANT CREATE SNAPSHOT TO MDMUSER;
/
exit

/*************************************************************/

IBM MDM - attributes as part of data extensions not coming in response xml

IBM MDM - attributes as part of data extensions not coming in response xml


Resolution:- Check if  optimized.sql is set to false in tcrm_extension.properties

Thursday, October 9, 2014

Generated files must be customized before code generation can be completed. Please see the high priority tasks in the Tasks view.

While doing Inline data extension on IBM MDM you may face this issue. 

Generated files must be customized before code generation can be completed.  Please see the high priority tasks in the Tasks view.


Incorrect parameter data for method getProduct within class com.training.extension.entityObject.XproductExtInquiryData. The SQL associated with the method requires 1 parameters, but 0 were supplied in the EntityMapping annotation.


For Resolution refer:

Friday, September 19, 2014

ibm mdm null response

MDM transactions showing success on Batch Processor (runbatch.sh) but not inserting or updating actually anything in Database and Customer.logs showing nothing except 

2014-09-19 07:52:01,951 [ORB.thread.pool : 8] INFO  com.dwl.tcrm.coreParty.xmlHandler.XMLRequestParser - [Info_XMLRequestParser_TotalTime:] XMLRequestParser : parseRequest : total time in milliseconds 1
2014-09-19 07:52:01,953 [ORB.thread.pool : 8] INFO  com.dwl.base.xml.AbstractXMLResponseConstructor - [Info_AbstractXMLResponseConstructor_XMLResponseConstructorTotalTime:] XMLResponseConstructor : constructTransactionResponse : total time in milliseconds  0
2014-09-19 07:52:01,953 [ORB.thread.pool : 8] INFO  com.dwl.base.requestHandler.DWLRequestHandler - [Info_DWLRequestHandler_TotalTime:] RequestHandler : processTx  : total time in milliseconds 3
2014-09-19 07:52:01,953 [ORB.thread.pool : 8] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,953 [ORB.thread.pool : 8] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - [Info_DWLServiceControllerBase_ProcessRequestTotalTime:] DWLServiceController : processRequest : total time in milliseconds 3
2014-09-19 07:52:01,953 [ORB.thread.pool : 8] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,957 [ORB.thread.pool : 4] INFO  com.dwl.base.requestHandler.RequestParserManager - [Info_RequestParserManager_TotalTime:] RequestParserManager : getRequestParser : total time in milliseconds 0
2014-09-19 07:52:01,957 [ORB.thread.pool : 4] INFO  com.dwl.tcrm.coreParty.xmlHandler.XMLRequestParser - [Info_XMLRequestParser_TotalTime:] XMLRequestParser : parseRequest : total time in milliseconds 0
2014-09-19 07:52:01,958 [ORB.thread.pool : 9] INFO  com.dwl.base.requestHandler.RequestParserManager - [Info_RequestParserManager_TotalTime:] RequestParserManager : getRequestParser : total time in milliseconds 0
2014-09-19 07:52:01,959 [ORB.thread.pool : 9] INFO  com.dwl.tcrm.coreParty.xmlHandler.XMLRequestParser - [Info_XMLRequestParser_TotalTime:] XMLRequestParser : parseRequest : total time in milliseconds 1
2014-09-19 07:52:01,962 [ORB.thread.pool : 0] INFO  com.dwl.base.requestHandler.RequestParserManager - [Info_RequestParserManager_TotalTime:] RequestParserManager : getRequestParser : total time in milliseconds 0
2014-09-19 07:52:01,962 [ORB.thread.pool : 0] INFO  com.dwl.tcrm.coreParty.xmlHandler.XMLRequestParser - [Info_XMLRequestParser_TotalTime:] XMLRequestParser : parseRequest : total time in milliseconds 0
2014-09-19 07:52:01,963 [ORB.thread.pool : 4] INFO  com.dwl.base.xml.AbstractXMLResponseConstructor - [Info_AbstractXMLResponseConstructor_XMLResponseConstructorTotalTime:] XMLResponseConstructor : constructTransactionResponse : total time in milliseconds  1
2014-09-19 07:52:01,963 [ORB.thread.pool : 4] INFO  com.dwl.base.requestHandler.DWLRequestHandler - [Info_DWLRequestHandler_TotalTime:] RequestHandler : processTx  : total time in milliseconds 6
2014-09-19 07:52:01,963 [ORB.thread.pool : 4] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,963 [ORB.thread.pool : 4] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - [Info_DWLServiceControllerBase_ProcessRequestTotalTime:] DWLServiceController : processRequest : total time in milliseconds 6
2014-09-19 07:52:01,963 [ORB.thread.pool : 4] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,964 [ORB.thread.pool : 9] INFO  com.dwl.base.xml.AbstractXMLResponseConstructor - [Info_AbstractXMLResponseConstructor_XMLResponseConstructorTotalTime:] XMLResponseConstructor : constructTransactionResponse : total time in milliseconds  0
2014-09-19 07:52:01,964 [ORB.thread.pool : 9] INFO  com.dwl.base.requestHandler.DWLRequestHandler - [Info_DWLRequestHandler_TotalTime:] RequestHandler : processTx  : total time in milliseconds 6
2014-09-19 07:52:01,964 [ORB.thread.pool : 9] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,964 [ORB.thread.pool : 9] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - [Info_DWLServiceControllerBase_ProcessRequestTotalTime:] DWLServiceController : processRequest : total time in milliseconds 6
2014-09-19 07:52:01,964 [ORB.thread.pool : 9] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,966 [ORB.thread.pool : 0] INFO  com.dwl.base.xml.AbstractXMLResponseConstructor - [Info_AbstractXMLResponseConstructor_XMLResponseConstructorTotalTime:] XMLResponseConstructor : constructTransactionResponse : total time in milliseconds  1
2014-09-19 07:52:01,966 [ORB.thread.pool : 0] INFO  com.dwl.base.requestHandler.DWLRequestHandler - [Info_DWLRequestHandler_TotalTime:] RequestHandler : processTx  : total time in milliseconds 4
2014-09-19 07:52:01,966 [ORB.thread.pool : 0] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################
2014-09-19 07:52:01,966 [ORB.thread.pool : 0] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - [Info_DWLServiceControllerBase_ProcessRequestTotalTime:] DWLServiceController : processRequest : total time in milliseconds 5
2014-09-19 07:52:01,966 [ORB.thread.pool : 0] INFO  com.dwl.base.requestHandler.beans.DWLServiceController - ###########################


Possible Cause: check if transaction xml has proper <requesterName>SYSTEM</requesterName> and it has proper access in USERACCESS or GROUPACCESS and related tables.

Thursday, September 18, 2014

com.ibm.wsspi.webcontainer.util.RequestUtils parseQueryString SRVE0325E: Exceeding maximum parameters allowed per request

Error:
[9/18/14 7:54:44:270 SAST] 00000033 util          E com.ibm.wsspi.webcontainer.util.RequestUtils parseQueryString SRVE0325E: Exceeding maximum parameters allowed per request 100 ,current 100 , cannot add more.
[9/18/14 7:54:44:274 SAST] 00000033 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet Faces Servlet in application CustomerDataStewardshipEar-TZB2. Exception created : java.lang.IllegalArgumentException
        at com.ibm.wsspi.webcontainer.util.RequestUtils.parseQueryString(RequestUtils.java:224)

Solution:
-----------
In the administrative console click Servers > Application Servers > server_name > Web Container settings > Web Container
Under Additional Properties select Custom Properties.

add a new property
name: com.ibm.ws.webcontainer.maxParamPerRequest
Value : some number

The default value for this is 10000. you can set it a different number or you can set this property to -1 if you do not want to limit the number of parameters that can be included in a request

Please check the ref link for complete information:

Wednesday, September 17, 2014

[Exception_BatchController_ExceptionCount:] CDKBC2006E:Exception occurred: count = 2; processorID = ParseAndExecuteConsumer; messageID = 0;

While running batch file getting this error.


ERROR     - [Exception_BatchController_ExceptionCount:] CDKBC2006E:Exception occ                                                                                        urred: count = 1; processorID = ParseAndExecuteConsumer; messageID = 1; addition                                                                                        al error message = null
DEBUG     - starting Processor.checkQueue: , inQueue size = 1, idleQueue size =                                                                                         8
DEBUG     - WriterConsumer >>> 1
Faulty record: 1
ERROR     - [Exception_BatchController_ExceptionCount:] CDKBC2006E:Exception occ                                                                                        urred: count = 2; processorID = ParseAndExecuteConsumer; messageID = 0; addition                                                                                        al error message = null
DEBUG     - starting Processor.checkQueue: , inQueue size = 1, idleQueue size =                                                                                         8
DEBUG     - WriterConsumer >>> 0
Faulty record: 2
--
Probable Cause:
Could be database connectivity issue. Check Customer.logs & SystemOut.logs
In my case it was also com.ibm.ws.Transaction.XAResourceNotAvailableException:
So resolved by :
clear the trans logs of Websphere Application Server and restart the same.

Reference used:
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wsadapters602.jca_ff.doc/shared/csha_tro_tranlog.html

----
Customer.logs
2014-09-17 14:34:35,417 [ORB.thread.pool : 3] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,417 [ORB.thread.pool : 3] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,417 [ORB.thread.pool : 3] WARN  com.dwl.base.util.DWLClassFactory - [Error_Common_NoClass:] CDKCS0008E:The following class cannot be created. Class = DWLErrorMessageComponent
2014-09-17 14:34:35,419 [ORB.thread.pool : 3] ERROR com.dwl.management.config.repository.database.RepositoryImpl - Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,419 [ORB.thread.pool : 3] INFO  com.dwl.management.config.cache.CacheFactory - Couldn't get the cache from CacheManager :ApplicationCache
com.ibm.mdm.cache.common.CacheLoaderException: CacheLoader Exception in getCache: java.lang.RuntimeException: com.dwl.management.config.repository.RepositoryStoreException: [Exception_RepositoryImpl_CreateConnectionFailed:] CDKCR2019E:A failure occurred while trying to create a connection to the configuration repository database.
2014-09-17 14:34:35,421 [ORB.thread.pool : 1] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,421 [ORB.thread.pool : 1] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,421 [ORB.thread.pool : 1] WARN  com.dwl.base.util.DWLClassFactory - [Error_Common_NoClass:] CDKCS0008E:The following class cannot be created. Class = DWLErrorMessageComponent
2014-09-17 14:34:35,424 [ORB.thread.pool : 0] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,425 [ORB.thread.pool : 0] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,425 [ORB.thread.pool : 0] WARN  com.dwl.base.util.DWLClassFactory - [Error_Common_NoClass:] CDKCS0008E:The following class cannot be created. Class = DWLErrorMessageComponent
2014-09-17 14:34:35,425 [ORB.thread.pool : 3] ERROR com.dwl.management.config.repository.database.RepositoryImpl - Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,425 [ORB.thread.pool : 3] INFO  com.dwl.management.config.cache.CacheFactory - Couldn't get the cache from CacheManager :ApplicationCache
com.ibm.mdm.cache.common.CacheLoaderException: CacheLoader Exception in getCache: java.lang.RuntimeException: com.dwl.management.config.repository.RepositoryStoreException: [Exception_RepositoryImpl_CreateConnectionFailed:] CDKCR2019E:A failure occurred while trying to create a connection to the configuration repository database.
2014-09-17 14:34:35,427 [ORB.thread.pool : 3] ERROR com.dwl.management.config.repository.database.RepositoryImpl - Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myclient)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
2014-09-17 14:34:35,429 [ORB.thread.pool : 3] ERROR com.dwl.base.db.DataManager - [pdq][10003][2.1.7500] pureQuery could not connect to the database.;  Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:

SystemOut.log
recoveryClasspath = /opt/IBM/WAS/wasadmin1/app/WebSphere/AppServer/lib/rsadapter.rar:/opt/IBM/WAS/wasadmin1/app/WebSphere/AppServer/lib/rsadapter.rar:/opt/IBM/WAS/wasadmin1/app/oracle/product/11.2.0/db11g/jdbc/lib/ojdbc14.jar
raKey = cells/oat/clusters/mdmb01/resources.xml#builtin_rra
. The exception stack trace follows: com.ibm.ws.Transaction.XAResourceNotAvailableException: com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException: DSRA8100E: Unable to get a XAConnection from the DataSource.
at com.ibm.ejs.j2c.J2CXAResourceFactory.getXAResource(J2CXAResourceFactory.java:413)
at com.ibm.ws.Transaction.JTA.XARecoveryData.getXARminst(XARecoveryData.java:446)
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:573)
at com.ibm.tx.jta.PartnerLogTable.recover(PartnerLogTable.java:389)
at com.ibm.tx.jta.RecoveryManager.resync(RecoveryManager.java:1530)
at com.ibm.tx.jta.RecoveryManager.performResync(RecoveryManager.java:2265)
at com.ibm.ws.tx.jta.RecoveryManager.performResync(RecoveryManager.java:114)
at com.ibm.tx.jta.RecoveryManager.run(RecoveryManager.java:2218)
at java.lang.Thread.run(Thread.java:738)
Caused by: com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException: DSRA8100E: Unable to get a XAConnection from the DataSource.
at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:444)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.getPooledConnection(InternalGenericDataStoreHelper.java:1324)
at com.ibm.ws.rsadapter.spi.WSRdbDataSource.getPooledConnection(WSRdbDataSource.java:2471)
at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.createManagedConnection(WSManagedConnectionFactoryImpl.java:1639)
at com.ibm.ejs.j2c.J2CXAResourceFactory$1.run(J2CXAResourceFactory.java:380)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ejs.j2c.J2CXAResourceFactory.getXAResource(J2CXAResourceFactory.java:190)
... 8 more
Caused by: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=191t.wload.myClients.co.uk)(PORT=7777))(CONNECT_DATA = (SERVICE_NAME = CDI.wload.myClients.co.uk)(METHOD=BASIC)(RETRIES=180)(DELAY=10)))
DSRA0010E: SQL State = null, Error Code = 0
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:261)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:441)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:297)
at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:472)
at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:159)
at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:133)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper$1.run(InternalGenericDataStoreHelper.java:1275)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.getPooledConnection(InternalGenericDataStoreHelper.java:1312)
... 13 more


Monday, September 15, 2014

reload All Code TYpes sample xml

reload All Code TYpes sample xml


<?xml version="1.0" encoding="UTF-8" ?>
                xsi:noNamespaceSchemaLocation="myTCRM.xsd">
                <RequestControl>
                                <requestID>2</requestID>
                                <DWLControl>
                                                <requesterName>SYSTEM</requesterName>
                                                <requesterLanguage>100</requesterLanguage>
                                </DWLControl>
                </RequestControl>
                <TCRMInquiry>
                                         <InquiryType>reloadAllCodeTypes</InquiryType>
                                         <InquiryParam>
                                         <tcrmParam name='CodeTableName'>cdregiontp</tcrmParam>
                                         </InquiryParam>
                </TCRMInquiry>

</TCRMService>