Monday, December 17, 2012

External Table Names column getting hang up while creating data objects in BAM


Problem : 

Creating data source using using Oracle EBS Database as external tables then BAM Web Application is getting hanged up!!
Steps to replicate :


1. We are using Oracle EBS R12 database as external datasource in BAM. This is done perfectly using BAM Architect -- External Datasources





2. Now While creating Data Objects and selecting above created external(refering to EBS database) data source then external table names.. are not coming up and its keep on processing and getting hanged up !!




Error : 

BEA-000337
I tried increasing the socket time from 600 to 26000 in weblogic and BAM server. But had no luck !!

Solution : 

As suggested by Oracle Support 

 
****

I have tried replicating the issue but in my case for the first time it took several minutes when I selected external data object and selected datasource from the drop down list. I believe this is not a BUG but dependent on performance.

*****

Problem occurred as result of performance and hardware issue .

I was  connecting eBS and SOA Suite ( which are located in different location/environment) and were not in same DMZ and I was connected to Oracle EBS instance over VPN connection too !!


Friday, December 14, 2012

Timed out when making request to XAResource

Error Log Trace :

[2012-09-11T19:58:01.053+05:30] [AdminServer] [ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1d4729d] [userId: <anonymous>] [ecid: 0000Jap5w7iCSs05Rz^Ayd1GJm2d000002,0] [APP: soa-infra] weblogic.transaction.RollbackException: Transaction has timed out when making request to XAResource 'EBSDS_base_domain'.[[
javax.resource.ResourceException: weblogic.transaction.RollbackException: Transaction has timed out when making request to XAResource 'EBSDS_base_domain'.atoracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.afterDelivery(MessageEndpointImpl.java:308) atoracle.tip.adapter.aq.v2.database.AbstractDequeueAgent$AQDeliveryBean.afterOnMessage(AbstractDequeueAgent.java:607)at oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent$AQDeliveryBean.access$100(AbstractDequeueAgent.java:473)
at oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.run(AbstractDequeueAgent.java:157)

Reason :

oracle.soa.adapter : indicates the error had resulted from JCA Adapter .

 XAResource 'EBSDS_base_domain :   EBSDS is datasource being used to make  database connection to EBS Suite( in my case ) for  base_domain.

JDBC datasource was not able connect to database with which it was configured at design time.

Solution : 

Try to check if the database in being up or down with help of Toad or Oracle SQL Developer.
Or Try to make new JDBC DataSource in Weblogic console using the same same database name, hostname, port, password  and try to test the connection.

ConnectionDeadSQLException & common.ResourceException


Error Log Trace:
internal Exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException:0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection.

Reason: 
The DB Service went down abrublty as This exception is generated when an application request to get a connection fails because the connection selected to be returned to the application from the pool fails the configured tests.
Weblogic tests a connection before it is given to a client.

Solution : 

Oracle DB Service need to be restarted !!