Tracking completion status for long running DML operations

Does anybody know:
Is there any possibility to track a completion status for long running DML operations (for example how many rows is inserted)?
For example if I execute an INSERT statement which is working for several hours it is very important to estimate the total time for this operation.
Thanks forward

I'm working with Oracle8 in present, and unfortunately this solution (V$SESSION_LONGOPS)cannot help me.
On Oracle8 it works, but with some restrictions:
- You must be using the cost-based optimizer
- Set the TIMED_STATISTICS or SQL_TRACE parameter to TRUE
- Gather statistics for your objects with the ANALYZE statement or the DBMS_STATS package.

Similar Messages

Alert monitor for long running background jobs

Hello,
I have to configure an alert moniter for long running background jobs which are running more than 20000 secs using rule based. I have created a rule based MTE and assigend MTE class CCMS_GET_MTE_BY_CLASS to virtual node but i dont find a node to specify the time.
could any one guide me how can i do this.
Thanks,
Kasi

Hi *,
I think the missing bit is where to set the maximum runtime. The runtime is set in the collection method and not the MTE class.
process: rz20 --> SAP CCMS Technical Expert Monitors --> All Contexts on local application server --> background --> long-running jobs. Click on 'Jobs over Runtime Limits' then properties, click the methods tab then double click 'CCMS_LONGRUNNING_JOB_COLLECT', in the parameters tab you can then set the maximum runtime.
If you need to monitor specific jobs, follow the process (http://help.sap.com/saphelp_nw70/helpdata/en/1d/ab3207b610e3408fff44d6b1de15e6/content.htm) to create the rule based monitor, then follow this process to set the runtime.
Hope this helps.
Regards,
Riyaan.
Edited by: Riyaan Mahri on Oct 22, 2009 5:07 PM
Edited by: Riyaan Mahri on Oct 22, 2009 5:08 PM

Profiler execution plan ONLY for long running queries

The duration only applies to specific profiler events however I'd like to capture the execution plan ONLY for queries over 10 minutes.
Is there a way to do this using Xevents?
Anyone knows?
Thanks!
Paula

I've wanted that too but could not find a way to get it from profiler.
But it may be possible with xevents (or without xevents!) to watch for long-running queries and then get the plan from the cache,where it will probably stick for some time, using DMVs.
Josh

RZ20 - Is there an alert for long running transactions?

In RZ20 is there an alert for long running transactions?

http://help.sap.com/saphelp_nw04s/helpdata/en/9c/f78b3ba19dfe47e10000000a11402f/content.htm
This document clearly explains your problem.
"Reward points if useful"

Considerations for long running publication extensions

We are considering implementing a post processing publication extension which may take several minutes to execute.   One of our concerns with this strategy is that the publication extension may bog down the Adaptive Processing Server.
Are there any general considerations / recommendations for long running post processing publication extensions?
Thanks!

Generally creating a new thread is an expensive process. Well, everything is relative. My laptop can create & run & stop 7,000+ threads per second, test program below, YMMV. If you are dealing with thousands of thread creations per second, pooling may be sensible; if not, premature optimization is the root of all evil, etc.
public class ThreadSpeed
    public static void main(String args[])
     throws Exception
        System.out.println("Ignore the first few timings.");
        System.out.println("They may include Hotspot compilation time.");
        System.out.println("I hope you are running me with \"java -server\"!");
     for (int n = 0; n < 5; n++)
         doit();
        System.out.println("Did you run me with \"java -server\"? You should!");
    public static void doit()
     throws Exception
        long start = System.currentTimeMillis();
        for (int n = 0; n < 10000; n++) {
         Thread thread = new Thread(new MyRunnable());
         thread.start();
         thread.join();
        long end = System.currentTimeMillis();
        System.out.println("thread time " + (end - start) + " ms");
    static class MyRunnable
     implements Runnable
     public void run()
}Edited by: sjasja on Jan 14, 2010 2:20 AM

Revoke Complete Status for Notification (is it possible?)

How can i revoke complete status for Notification??
Change NOCO back to NOPR?
just like revoke TECO in Production Order

Hi,
Yes it is possible, Goto QM02 -->select notf no >select notification>Functions>Inprocess again> now system status back from NOCO to NOPR.
Edited by: Lokesh K on Jun 14, 2011 10:35 AM

Is there any time out defined for long running transaction?

hi,
i have to make one big data transferring script , though transaction is not required here, but i was planning to,
please tel me is there any time out for long running transactions.i have to run the script from database it self
yours sincerley

Can you show us an example of your script? You can divide the transaction into small chunks to reduce time and locking/blocking as well.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Should EntryProcessors be used for long-running operations?

Hi Gene and All,
     a couple of other questions come from the seemingly unexhaustible list :-)
     - what happens if the caller of an InvocableMap.invokeAll or invoke method dies?
     - all entryProcessors complete regardless of the client being there or not
     - all already started process method calls complete, the unprocessed entries will not get processed
     - something else happens
     - what happens if the caller of an InvocableMap.aggregate method with a parallel-aggregator dies
     - all aggregate methods in the parallel-aggregator complete
     - the aggregate methods in the parallel-aggregator stop during processing
     - something else happens
     - should an entryprocessor or a parallel-aware entryaggregator implement a comparably long-running operation (e.g. jdbc access), or does that seriously affect performance of other concurrent operations within the cluster node or the entire cluster (e.g. becuase of blocking other events/requests)?
     - should the work manager be used instead for these kinds of things (e.g. jdbc access)?
     Thanks and best regards,
     Robert

