Delete Instances in BPEL console

HI
I am using Oracle SOA suite 10.1.3.1.0. So I will be having the Oracle lite as the dehydration store.
I Have around 6400 instances in my BPEL console.
What will happen when the number of instances are increasing.
I am using a BPEL process to read xml and add data to SQL server database.
When I deployed this process it was running properly. But now it is thrwoing the exceptions saying that the XPATH expression is failed.
But when I process the same file it is not throwing any exceptions. Is this somewhere related to number of instances in the BPEL console??
is there anyway to recreate the oracle lite database tables?
Is there any way I can delete all the instances on a periodic basic without using another process or coding??
Thanks
V Kumar

Well I have tried this crazy idea of using Oracle Lite with huge number of instance.
I did this in performance test environment, not in Production.
I could pump in huge number of transactions, and surprisingly Olite was able to take that.
But the real bolt came when I tried to use "Purge All Instances" from BPEL console.
The whole Olite crashed.
But this was way back in the first version of BPEL and in the GA version of it.
Never tried this in any version after that.
Every Little Helps
Kalidass Mookkaiah
http://oraclebpelindepth.blogspot.com/

Similar Messages

  • Delete stale instances using BPEL Console

    Hi,
    I want to delete all the stale instances at a time from a particular domain in produciton environment using BPEL console.
    I can delete them individually but i want to delete them all at one time
    Can any one please help me with the same.
    Thanks in advance.
    Edited by: 786384 on Aug 11, 2010 11:20 PM

    Currently you don't have this option out of box, leaving the users to customize the existing purge script. However, an Enhancement Request has been logged with Oracle DEV Team for the same.

  • DisplayInstance.jsp gives 404 when viewing instances in BPEL Console

    Using soa suite 10.1.3.4 on WL 9.2
    In the /BPELConsole app, deployed bpel processes list their instances on the instances tab. But clicking on any of the links for the instances gives a 404
    https://our_host:our_port/BPELConsole/default/displayInstance.jsp?referenceId=bpel://localhost/default/process_name/30054&mode=manage
    Removing the parameters from the above to the following resolves correctly and just re-displays the page at
    https://our_host:our_port/BPELConsole/default/instances.jsp
    I don't see any errors thrown in the "SOA_HOME"/bpel/domains/default/logs/domain.log or in the WL managed server logs other than the actual 404 itself in the WL access log:
    [14/Oct/2009:10:08:04 -0400] "GET /BPELConsole/default/displayInstance.jsp?referenceId=bpel://localhost/default/process_name/30049&mode=manage HTTP/1.1" 404 1214
    I've checked the esb_parameter table, and the dt_oc4j_host & dt_oc4j_http_port rows are correctly set to the server's host & port
    Although all of our WL instances use explicit ListenAddress values which match their host names, I'm pretty sure it's not the localhost portion of "bpel://localhost" as our other environments show the same syntax in their BPELConsole pages but correctly display the instances. And /etc/hosts does have the localhost entry.
    Yet when a process is invoked within the BPELConsole, the Initiate tab shows icons for Visual Flow, Audit Instance & Debug Instance which use very similiar addresss - which work. Note a very different referenceId:
    https://our_host:our_port/BPELConsole/default/displayInstance.jsp?referenceId=7cde75f4b22c157a:4d690c8d:1243a74da38:-7ef0&mode=flow
    and this also works:
    https://our_host:our_port/BPELConsole/default/displayInstance.jsp?referenceId=7cde75f4b22c157a:4d690c8d:1243a74da38:-7ef0&mode=manage
    But when using the Instances tab, the links give 404. So why ?

    Hi,
    I don't understand this behaviour in detail, by now. Could you please state if this is correct?
    1. I call an async bpel process A.
    2. The message is put in the delivery queue.
    3. My client is free again, not blocking.
    4. Process A does not show up in Console by now. (If I would call checkpoint(), it would do).
    5. A worker takes the message and instantiates the Process A.
    6. Process A instance is running now, calling some sync processes.
    7. NO dehydration so far.
    8. Process A does not show up in Console by now. The called subprocess (sync) do show up, if they are completed.
    9. Loop to 6, until Process A ends and makes callback to client.
    10. After sending callback, Process A shows up in Console.
    11. Now I can monitor, what HAS happened.
    I understand, that you can't commit your process data, until a regular dehydration point is reached.
    But consequence: I can't even SEE that there exists a process instance from A, until it worked through all the steps above. I just see a swarm of sub processes without an existing parent.
    That's the behaviour, you call "intended"?
    Workaround would be to do dehydration after each bpel invoke activity. Do you see a problem in doing this?
    Thanks in advance!
    Torsten

  • Error Handling mechanism in BPEL Console

    Hi
    One of our client wanted to handle the situations where a BPEL Instance at BPEL console got errored for different reasons.
    We Know that we can handle all possible error combinations with in a BPEL. But, here client requirement is because of any reasons (May be not problem because of any BPEL code) if BPEL Process Instance will complete with error in BPEL Console how do we handle those errors. Do, we have any control on BPEL console.
    Please do share your experience on this requriement.
    Regards
    Kiran Akkiraju

    I have tried to chain two conditions when a remote fault occurs, as described in the links suggested.
    ora-retry and then ora-human-intervention.
    But only the last condition is executed, in this case it is the human-intervention. The retry is definitively not executed.
    If I do the other way around human then retry, only retry is executed.
    Does someone has the same issue?
    Extract from DefaultPolicy.xml:
         <Conditions>
              <!-- Fault if wsdlRuntimeLocation is not reachable -->
              <faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
                   <condition>
                        <action ref="ora-retry"/>
                   </condition>
                   <condition>
                        <action ref="ora-human-intervention"/>
                   </condition>

  • Error message in BPEL console when purging instances

    Hi
    I get an error message in the BPEL console when I Purge All Instances. The problem arised when i patched SOA suite to version 10.1.3.3. (On 10.1.3.1 i beleive this worked.)
    ======================================
    Exception
    Operation failed because:
    Cannot delete instances.
    The process domain was unable to purge the instances from the datastore. The exception reported is: [POL-5130] table or view SYSTEM.WI_FAULT not found
    Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: DELETE FROM wi_fault WHERE domain_ref = ?
    ======================================
    I also get a similar error message when i use the search activity function in the BPEL console, and when I use the java-api:s to search among activities.
    Does anyone know anything about this error?
    Thankyou
    //Kalle

    I got the same error, but long after I upgraded to 10.1.3.3.
    As this was on Windows with Oracle Lite, I did like below to fix the issue. Unfortunately I seem to have more issues with the BPEL database so I'm going to try to find a way to reinitialize it from scratch.
    C:\product\10.1.3.1\OracleAS_1\Mobile\Sdk\BIN>msql system/manager@jdbc:[email protected]:1531:orabpel
    SQL> @C:\product\10.1.3.1\OracleAS_1\bpel\system\database\scripts\upgrade_10131_10133_olite.sql
    [POL-5130] table or view SYSTEM.WI_FAULT not found
    Table created
    Index created
    Index created
    Object created
    Object created
    [POL-5130] table or view SYSTEM.WFPRODUCTIVITY_VIEW not found
    [POL-5130] table or view SYSTEM.WFTASKPRIORITY_VIEW not found
    [POL-5130] table or view SYSTEM.WFUNATTENDEDTASKS_VIEW not found
    [POL-5130] table or view SYSTEM.WFTASKCYCLETIME_VIEW not found
    View created
    View created
    View created
    View created
    Commit complete

  • SOA Suite 10.1.3.4 loses instances in the BPEL console

    Hello,
    One of my BPEL processes loses instnaces in the BPEL console.
    OS: AIX 5.3 oslevel –s:5300-04-02
    SOA Suite 10.1.3.4
    I feel I hit the same problem as this thread, process is supposed to be in a jta transaction
    But I have set following 3 values (all in seconds), and I still have the problem. The SYNC call is to query the Oracle EBS PO by PO NO, and get its po lines, line shipments, and shipment distributions by Oracle Database Adapter. If my PO just had one line, the process instance can be seen in the console, otherwise it won't, but all these instances are finished, because in the end the process will enqueue a message into a queue. And I can see all these messages there. Anyone can help? Thanks!
    $ORACLE_HOME/j2ee/oc4j_soa/config/transaction-manager.xml
    transaction-timeout="240"
    $ORACLE_HOME/j2ee/oc4j_soa/application-deployments/orabpel/ejb_ob_engine/orion-ejb-jar.xml
    transaction-timeout="180"
    $ORACLE_HOME/bpel/domains/default/config/domain.xml
    <property id="syncMaxWaitTime">
    <name>Delivery result receiver maximum wait time</name>
    <value>600</value>
    -------------- Error messages ----------------
    <2009-04-02 11:40:03,319> <ERROR> <default.collaxa.cube.engine> The execution of this instance "40002" for process "PROEBSMsgToB2B" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    <2009-04-02 11:40:03,324> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Scope not found.
    The scope "BpPrc0.1" has not been defined in the current instance.
    ORABPEL-02094
    Scope not found.
    The scope "BpPrc0.1" has not been defined in the current instance.
    Regards,
    Kerr
    Edited by: Kerrs on 2/04/2009 12:15

    Hi Kerr,
    These are the possible cause to the problem and their solutions:
    Poor performance of the dehydration database If you are using Oracle Lite as dehydration store, please switch to use Oracle 9i or 10g. If Oracle 9i/10g is already in use, check the database parameter 'process' and 'session' to make sure it can handle the expected throughput.
    OC4J has too few available connections to the dehydration database. Increase the maxConnection number of the BPELServerDataSource at the BPEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml (for developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/data-sources.xml (mid-tier installation).
    Size of message is too big Two ways to deal with this problem:
    Increase the transaction timeout at PEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/server.xml (developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/server.xml (mid-tier installation) : http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/app_trblshoot.htm#sthref3957
    Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.
    Having said all that , its always good to be on latest 10.1.3.4 MLR # 5, so that if you have an SR logged with Oracle Support, they will not again ask you to upgrade to latest patch, rather they can focus on getting a fix for you on top of the latest patch itself.
    Hope this helps!
    Cheers
    Anirudh Pucha

  • BPEL Console doesn't show any instances created

    Hi,
    We are using file protocol to read the files from trading partner into B2B. File is successfully processes by B2B. I can see that in reports.
    Then I have defined a BPEL process to Dequeue the messages from B2B using AQ Adapter, transforms and places the files in the local file system.
    The BPEL process is simple flow with one receive , transform and invoke activity.
    I have configured AQ adapter using WSIF browser. I can see the deployed document definition in browser.
    I have the TP agreement deployed, BPEL process deployed, but I don't see the 850 file processed. BPEL Console doesn't show any instances created. How would I know where what went wrong?
    Please help.

    Try using java oracle.tip.adapter.b2b.data.IPDequeue to dequeue the message and see if you can dequeue
    Then you'l be able to pin point if the issue is with your BPEL or with B2B Queue's
    Kalyan

  • Upgraded to BPEL 10.1.3.4, but BPEL console doesn't list all the instances

    Hi,
    I have upgraded from Oracle SOA 10.1.3.1 to 10.1.3.4 and have a simple BPEL deployed. It works fine and I can see the instances while they are in the running state. But after they are completed, the search page doesn't list them. Is there a problem with the console? I can see all the completed instances in the CUBE_INSTANCE table in the olite database.
    Thanks
    Clement

    Could you confirm if you have completed 1.6 steps successfully?
    Is the process deploying fine and able to see the instance created on console ? Able to see the tasks created for the user on worklist app console ? 10.1.3.4 + any MLR ?

  • Instance missing in BPEL console

    Hi,
    I have a process say "THIRD", it has database adapters and exception handling for each scope as well. In the case of any exception in "THIRD", the process calls the another process say "EMAIL" which is only meant for e-mail notification.
    Now the situation:
    When sometimes the process name "THIRD" is invoked from client(Oracle Apps/BES) first time in the morning and if any of the DB adapter throws exception, the instance of "EMAIL" is created and send the mail too. But if we try to find out the instance of "THIRD" which cause the problem is missing in BPEL Console.
    Moreover, it happens only first time in the morning and doesn't happen everyday.
    Thanks in advance.
    ---Janit

    Is your BPEL deployed on OC4J?
    Described property is here
    <ORAHOME>\integration\orabpel\system\appserver\oc4j\j2ee\home\config\server.xml
    restart OC4J. Check also BPEL domain parameter syncMaxWaitTime (From BPEL Console-> Manage BPEL Domain). syncMaxWaitTime should be less than transaction-config timeout. Otherwise it is not working properly.
    <snip>
    <?xml version="1.0"?>
    <!DOCTYPE application-server PUBLIC "-//Oracle//DTD OC4J Application-server 9.04//EN" "http://xmlns.oracle.com/ias/dtds/application-server-9_04.dtd">
    <application-server application-directory="../applications"
    check-for-updates="false"
    deployment-directory="../application-deployments"
    connector-directory="../connectors"
    >
         <rmi-config path="./rmi.xml" />
         <jms-config path="./jms.xml" />
         <j2ee-logging-config path="./j2ee-logging.xml" />
         <log>
              <file path="../log/server.log" />
         </log>
         <transaction-config timeout="60000" />
    </snip>

  • BPEL Console not showing instance.

    I have written an Empty BPEL (not sync/async) process. Internally it calls three synchronous Web Services(partner links). The process starts with a DB poller. When I run the process the three partnerlink process instances are shown but the main BPEL does not appear in the instances list in the BPEL Console. (This is occuring whenever there is a fault in the BP, when the BP executes successfully it is shown in the BPEL Console.) How can I get to know the error in such a case?
    Adding a Java Embedding did not work because when the Java Embedding is after the step where the fault is occuring then the instance is not getting reflected.
    Any idea where BPEL process logs are written and how can I write custom logs in the log file?
    Any help would be appreciated.

    Check the log file at
    $ORACLE_HOME/opmn/logs/default*.log

  • Process Instances do not appear in BPEl console

    HI everybody
    I have a Asyn BPEL worflow which consists of a receive business event lisening to a change in database which in turn initiates a BPEL flow.The problem i am facing is that when i do make a change in database everything works fine but i am not able to see the process instances generated , in BPEL console instantly. I have to restart the BPEL server one or more time in order to view them on the console. have any body faced a similar prob ??

    SOA version ? Able to see the processes in the manual recovery section ? Processes disappear or insatnces ?
    Errors in the logs ? What happens if you randomly click on various tabs of the console - still unable to see the previous instances ?

  • Instance not found in BPEL Console until Process finished

    I have two services on the server, where one (asynchronous) service is calling another (synchronous) service multiple times.
    WHen creating an instance in the BPEL Console, this instance is nowhere to be found. When trying to see the flow, an error message occurs in the console and on the BPEL server window:
    ORABPEL-02152
    Instanz in Datenquelle nicht gefunden.
    Die Prozessdomõne konnte die Instanz mit dem Schl³ssel "226865cd4e81777c:1a001ff
    :10c814abd65:-7f83" nicht aus der Datenquelle abrufen.
    Stellen Sie sicher, dass sich der Schl³ssel "226865cd4e81777c:1a001ff:10c814abd6
    5:-7f83" auf eine g³ltige Instanz bezieht, die gestartet und nicht aus der Proze
    ssdomõne entfernt wurde.
    at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:314)
    at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:262)
    at com.collaxa.cube.engine.data.AdminFinder.lookupInstanceByConversationId(AdminFinder.java:235)
    at com.collaxa.cube.ejb.impl.FinderBean.lookupInstanceByConversationId(FinderBean.java:177)
    at IFinderBean_StatelessSessionBeanWrapper42.lookupInstanceByConversationId(IFinderBean_StatelessSessionBeanWrapper42.java:669)
    at com.oracle.bpel.client.Locator.lookupInstance(Locator.java:420)
    at displayInstance.jspService(_displayInstance.java:111)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
    at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Interestingly, the instances of the (synchronous) service, which are called from the mysterious service, are visible all the time and the flow can be viewed while these services are processed.
    Does anybody have an idea why this is happening?
    Thank you,
    Nina

    Hi,
    I don't understand this behaviour in detail, by now. Could you please state if this is correct?
    1. I call an async bpel process A.
    2. The message is put in the delivery queue.
    3. My client is free again, not blocking.
    4. Process A does not show up in Console by now. (If I would call checkpoint(), it would do).
    5. A worker takes the message and instantiates the Process A.
    6. Process A instance is running now, calling some sync processes.
    7. NO dehydration so far.
    8. Process A does not show up in Console by now. The called subprocess (sync) do show up, if they are completed.
    9. Loop to 6, until Process A ends and makes callback to client.
    10. After sending callback, Process A shows up in Console.
    11. Now I can monitor, what HAS happened.
    I understand, that you can't commit your process data, until a regular dehydration point is reached.
    But consequence: I can't even SEE that there exists a process instance from A, until it worked through all the steps above. I just see a swarm of sub processes without an existing parent.
    That's the behaviour, you call "intended"?
    Workaround would be to do dehydration after each bpel invoke activity. Do you see a problem in doing this?
    Thanks in advance!
    Torsten

  • Process instances do not show in BPEL Console

    Hi all,
    I have a BPEL, which reads a files from a particular folder if any, Process records in that file and then stores it in database.
    I am facing a problem, my records gets processed, this BPEL works fine, as i can see the output in database, however associated instances are not shown in the BPEL Console. But if i restart the process (i.e. Switch OFF the process and Again Switch ON) it shows me all the previous instances and also the current instances. But sometime again this problem occurs.
    Has anyone faced the same issue? Please let me know in case anyone has solution.
    Thanks in advance.

    [http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf|http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf] I found below in SOA best practices guide:
    Why Does the Instance of an Invoked Process Not Display in Oracle BPEL Control?
    If the process invoked is asynchronous, the message headers and payload are stored in
    the invoke_message table. The invocation message is then processed by a
    background thread to create an asynchronous BPEL process instance. If an error is
    encountered while processing the invocation message, the transaction is rolled back
    and the invoke message remains in its unhandled state in the invoke_message table.
    See "How Does an Invoke Message and Activity Display in the Manual Recovery
    Page?" on page 1-18 for more details on this scenario.
    If the process invoked is synchronous, the cause for the missing instance is likely a
    transaction rollback. The reasons for a transaction rollback are as follows:
    ■ Third party manipulation of the JTA transaction. As described in "How Do I Force
    a Rollback in a BPEL Flow?" on page 1-5, a failed database adapter invocation can
    cause the TopLink layer to mark the JTA transaction for rollback. Because Oracle
    BPEL Server relies on the JTA transaction for persistence (not just as a signaling
    mechanism between transaction-aware modules), any changes to the status of the
    transaction impact Oracle BPEL Server’s ability to dehydrate the instance.
    ■ Transaction timeout. The synchronous process may be invoking one or more
    backend synchronous services; the total time of all the backend calls may exceed
    the timeout value for the transaction. See "How Do I Modify Transaction Timeout
    Settings for Oracle BPEL Server?" on page 1-9 for details on how to increase the
    transaction timeout value.
    ■ Failure to dehydrate the synchronous instance to the database. If the
    completionPersistPolicy is set to on, the instance attempts to save itself
    before returning to the caller. Typically, errors are encountered during this step if
    the database connection has been severed or the tablespace is full. Some customers
    Transactions
    Oracle BPEL Process Manager 1-9
    have encountered problems with saving the audit trail of the instance. For
    example, there are problems with JDBC batching in 10.1.3.1.0 that the audit trail
    persistence code uses. When a synchronous invocation does not result in an
    instance visible from Oracle BPEL Control (assuming that
    completionPersistPolicy is set to a value of on, deferred, or faulted),
    use the following steps to find the underlying error:
    – Enable all loggers to debug mode.
    – Resubmit the invocation message.
    – Check the Oracle Process Manager and Notification Server (OPMN) or
    command-line log for the underlying exception stack trace.
    Please refer to link below:
    http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf

  • Instance doesn't initiate from BPEL console

    BPEL 10.1.2.0.2
    Where can I find debug messages to understand why the process doesn't initiate from bpel console? message on console reads:
    'Cannot find the specified instance'
    Thanks

    Check the Domain.log. I suspect you have an invalid XPATH expression before you reach the first hydration point. Take a look on the Manual Recovery Queue and you should see the Invoke message sitting there.
    Pete

  • Unable to use BPEL instance search form in BPEL Console

    Hi,
    I have a few instances whose titles are as follows
    2481046 : Log:FAILDLVRY:ABCD
    2481047 : Log:FAILDLVRY:ABCD
    2481048 : Log:DLVRD:ABCD
    2481049 : Log:GOTACK:ABCD
    I want to search for instances whose title contains FAILDLVRY.
    In the search form that appears on the left side in Instances tab of BPEL console, I tried giving the following values for title field, but none works..
    \*FAILDLVRY\*
    %FAILDLVRY%
    FAILDLVRY
    What is the correct format to be able to search any instance that has title with FAILDLVRY?
    I am on 10.1.3.4
    Thanks,
    Amit

    There's no wild card search available on the BPEL console. You have to search for the whole of the title text excluding the instance ref ID.
    The best thing to search in your case would be - +'Log:FAILDLVRY:ABCD'+ wherein am asssuming that +'ABCD'+ is some constant.
    hth,
    -Shishir

Maybe you are looking for