Duplicate Instances in cube_instances with same root_id , parent_Id

Question

Environment - We are having a 2 node cluster installation of SOA SUITE 10.1.3.4, MLR-
We have a file poller (say ESB_poller) and for each record in the file we call a BPEL Process (say BPEL_parent) which call another BPEL process (say BPEL_child). BPEL_child calls a PL/SQL procedure which basicall does an insertion of each record in the DB.
PROBLEM - We have observed that when 2 to 3 large file containing 3000 records each is fed to the system, then sometimes, for 5 to 10 records we have 2 instances of BPEL_child process. They have the same root id and same parent id in CUBE_INSTANCE. One of them gives an error with primary key violation error while inserting in the DB. But the audit trail in BPEL Console for BPEL_parent shows only 1 instance of BPEL_child which has errored and hence our instance goes for exception handling (business perspective).
Could someone tell us,
1. WHY ARE THERE TWO INSTANCES OF BPEL_CHILD PROCESS?
2. UNDER WHAT SCENARIO WE SHOULD EXPECT THIS?
3. WHY AREN'T BOTH THE INSTANCE SHOWING IN BPEL CONSOLE?
4. HOW TO HANDLE THIS SCENARIO/ THE WORKAROUND?
NOTE : Call to child process is synch.
Fault policy is as follows for the process -
<Conditions>
          <!-- Fault if wsdlRuntimeLocation is not reachable -->
          <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
               <condition>
                    <action ref="ora-rethrow-fault"/>
               </condition>
          </faultName>
          <!-- Fault if location port is not reachable-->
          <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
               <condition>
                    <action ref="ora-rethrow-fault"/>
               </condition>
          </faultName>
     </Conditions>

Answer 1

Hi,
This is a problem with the clustered environment...add clusterGroupId to your file adapter activation agent to make sure only one activation agent is active at anytime in the clustered environment.
Have a luk at this link:Duplicate instance created in BPEL