2 Replies Latest reply: Mar 7, 2013 5:16 PM by 994429 RSS

    Message: ORA-01013: user requested cancel of current operation

    Buchez81
      Hi,
      I have been working an issue involving an application that is receiving "Message: ORA-01013: user requested cancel of current operation" errors. These errors are seen in the Application servers which are 6, w2k3 Standard sp2.
      My problem is the users are not the ones requesting the cancel. I have worked with my application support dept and they have informed me the timeout settign is 2 seconds. As you can see in my list below these transactions are taking longer then 2 seconds. A good transaction should take less then 3ms.

      Here is a short log of bad times this has occurred:

      Duration
      (in ms) Error Time
      2226       2013-01-22 12:30:11.023
      2006       2013-01-22 12:30:10.827
      2833       2013-01-22 11:38:56.813
      2026       2013-01-22 11:15:28.490
      2026       2013-01-18 15:00:24.930
      2990       2013-01-21 04:47:10.317
      2026       2013-01-18 11:14:45.370
      10910    2013-01-18 11:14:33.673 
      2026       2013-01-18 11:08:39.970
      2140       2013-01-18 11:08:33.310
      2140       2013-01-18 11:08:31.620
      2230       2013-01-18 11:08:30.330
      2130       2013-01-18 11:08:25.737
      3506       2013-01-18 09:00:15.453
      4390     2013-01-17 11:44:55.243
      9793     2013-01-17 11:44:55.233
      6216     2013-01-17 11:44:54.317
      4800     2013-01-17 11:44:54.313
      8443     2013-01-17 11:44:54.313
      2006     2013-01-17 11:44:52.980
      3143     2013-01-17 11:44:50.850
      3760      2013-01-17 11:44:47.697
      3406      2013-01-17 11:44:47.693

      Example's of good

      Duration
      (in ms) Event_Time
      3 2013-01-17 11:44:50.560
      0 2013-01-17 11:44:50.410
      3 2013-01-17 11:44:50.233
      0 2013-01-17 11:44:50.213
      0 2013-01-17 11:44:50.013
      3 2013-01-17 11:44:49.813
      0 2013-01-17 11:44:49.793
      3 2013-01-17 11:44:49.627
      0 2013-01-17 11:44:49.537
      0 2013-01-17 11:44:49.363
      0 2013-01-17 11:44:49.140
      3 2013-01-17 11:44:48.097
      3 2013-01-17 11:44:46.723
      3 2013-01-17 11:44:46.117
      3 2013-01-17 11:44:46.000


      We can't up the timeout setting in the application, We've already looked into it and theres to much red tape for us to cut in order to implement that setting.
      Recently our DB's were upgraded from Oracle 11.2.0.2 to Oracle 11.2.0.3. The very next day is when we started receiving these alerts.

      Any thoughts?