Unable to add new data store in Information Analyzer using the DB2 or Oracle Connector

Problem(Abstract)

You are unable to add new data store in Information Analyzer using the DB2 or Oracle Connector

Cause

ASB Agent connections managed in WebSphere Application Server have been exhausted.

Diagnosing the problem

Add a new data store in Information Analyzer client. When defining a Data Connection, select DB2Connector or OracleConnector. The error message "Unable to connect successfully using the selected connector. Check to ensure the selected connector is installed in the engine tier system or select a different connector to establish the connection" is displayed.

Information Server Console log (isc.log) located in the directory "C:\Documents and Settings\<user>\Local Settings\Application Data\IBM\IBM Information Server console" on the client tier contains the following errors:

<Type>com/ascential/investigate/cas/exception/CASConnectionException</Type>
<Message><![CDATA[Failed to create a Connection]]></Message>
<StackTrace><![CDATA[com.ascential.investigate.cas.exception.CASConnectionException: Failed to create a Connection
at com.ascential.investigate.cas.ConnectorAccessorServiceImpl.getDataSources_retryable(ConnectorAccessorServiceImpl.java:1555)
at com.ascential.investigate.cas.ConnectorAccessorServiceImpl.access$100(ConnectorAccessorServiceImpl.java:84)
at com.ascential.investigate.cas.ConnectorAccessorServiceImpl$2.retryableOperation(ConnectorAccessorServiceImpl.java:368)
at com.ascential.investigate.utils.locking.RetryableOperation.doRetryableOperation(RetryableOperation.java:249)
at com.ascential.investigate.utils.locking.RetryableOperation.doRetryableOperation(RetryableOperation.java:212)
at com.ascential.investigate.utils.locking.RetryableOperation.doRetryableOperation(RetryableOperation.java:152)
at com.ascential.investigate.cas.ConnectorAccessorServiceImpl.getDataSources(ConnectorAccessorServiceImpl.java:372)
at com.ascential.investigate.cas.ConnectorAccessorServiceImpl.getDataSources(ConnectorAccessorServiceImpl.java:348)
Caused by: com.ascential.asb.cas.shared.exceptions.CommunicationException: Failed to send the request to the handler: Connection not available, Timed out waiting for 180001
at com.ascential.asb.cas.service.impl.ConnectorAccessServiceBean.sendToHandler(ConnectorAccessServiceBean.java:3597)
at com.ascential.asb.cas.service.impl.ConnectorAccessServiceBean.sendConnectorAccessRequest(ConnectorAccessServiceBean.java:3445)
at com.ascential.asb.cas.shared.ConnectorAccessServiceBeanSupport.sendToHandler(ConnectorAccessServiceBeanSupport.java:3439)


Additionally, the WebSphere SystemOut.log located in the default directory "/opt/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1" on the Services tier contains the following error:

[12/5/13 9:28:12:142 EST] 00000057 FreePool      E   J2CA0045E: Connection not available while invoking method createOrWaitForConnection for resource ASBAgentConnectionFactory.


Resolving the problem

The ASB Agent connections managed in WebSphere Application Server have been exhausted. WebSphere Application Server must be restarted to clear this condition.

​Source: http://www-01.ibm.com/support/docview.wss?uid=swg21659651

Popular posts from this blog

Shrink you container size up to 95%.

alma linux: dnf Module yaml error: Unexpected key in data