Robert,
     As soon as an EntryProcessor or EntryAggregator get delivered to the server nodes, it will get executed regardless of the requestor's state.
     In regard to long-running operations the only thing you have to be conscious about is a number of worker threads allocated for such a processing. Since there is a single client thread issuing a request, it would suggests allocation as many worker threads (across the cache server tier) as there are client thread (across the presentation/application tier).
     Regards,
     Gene

Challenging question: Status report for long running program...

Hi All,
With all the control stuff around like cl_dd_document I was wondering if there is a way to give a user a report which shows the progress of a very long running program?
i.e. If I have a 20 step process and each step takes 1 minute, the following is what I would like to occur:
Output a status line in a report format, run step, repeat until all steps are finished.
This is similar to the status bar, but with a history of what is happening. Obviously scrolling needs to be considered also. Ideally it would behave like sapinst would but in a reporting format.
Obviously this has to bypass the PBO/PAI approach, hence why I believe UI Controls must be the answer.
Any ideas anyone?
Regards,
Matt

Without using a control, you could try the old report refresh trick using set user-command and an action triggered after an RFC in a new task ... see basic demo below:
report zlocal_auto_refresh no standard page heading.
data:
begin of gs_step,
    uzeit               like sy-uzeit,
    step                like sy-tabix,
    start_end(10)       type c,
end of gs_step,
gt_step               like gs_step occurs 10,
g_step_number         like sy-tabix.
*=======================================================================
* Events
*=======================================================================
at user-command.
perform user_command.
*=======================================================================
* Mainline
*=======================================================================
start-of-selection.
perform start_of_report.
end-of-selection.
*&      Form start_of_report
form start_of_report.
set pf-status '1000LIST'. "contains ZREFRESH ucomm
perform run_a_step.
endform.                    "start_of_report
*&      Form run_a_step
form run_a_step.
* Demo with something that takes some time, like sleeping...
data:
    ls_step             like gs_step.
add 1 to g_step_number.
if g_step_number > 9.
    stop.
endif.
get time.
clear: ls_step.
ls_step-step      = g_step_number.
ls_step-uzeit     = sy-uzeit.
ls_step-start_end = 'Starting'.
append ls_step to gt_step.
* generate a delay for demo
call function 'ENQUE_SLEEP'
    exporting
      seconds = 1
    exceptions
      others = 0.
get time.
clear: ls_step.
ls_step-step      = g_step_number.
ls_step-uzeit     = sy-uzeit.
ls_step-start_end = 'Ended'.
append ls_step to gt_step.
format reset.
format color col_normal.
loop at gt_step into ls_step.
    write: /
      ls_step-uzeit,
      ls_step-start_end,
      ls_step-step,
      at sy-linsz space.
endloop.
uline.
call function 'RFC_PING'
    starting new task 'NEWTASK'
    performing when_back on end of task.
endform.                    "run_a_step
*&      Form when_back
form when_back
using
    i_taskname          type any.
receive results from function 'RFC_PING'.
set user-command 'ZREFRESH'. "act like user pressed something
endform.                    "when_back
*&      Form user_command
form user_command.
case sy-ucomm.
    when 'ZREFRESH'.
      perform run_a_step.
      sy-lsind = sy-lsind - 1.
endcase.
endform.                    "user_command
cheers
jc

Messages in devivering status for long

