JCA Binding execute of Reference operation 'insert' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: javax.resource.spi.IllegalStateException: [Connector:199176]Unable to execute allocateConnection(...) on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to re-lookup Connection Factory eis/DB/Sample from JNDI and get a new Connection Handle.”

HI Folks ,

I have experienced this issue in my clients environment.

Reason

There is a disconnection between WLS and JCA connection pool manager.
When we update JCA adapter deployment with new JNDI and redeploy the adapter instance then WLS invalidates all the existing connections and it seems WLS even doesn't know that JCA connection pool is the owner of these connections and it doesn't inform JCA pool manager that it has invalidated the connections.
Now JCA pool manager has no idea of what happened and it still maintains invalid connections in its pool.

When client requests JCA connection then JCA manager try to return the dead connection which results above error.


 Solution 1

1.Try applying patch 11812911 


 Solution 2

2.This solution is about just updating weblogic-ra.xml without redeploying it

•   Update adapter JNDI from the weblogic administration console deployments
•   Save the changes
•   Go to the Deployments page
•   Check the required Adapter
•   Click on the Update button
•   Choose "Update this application in place with new deployment plan changes. (We need to specify a deployment plan for this option) Do not choose the default option: "Redeploy this application using the following deployment files"

•   Click finish 

Happy Learning...!!!!!!!!   Fun Sharing........!!!!!!!!!!!!!

JCA Binding execute of Reference operation 'Calling_DB_run_settlement'(Stored Procedure) failed due to: Stored procedure invocation error(ORA-20100: File l32.tmp creation for FND_FILE failed)

Hi Folks ,

I have faced this scenario in 11.1.1.4 Env.

Error:-

