SOA11g DBAdapter - Package Body has been invalidated

 Problem:

 SOA via dbadapter calls a parent API.
 This Parent API can inturn call child APIs.
 The child API was recompiled and is in a valid state at the database layer.
 
 The DB Adapter fails with the following message:

 ORA-04061: existing state of package body "APPS.XYZ" has been invalidated
 ORA-04065: not executed, altered or dropped package body "APPS.XYZ"
 ORA-06508: PL/SQL: could not find program unit being called: "APPS.XYZ"

 Solution:

 This is a caching issue.
 Either recompile the package again at the database side or bounce the SOA Managed server.

SOA11g Datasource has been suspended.

Problem:
 Pool xyz_db_ds is Suspended, cannot allocate resources to applications

Summary:
This happens when the database has no more free connections, the datasource connection pool keeps requesting them, and weblogic suspends it.

Solution:
To resolve this exception, ask your DBA to give you a report about you database load, or, if you have a sysdba account, just run these commands:

Run these commands

--see current sessions/processes:
select count(*) from v$process;
select count(*) from v$session;

--see database configuration:
select *  from v$parameter where name in ('sessions','processes','transactions');

Increase the connections or correctly dimension your datasource connection pool to match the free sessions

sql> alter system set processes=500 scope=spfile sid='*';
sql> alter system set sessions=555 scope=spfile sid='*';
sql> alter system set transactions=610 scope=spfile sid='*';
sql> shutdown immediate
sql> restart

Finally , on the weblogic server reset this  datasource.

References:
http://egherardini.wordpress.com/2011/04/27/oracle-soa-suite-11g-datasource-has-been-suspended/

DB Adapter: Interaction processing error

Exception:

Exception occured when binding was invoked.Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'DEMO_TEST' failed due to: Interaction processing error.Error while processing the execution of the APPS.ABC.DEMO API interaction.An error occurred while processing the interaction for invoking the APPS.ABC.DEMO API. Cause: java.lang.NullPointerException.Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD. This exception is considered not retriable, likely due to a modelling mistake.". The invoked JCA adapter raised a resource exception.Please examine the above error message carefully to determine a resolution.

Solution:

Undeploy the composite and Redeploy it again

ORACLE initialization or shutdown in progress

Exception:

java.sql.SQLException: ORA-01033: ORACLE initialization or shutdown in progress Error Code: 1033 [Caused by: ORA-01033: ORACLE initialization or shutdown in progress ] Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD.
Contact oracle support if error is not fixable.

Cause:

This is not a JCA adapter problem. Please verify the stability of target database.

No more data to read from socket

Exception:

The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.

,detail=No more data to read from socket ,code=17410}

Cause:

Occurs if application that uses DB connection from the DataSource which has been already been timed out.The application is not aware of this and still tries to use it to connect to the database.


Soultion:


Option1:
Reset the datasource

Option2:
Bounce Managed Servers

Option3:
Delete the datasource , bounce managed server and create the datasource again.

Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec



Exception:

Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: ". The invoked JCA adapter raised a resource exception.Please examine the above error message carefully to determine a resolution

Cause:

The issue was caused by known Unpublished Bug 11924578
Bug 11924578 - ADAPTERS USE OF HASHMAP CAN LEAD TO DEADLOCKS
Additional Information: Bug 11924578 exists in versions 11.1.1.3, 11.1.1.4 and 11.1.1.5


Solution:

To implement the solution:

For Non-Clustered environments, patches for the following three bugs have to be applied Bug 13360039 , Bug 12573835 and Bug 13394139
Note: Patch for Bug 11924578 is included in Patch for Bug 13360039
For Clustered environments, in addition to the above 3 patches, patch for bug 12797505 is also required

Failed to read wsdl file at: caused by:java.net.ConnectException: java.net.ConnectException: Connection refused


Solution:
Telnet to the external server to check whether the Connection to the server is established properly