Hi All,
I am in with a problem.I have an File XI RFC async scenario.While posting data to the RFC the message are kept on delivering status for very long .
If for this interface more than 5 files are kept all the othere messages are in to be delivered status which enlongens the queue.
Only 5 messages are getting delivered at a time as the number of RFC threads in XI Box is 5.
Please help me in this .
I had a thought that from XI side it was only a fire and forget type of scenario but is it possible that while delivering it waits for successfull compleation of the target systems application program.
Mudit Mehra

No not all but only a single interface is running slow.
Can you also explain on how to increase the parallet processes?
Mudit

Using MDBs for long running transactions

Although MDBs are not the best vehicles for running long transactions, I am
          forced to use them for one such scenario (let's say for lack of a better
          pattern). In order to let my long running MDB (with Container Managed Tx)
          do it's chores I increased the time-out value to a higher number rather than
          using the default of 30 secs. Strangely, I was seeing
          IllegalStateExceptions in stdout. So I created a brand new test MDB with a
          Thread.sleep for 60 seconds, increased my MDBs timeout value to 120 secs,
          made sure there was only one MDB in the pool and ran the test again. I
          still see the below error after 30 seconds.
          I guess I should probably open a support case, but I thought I'll post here
          as well in case there's something I am missing.
          <May 27, 2003 5:26:31 PM PDT> <Notice> <EJB> <Error marking transaction for
          rollback: java.lang.IllegalStateException: Cannot m
          ark the transaction for rollback. xid=64:bea55f200db2c786, status=Rolled
          back. [Reason=weblogic.transaction.internal.TimedOutEx
          ception: Transaction timed out after 34 seconds
          Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
          esOwedOthers=0,seconds since begin=34,seconds left=
          30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
          Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
          BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
          active),OwnerTransactionManager=ServerTM[ServerCoor
          dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
          Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
          40:7501+wlcsDomain+)]
          java.lang.IllegalStateException: Cannot mark the transaction for rollback.
          xid=64:bea55f200db2c786, status=Rolled back. [Reason
          =weblogic.transaction.internal.TimedOutException: Transaction timed out
          after 34 seconds
          Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
          esOwedOthers=0,seconds since begin=34,seconds left=
          30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
          Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
          BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
          active),OwnerTransactionManager=ServerTM[ServerCoor
          dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
          Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
          40:7501+wlcsDomain+)]
          at
          weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
          nsactionImpl.java:1486)
          at
          weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
          l.java:466)
          at
          weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
          ava:255)
          at
          weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
          5)
          at
          weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:153)
          at
          weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:117)
          at
          weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
          :63)
          at
          com.xoriant.hm.ejb.session.HierarchyManagerBean_fzysig_EOImpl.getHierarchyId
          (HierarchyManagerBean_fzysig_EOImpl.java
          :1477)
          at
          com.ebiz.application.customerprofile.hm.CPXHMController.SynchronizeMHTH(Unkn
          own Source)
          at
          com.ebiz.application.customerprofile.hm.CPHMOrgGroupMsgBean.onMessage(Unknow
          n Source)
          at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