Binding fault has occured in the Stored Prosedure Component please check with the Admin;.............................
FaultName: bindingFault
Fault Info: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage} parts: {{ summary=Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Calling_DB_xxwfs_run_wex_settlement' failed due to: Stored procedure invocation error. Error while trying to prepare and execute the STORED_PROCEDURE. An error occurred while preparing and executing the .STORED_PROCEDURE Cause: java.sql.SQLException: ORA-20100: File l32.tmp creation for FND_FILE failed. You will find more information on the cause of the error in request log. ORA-06512: at "APPS.FND_FILE", line 667 ORA-06512: at "STORED_PROCEDURE", line 375 ORA-06512: at line 1 Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-20100" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ,detail=ORA-20100: File l3247078.tmp creation for FND_FILE failed. You will find more information on the cause of the error in request log. ORA-06512: at "APPS.FND_FILE", line 667 ORA-06512: at "STORED_PROCEDURE", line 375 ORA-06512: at line 1 ,code=20100}

Solution:-  Doc ID 392635.1

Metalink description below

Error ORA-20100 .tmp Creation For FND_FILE Failed In FA Concurrent Requests (Doc ID 392635.1)

APPLIES TO:

Oracle Assets - Version 11.5.10.2 and later
Oracle Application Object Library - Version 11.5.1 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 14-Jan-2013***

SYMPTOMS

When attempting to run a concurrent request such as the 'Generate Asset Trace' program (FATRACE), the following error occurs in the log file:

ERROR
ORA-20100: File o0013319.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
Error: function fa_asset_trace_pkg.save_output returned failure

CAUSE

This error is caused by a concurrent manager setup and privilege related issue in the $APPLPTMP environment variable and UTL_FILE_DIR database parameter.

For example:
There could be one user for the Application Tier (applmgr in group applmgr) that is used by the Concurrent Manager, and one user for the database (oracle in group dba) that is used by the database.

The .tmp file is released by user oracle out by utl_file_dir, but the Concurrent Manager will try to access it with user applmgr.  As they are in different groups, this could be an issue on Linux/Unix environments.

Another environment problem could be that the utl_file_dir first directory is not $APPLPTMP.  Then the Concurrent Manager will check in a directory for a tmp and will not find it.

This error can also be seen in cases were there is more then one instance on the same server, and they share the same directory for $APPLPTMP or $UTL_FILE_DIR.  One instance can try to write to the same temporary file, which is locked by the other one.

SOLUTION

Please do the following:

1.  Change the UTL_FILE_DIR to have the same first value as the $APPLPTMP, ex: /usr/tmp
Change it in the initSID.ora and reboot the database after.

2.  Grant all users read/write permissions to that directory:
chmod 777 /usr/tmp

3.  If the error persists, check the following notes:

Oracle Applications System Administrator's Guide - Configuration
Note:157756.1: APPLPTMP , utl_file_dir and FND_FILE package
Note:303913.1: Upgrading From 11.5.9 To 11.5.10: Ora-20100 , Ora-06512 Fnd_file Creation failed
Note:123977.1: ORA-20100 & ORA-6512 When Running a Concurrent Process

4.  If still having the issue, please log an SR with Oracle Support, RDBMS team.

REFERENCES

NOTE:123977.1 - ORA-20100 & ORA-6512 When Running a Concurrent Process
NOTE:148262.1 - Concurrent Processing - Concurrent Requests Fail with FDPSTP failed due to ORA-20100: File o0002712.tmp creation for FND_FILE
NOTE:157756.1 - Concurrent Requests Complete with ORACLE Error 20100 in FDPSTP
NOTE:303913.1 - Upgrade to 11.5.10fails with ORA-20100, ORA-06512 'creation for FND_FILE failed'

Happy learning......!!!!!!!!!   Fun Sharing....!!!!!!!!!!!

How to "Turn Off EDN" & "Turn On EDN" if its not using in a SOA deployment

Hi  Folks ,

Now we gonna learn how to turn off/on EDN in SOA Environment.

1.Open the EM console.
2.Navigate to System MBean Browser-> MBeam Application-> Application Defined MBeans ->oracle.as.soainfra.config -> SOA Server-> EDN Config ->edn

and set the paused attribute to "True".
If true, EDN listener/poller threads are decreased to 0 which effectively stops delivering events.
Works for EDN-DB and EDN-JMS.
If you would like to do this through WLST the commands are listed below.
WLST command to enable/disable EDN event delivery.

sca_enableEventsDelivery()
sca_disableEventsDelivery()
(start WLST script, for example, $MW_HOMES/AS11gR1SOA/common/bin/wlst.sh)

1.connect ('<user>','<password>','t3://<soa server>:<port>')
2.custom().
3.cd('oracle.as.soninfra.config/oracle.as.soninfra.configname-edn,type=EDNConfig,Application=soa-infra')
4.set('Paused',1)
5.exit()

In Step 4, change it to set('Paused',0) would resume EDN event delivery.
This does not require a restart of the Managed Server to take effect.


Happy Learning.......!!!!   Fun Sharing......!!!!

List of all states from COMPOSITE_INSTANCE, CUBE_INSTANCE, DLV_MESSAGE tables

COMPOSITE_INSTANCE States

State	Description
0	Running
1	Completed
2	Running with faults
3	Completed with faults
4	Running with recovery required
5	Completed with recovery required
6	Running with faults and recovery required
7	Completed with faults and recovery required
8	Running with suspended
9	Completed with suspended
10	Running with faults and suspended
11	Completed with faults and suspended
12	Running with recovery required and suspended
13	Completed with recovery required and suspended
14	Running with faults, recovery required, and suspended
15	Completed with faults, recovery required, and suspended
16	Running with terminated
17	Completed with terminated
18	Running with faults and terminated
19	Completed with faults and terminated
20	Running with recovery required and terminated
21	Completed with recovery required and terminated
22	Running with faults, recovery required, and terminated
23	Completed with faults, recovery required, and terminated
24	Running with suspended and terminated
25	Completed with suspended and terminated
26	Running with faulted, suspended, and terminated
27	Completed with faulted, suspended, and terminated
28	Running with recovery required, suspended, and terminated
29	Completed with recovery required, suspended, and terminated
30	Running with faulted, recovery required, suspended, and terminated
31	Completed with faulted, recovery required, suspended, and terminated
32	Unknown
64	-

Any value in the range of 32 to 63 indicates that the composite instance state has not been enabled, but the instance state is updated for faults, aborts, etc.

CUBE_INSTANCE States

State	Description
0	STATE_INITIATED
1	STATE_OPEN_RUNNING
2	STATE_OPEN_SUSPENDED
3	STATE_OPEN_FAULTED
4	STATE_CLOSED_PENDING_CANCEL
5	STATE_CLOSED_COMPLETED
6	STATE_CLOSED_FAULTED
7	STATE_CLOSED_CANCELLED
8	STATE_CLOSED_ABORTED
9	STATE_CLOSED_STALE
10	STATE_CLOSED_ROLLED_BACK

DLV_MESSAGE States

State	Description
0	STATE_UNRESOLVED
1	STATE_RESOLVED
2	STATE_HANDLED
3	STATE_CANCELLED
4	STATE_MAX_RECOVERED

Since now in 11g the Invoke_Messages table is not there so to distinguish between a new message (Invoke) and callback (DLV) and there is DLV_TYPE column that defines the type of message:

DLV_TYPE States 

State	Description
1	Invoke Message
2	DLV Message

MEDIATOR_INSTANCE

State	Description
0	No faults but there still might be running instances
1	At least one case is aborted by user
2	At least one case is faulted (non-recoverable)
3	At least one case is faulted and one case is aborted
4	At least one case is in recovery required state
5	At least one case is in recovery required state and at least one is aborted
6	At least one case is in recovery required state and at least one is faulted
7	At least one case is in recovery required state, one faulted and one aborted
>=8 and < 16	Running
>= 16	Stale

Happy Learning....!!!!!!!!! Fun Sharing..........!!!!!!!!!!