Hi Adarsh,
          It may be that the transaction time-out setting in the descriptor
          is not taking effect. The tx is still timing out after
          the default 30 seconds, so the later attempt to call
          "setRollbackOnly" fails as the transaction has already
          rolled back The ignored descriptor setting is a known issue
          in some earlier SPs, but I'm not sure when and where it
          was fixed - so yes, contact customer support. The work-around
          is to set the default transaction time-out for the entire server to a
          higher value. (I'm not sure where to set this on the console,
          but the relevant JTA MBean field is "TimeoutSeconds".)
          Tom
          Adarsh Dattani wrote:
          > Although MDBs are not the best vehicles for running long transactions, I am
          > forced to use them for one such scenario (let's say for lack of a better
          > pattern). In order to let my long running MDB (with Container Managed Tx)
          > do it's chores I increased the time-out value to a higher number rather than
          > using the default of 30 secs. Strangely, I was seeing
          > IllegalStateExceptions in stdout. So I created a brand new test MDB with a
          > Thread.sleep for 60 seconds, increased my MDBs timeout value to 120 secs,
          > made sure there was only one MDB in the pool and ran the test again. I
          > still see the below error after 30 seconds.
          > I guess I should probably open a support case, but I thought I'll post here
          > as well in case there's something I am missing.
          >
          > <May 27, 2003 5:26:31 PM PDT> <Notice> <EJB> <Error marking transaction for
          > rollback: java.lang.IllegalStateException: Cannot m
          >
          > ark the transaction for rollback. xid=64:bea55f200db2c786, status=Rolled
          > back. [Reason=weblogic.transaction.internal.TimedOutEx
          >
          > ception: Transaction timed out after 34 seconds
          >
          > Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
          > esOwedOthers=0,seconds since begin=34,seconds left=
          >
          > 30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
          > Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
          >
          > BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
          > active),OwnerTransactionManager=ServerTM[ServerCoor
          >
          > dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
          > Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
          >
          > 40:7501+wlcsDomain+)]
          >
          > java.lang.IllegalStateException: Cannot mark the transaction for rollback.
          > xid=64:bea55f200db2c786, status=Rolled back. [Reason
          >
          > =weblogic.transaction.internal.TimedOutException: Transaction timed out
          > after 34 seconds
          >
          > Xid=64:bea55f200db2c786(-33600248),Status=Active,numRepliesOwedMe=0,numRepli
          > esOwedOthers=0,seconds since begin=34,seconds left=
          >
          > 30,activeThread=Thread[ExecuteThread: '9' for queue: 'default',5,Thread
          > Group for Queue: 'default'],ServerResourceInfo[JMS_hmJD
          >
          > BCStore]=(state=started,assigned=none),SCInfo[wlcsDomain+wlcsServer]=(state=
          > active),OwnerTransactionManager=ServerTM[ServerCoor
          >
          > dinatorDescriptor=(CoordinatorURL=wlcsServer+155.14.3.140:7501+wlcsDomain+,
          > Resources={})],CoordinatorURL=wlcsServer+155.14.3.1
          >
          > 40:7501+wlcsDomain+)]
          >
          > at
          > weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
          > nsactionImpl.java:1486)
          >
          > at
          > weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
          > l.java:466)
          >
          > at
          > weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
          > ava:255)
          >
          > at
          > weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
          > 5)
          >
          > at
          > weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:153)
          >
          > at
          > weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:117)
          >
          > at
          > weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java
          > :63)
          >
          > at
          > com.xoriant.hm.ejb.session.HierarchyManagerBean_fzysig_EOImpl.getHierarchyId
          > (HierarchyManagerBean_fzysig_EOImpl.java
          >
          > :1477)
          >
          > at
          > com.ebiz.application.customerprofile.hm.CPXHMController.SynchronizeMHTH(Unkn
          > own Source)
          >
          > at
          > com.ebiz.application.customerprofile.hm.CPHMOrgGroupMsgBean.onMessage(Unknow
          > n Source)
          >
          > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
          >
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          >
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          >
          >
          >

ADF page times out for long running backend procedure

Dear gurus,
I have an ADF 10g web page that invokes a long running backend PL/SQL procedure.
After some time, and while the web page awaits for the completion of the PL/SQL procedure, I get an *'Oops! This page appears broken'* from my browser (either IE or Firefox).
Does anybody know what setting to use to make my application endure long running backend procedures without timing out ?

What is the Application Server you are deploying to? In WebLogic for example, there are options to configure the server stuck thread timeout for instance.
Edited by: Nick Haralabidis on Jun 20, 2011 4:57 PM
Also, consider trying to figure out the exact exception or error message. For instance, if your are using a software load balancer solution it may be that this layer times out.

Creating wrapper procedures for Long running procedures

In SQL server, we can create a wrapper procedure to call long running procedure. Wrapper procedure calls long running procedure and returns to its calling application and give message "your request has been received and being processed. result will sent to your email-id." So user need not wait for complete execution for his request. From long running stored procedure we can send email to user stating all execution result he wants.
Is there any way to implement it in Oracle9i? Or any other technique to call such long running procedures asynchronously through wrapper procedure sothat user need not to wait and also avoid "request time out" error.

This question would be better off posed in the Oracle Data Provider for .NET forum.
Christian

OHS Webserver Timeout for long running requests

Hi,
I have applications which have some pages which make requests that take longer than 60 seconds to complete (say a report that takes more than a minute). I know that this may not be considered ideal to make a user wait this long, but the users are ok with this. And I know that there are work arounds, but I'd like to research if this problem is simply one of configuration before implementing such work arounds.
I have checked that the apache webserver timeout is set to the default of 300 seconds in httpd.conf, so this is not the issue. I have checked the other conf files (both for Apache and mod_plsql) on the webserver and these have been left with default settings, none of which suggest a 60 second limitation.
The databases being connected to are 10.1 and 10.2. The apex versions are 2.0 and 2.2.
To further test this issue I created a page in the app that submits a sleep request using a variable wait time (P1_WAIT). When P1_WAIT is set to 59 seconds it runs successfully. However, when I set P1_WAIT = 60 seconds (or greater) it timesout (the process continues successfully on the database, it's just that the OHS disconnects). I see no helpful information in either the apache or mod_plsql logs.
Any ideas?
begin
DBMS_LOCK.SLEEP(to_number(:P1_WAIT));
end;

Hello. We had a problem with long running web services as well. Main culprit is the httpd.conf Timeout setting. If the service took longer than 5 minutes to run, BPEL would get a generic remoteFault with a generic empty detail message. We worked with Oracle support and together figured this out: 1) the server hosting the web service needs to have the $ORACLE_HOME/Apache/Apache/conf/httpd.conf Timeout value set longer than the longest running web service - the default value is 5 minutes; 2) the BPEL partner link can be given the "timeout" property (ends up in the bpel.xml partnerlinkBinding section) which controls how long BPEL is willing to wait before giving up on the web service call. If this second limit is reached before the web service has completed you get a useful remoteFault, showing "java.net.SocketTimeoutException: Read timed out"

ORABPEL-05002 for long running process

Hi everybody,
My question is related with a long running process I have designed and which, after running for a couple of days, ends by reporting the ORABPEL-05002 error:
===============================================================
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
===============================================================
Looking in the Manual Recovery screen, I can see an Activity I can recover. It's about an assign Activity where I'm doing a single boolean assignation.
Of course, together with the ORABPEL-05002 error I got also the 'Transaction was rolled back: time out' message. Note that I have modified the transaction-timeout value to 180000. The error occurs during the night, with no heavy load of the server.
Recovering the assign activity brings back the process in the running state.
My process pattern:
while (1 == 1) {
do activity;
wait_timeout();
So, I have the following questions:
1. Which is cause of this error?
2. How may I automatically recover this lost activity? RecoveryAgent?
Any suggestion is appreciated.
Regards,
amo
P.S: the full stack of error messages reported in domain.log:
===============================================================
<2006-09-18 08:08:34,101> <ERROR> <SRH.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:873)
     at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1479)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: No Exception - originate from:
     at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:871)
     ... 10 more
javax.ejb.EJBException: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1479)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:08:34,129> <ERROR> <SRH.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.PerformMessage"; the exception is: Transaction was rolled back: timed out; nested exception is: java.rmi.RemoteException: No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
     java.lang.Exception: No Exception - originate from:
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,236> <ERROR> <SRH.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
ORABPEL-02094
Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
     at com.collaxa.cube.engine.core.ScopeContext.getScope(ScopeContext.java:213)
     at com.collaxa.cube.engine.core.WorkItem.setCubeInstance(WorkItem.java:259)
     at com.collaxa.cube.engine.core.WorkItemFactory.init(WorkItemFactory.java:68)
     at com.collaxa.cube.engine.core.WorkItemFactory.create(WorkItemFactory.java:58)
     at com.collaxa.cube.engine.adaptors.common.BaseWorkItemPersistenceAdaptor.load(BaseWorkItemPersistenceAdaptor.java:147)
     at com.collaxa.cube.engine.data.WorkItemPersistenceMgr.load(WorkItemPersistenceMgr.java:75)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5185)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5173)
     at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2136)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
     at IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
     at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,274> <ERROR> <SRH.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
ORABPEL-02094
Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
     at com.collaxa.cube.engine.core.ScopeContext.getScope(ScopeContext.java:213)
     at com.collaxa.cube.engine.core.WorkItem.setCubeInstance(WorkItem.java:259)
     at com.collaxa.cube.engine.core.WorkItemFactory.init(WorkItemFactory.java:68)
     at com.collaxa.cube.engine.core.WorkItemFactory.create(WorkItemFactory.java:58)
     at com.collaxa.cube.engine.adaptors.common.BaseWorkItemPersistenceAdaptor.load(BaseWorkItemPersistenceAdaptor.java:147)
     at com.collaxa.cube.engine.data.WorkItemPersistenceMgr.load(WorkItemPersistenceMgr.java:75)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5185)
     at com.collaxa.cube.engine.CubeEngine.load(CubeEngine.java:5173)
     at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2136)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:116)
     at IActivityManagerLocalBean_StatelessSessionBeanWrapper52.expireActivity(IActivityManagerLocalBean_StatelessSessionBeanWrapper52.java:645)
     at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
<2006-09-18 08:09:05,275> <ERROR> <SRH.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: Scope not found.
The scope "BpSwt2.30995" has not been defined in the current instance.
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:152)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
===============================================================

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)
Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.
Cheers
Anirudh Pucha

Tracking completion status for long running DML operations

Similar Messages

Maybe you are looking for