ORA-01013: user requested cancel of current operation Disconnected from Ora

Hi Hussein;
When i run my script for cold backup in r11.5.10.2 solaris 9.2.0.8 database it gives me:
ORA-01013: user requested cancel of current operation Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production
What is matter?

Hi,
Run this query to determine the session details of the OS PID:
SQL> select s.sid, s.serial#, s.username, s.osuser, p.spid, p.terminal, s.program
from v$session s, v$process p
where paddr=addr
and spid='<OS PID>';Regards,
Hussein

Similar Messages

ORA-01013: User requested cancel of current operation (#1013)

Hi Guys,
I have an application and in particular an append query that inserts rows into a linked table. I keep on getting this error, (although the code works fine in enterprise manager, and code-imports ok).
I did not cancel the query but it seems to think it has. The insert/append query starts and prompts me for the username and password, this works fine, it just stops half way or beggining etc...
This is the error:
ORA-01013: User requested cancel of current operation (#1013)
And this is the error on Help file:
ODBC – call failed. (Error 3146)
Using an ODBC connection, you tried to perform an operation on data in an ODBC data source. This error may occur when the ODBC data source is on a network drive and you are not connected to the network. Make sure the network is available, and then try the operation again.
Cheers
Champinco

Does "linked table" imply that you're using Access as a front-end for Oracle? I know that Access sets a query timeout value when it works with ODBC connections and this error generally occurs when you have a query that exceeds that timeout. I don't know whether Access lets you adjust that timeout, but assuming you're using the Oracle ODBC driver, you should be able to disable query timeout in the DSN configuration.
Justin

Hi, i am getting oracle error ora-01013 user requested cancel of current operation.

I know this is timeout error however my select query simply returns count from 2-3 tables.. any help would be appritiated, please help me.

Hi Ramin,
Thanks for reply. Below is the query i am running,
SELECT COUNT(TRN.TRANSACTIONID)
FROM TRANSACTIONDATA TRN,
CONTENTDATA CND,
ACTIVITY AC,
ACTIVINVOL AVL,
PARTY PR
WHERE TRN.T_ID=CND.T_ID
AND CND.CD=AC.CD
AND AC.AD=AVL.AD,
AND AVL.PRD=PR.PRD
AND PR.SPRI=42345
AND TRN.LUT > '16-JUN-2013'
AND UPPER(TRN.T_ID) LIKE 'ONE AND DONE COM%' ;
WHICH OCCURS ERROR ora-01013 user requested cancel of current operation.
THANKS
DESHMUKH

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

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?

What's it doing during these bad transactions? Is there a difference between what those are doing and what the fast ones are doing?
Off the top of my head with so little information, the only thing I can come up with is that a lock is being held which is delaying some of the transactions from completing until after the timeout hits.

ORA-01013 User requested cancel of current operation

Hi
I'm stuck with ORA-01013 on RDBMS 7.3.2.3.0 on OpenVMS 7.1. Yes, I know the product is long time desupported by Oracle, but some systems are built to last ... (!)
My client application is built with Forms 4.5; the application has a trigger running a longlasting database maintenance job.
Depending on overall system load ORA-01013 may show up more often, causing the application to fail, and job must be re-started. Setting the SQLNET.EXPIRE_TIME=0 (on server and client) apparently has no effect (I restarted the client only after changed settings).
I found bug no 590961 on metalink, and there should exist a patch held by global support, but no direct link. And there is no way that I may register issues for 7.3 using Metalik.
Upgrading Oracle to a supported version is unfortunately no option. Any suggestion for corrective actions that can be taken; it surely would be appreciated?

ORA-01013 is not an error message, it says someone/something (mostly a human) has interrupted the running application. You cannot avoid this by changing parameters or settings. Maybe users are too impatient and hit the interruption keys, if they think the application is stuck.
Werner

CsDbUnableToStartTransaction() ORA-01013: user requested cancel of current

Hello Guru's,
We are getting this error once in a while(may be once in 20 check-in's). Please through some lights why this error occurs? Thanks in advance.
Error Log :
sscproducmap02.ph.rc: Event generated by user 'fmwadmin' at host 'xxxxxxxxxxxx:7151'. csDbUnableToStartTransaction() ORA-01013: user requested cancel of current operation
csDbUnableToStartTransaction() ORA-01013: user requested cancel of current operation
java.sql.SQLException: ORA-01013: user requested cancel of current operation [ Details ]
An error has occurred. The stack trace below shows more information.
!$sscproducmap02.ph.rc: !csUserEventMessage,fmwadmin,xxxxxxxxxxx:7151!$!csDbUnableToStartTransaction,!$ORA-01013: user requested cancel of current operation<br>!csDbUnableToStartTransaction,!$ORA-01013: user requested cancel of current operation<br>!syExceptionType2,java.sql.SQLException,ORA-01013: user requested cancel of current operation<br>
intradoc.common.ServiceException: !csDbUnableToStartTransaction,!$ORA-01013: user requested cancel of current operation
     at intradoc.data.WorkspaceTransactionWrapper.beginTransaction(WorkspaceTransactionWrapper.java:52)
     at intradoc.server.ServiceRequestImplementor.beginTransaction(ServiceRequestImplementor.java:285)
     at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1186)
     at intradoc.server.Service.doActions(Service.java:447)
     at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1121)
     at intradoc.server.Service.executeActions(Service.java:433)
     at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:635)
     at intradoc.server.Service.doRequest(Service.java:1707)
     at intradoc.server.ServiceManager.processCommand(ServiceManager.java:359)
     at intradoc.server.IdcServerThread.run(IdcServerThread.java:197)
Caused by: intradoc.data.DataException: !csDbUnableToStartTransaction,!$ORA-01013: user requested cancel of current operation
     at intradoc.jdbc.JdbcWorkspace.handleSQLException(JdbcWorkspace.java:2371)
     at intradoc.jdbc.JdbcWorkspace.beginTranEx(JdbcWorkspace.java:1059)
     at intradoc.data.WorkspaceTransactionWrapper.beginTransaction(WorkspaceTransactionWrapper.java:47)
     ... 9 more
Caused by: java.sql.SQLException: ORA-01013: user requested cancel of current operation
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
     at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
     at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190)
     at oracle.jdbc.driver.OracleStatement.doScrollExecuteCommon(OracleStatement.java:4086)
     at oracle.jdbc.driver.OracleStatement.doScrollStmtExecuteQuery(OracleStatement.java:4234)
     at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1661)
     at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1626)
     at intradoc.jdbc.JdbcWorkspace.beginTranEx(JdbcWorkspace.java:1038)
     ... 10 more

The ORA-01013 error is a database error. The error is thrown when an activity is cancelled by the requested user before it was completed.
In this case UCM is the application that is cancelling a database query/update/etc. UCM does this automatically if a database action takes
longer then a treshold value (I think by default it's 30 seconds, but I am not completely sure).
If you are suffering from ORA-01013 it might be good to contact your DBA and ask if there are any queries from your UCM application that
take a long time. Or trace the systemdatabase event and look for queries that take a long time.

ORA-01013: user requested cancel...........

Hi,
I've an application on Oracle 10.2.0.3.0 that run a basic script but I get always this error:
ORA-01013: user requested cancel of current operation
I was thinking to solve the problem by changing the ODBC settings in ODBC sources, I'd like to uncheck the "Enable Query Timeout" option, BUT when I trying to do the following with the Oracle ODBC Driver version 10.2.0.3.0 I get the error:
"An unsupported operation was attempted"
Have someone any idea How can I fix my ORA-01013 error and ODBC error?
Thanks in advance!

Sqlnet.expire_time=0 which is a way to eable DCD wil not help here.
Please try to set the sqlnet. inbound_connect_timeout . But I doubt this will help because these parameters solves the timeout error.. the error we are getting here is like pressing ctl C while something is running.
The best way will be to enable a client trace and see the network error.
Also you can run the script locally to the server (if possible) to narrow down the issue.

Error: USer request cancel of current operatin

Hi,
My database is in 10.2.0 and OS is Windows 2003. We are having some inhouse MIS reports. One report was running earlier without any error. But past few days I am getting the following error:
Can any one help me.
Microsoft OLE DB Provider for ODBC Drivers error '80040e31'
[Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
/mis/procedures.asp, line 291
thankyou
satyanag

ORA-01013 user requested cancel of current operation
Cause: The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only.
Action: Continue with the next operation.
So it means that you need to check back with the application. If its coming from the MIS than check back what's happening in the file that is given in the error.
Aman....

User Cannot Cancel Meeting Arranged by delegate from their own Calendar

Environment is Outlook 2010 running on windows 7. We are up to date with service packs/updates. Back end is exchange 2010 SP1 with Rollup 8. Users connect in cached exchange mode.
User A has a delegate (User B) setup on her mailbox who has editor permissions on Calendar, Tasks and Inbox, User B is also set to receive copies of meeting related requests.
User B will open User A's calendar and create a new meeting inviting attendees and adding a meeting room.
User A will later decide to cancel the meeting so opens the meeting and clicks the cancel meeting button. A dialogue box opens saying she doesn't have permission. The meeting stays in her calendar.
I have tried to replicate the issue by setting up the same permissions between two separate mailboxes and everything works fine.
Anyone have any Ideas why this user can not cancel meeting in her own calendar?

Hi,
Please try the following steps to narrow down the issue:
1. Check whether UserA can cancel the meeting request which is created by himself in his own Calendar.
2. Disable Exchange Cached mode and use Outlook Online to cancel the meeting request which was created by UserB.
If the issue doesn't happen in Outlook Online mode, please create a new Outlook profile to have a try:
http://support2.microsoft.com/kb/829918/en-us
Regards,
Winnie Liang
TechNet Community Support

OCITransCommit() returns ORA-01013 for correctly committed transaction

I had the following issue which seems to me a critial bug in Oracle 11g:
Breaking an oracle transaction asynchronously with OCIBreak() while transaction is being committed with OCITransCommit() did result in a correctly committed transaction on the database server. However OCITransCommit() returned ORA-01013 (user requested cancel of current operation) which is inconsistent. It should never happen that the transaction is correctly committed and OCITransCommit() returns anything other than OCI_SUCCESS.
My assumption is that the transaction is only committed on the database server if the OCITransCommit() returns OCI_SUCCESS. Or is this assumption not always correct?
Oracle version 11.2.0.3.0 64bit (Linux)

As Karthick says, perhaps the Call Interface forum is a better place to ask.
However, as a guess on my part (I've rarely had a need to go directly into OCI calls) from what I know of the internal workings of transactions on Oracle, the COMMIT operation is an atomic (if that's the right word to use here) operation. When you issue a COMMIT from your code, it doesn't go off to the database, do loads of work committing your data and writing it to the disks etc. before execution is returned to your code, it is a very basic instruction to the database to commit the data, which then goes off and does that in the background, whilst execution is returned immediately to the calling code, and Oracle in the background can take it's time getting the data written, and can present the data to your session and others, as if it is actually on the tables. This is all handled using the SCN and the logs internally and users don't have to worry about it (usually) because it all appears on the front end as though the data exists and is written on the tables.
So, I'm curious as to how you (or the OCI calls) are managing to issue a "break" to try and break a commit from happening. Without seeing code it's hard to see how you are testing this.
I've just looked up the documentation for TransCommit...
http://docs.oracle.com/cd/E11882_01/appdev.112/e10646/oci17msc006.htm#LNOCI13112
and I see you have the option of "Waiting" for the LGWR to write the transaction to the online redo logs, so that's a possible scenario for breaking, though I imagine you'd have to get in quickly with the break from another thread if the one thread is waiting for the commit.
Intersting part of the docs...
>
Under normal circumstances, OCITransCommit() returns with a status indicating that the transaction has either been committed or rolled back. With global transactions, it is possible that the transaction is now in doubt, meaning that it is neither committed nor terminated. In this case, OCITransCommit() attempts to retrieve the status of the transaction from the server. The status is returned.
>
Still, it would be interesting to see the test code to reproduce this.... just my morbid curiosity for low level coding.... ;)

ORA:01013 with Duplicate Database - RMAN

Hi,
I havea demo database on server1 and am creating a clone database on server2 with RMAN duplicate command. I have the catalog on server1 itself. I created the backups of the database and executed RMAN command from server2 with
server1 in open status and server2 in nomount state.
the command i ran was:
duplicate target database to clonedb
until logseq 338 thread 1
pfile=/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora
logfile
'/u01/app/oracle/oradata/clonedb/redo01.log' size 1m,
'/u01/app/oracle/oradata/clonedb/redo02.log' size 1m;
Please let me know how to overcome this error..
Thanks,
Raj
This is the error i got along with the log it created...
Starting Duplicate Db at 28-OCT-04
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=14 devtype=DISK
printing stored script: Memory Script
set until scn 130734;
set newname for datafile 1 to
"/u02/oradata/clonedb/system01.dbf";
set newname for datafile 2 to
"/u03/oradata/clonedb/undotbs01.dbf";
set newname for datafile 3 to
"/u02/oradata/clonedb/testtbs_01.dbf";
set newname for datafile 4 to
"/u02/oradata/clonedb/system02.dbf";
set newname for datafile 5 to
"/u02/oradata/clonedb/rmantbs_01.dbf";
restore
check readonly
clone database
executing script: Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 28-OCT-04
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /u02/oradata/clonedb/system01.dbf restoring datafile 00002 to /u03/oradata/clonedb/undotbs01.dbf
restoring datafile 00003 to /u02/oradata/clonedb/testtbs_01.dbf
restoring datafile 00004 to /u02/oradata/clonedb/system02.dbf restoring datafile 00005 to /u02/oradata/clonedb/rmantbs_01.dbf
channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/full/DEMODB_20041027_05g3jeeq_1_1 tag=FULL params=NULL channel ORA_AUX_DISK_1: restore complete Finished restore at 28-OCT-04 sql statement: CREATE CONTROLFILE REUSE SET DATABASE "clonedb" RESETLOGS ARCHIVELOG
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 680
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/clonedb/redo01.log' SIZE 1048576 ,
GROUP 2 '/u01/app/oracle/oradata/clonedb/redo02.log' SIZE 1048576
DATAFILE
'/u02/oradata/clonedb/system01.dbf'
CHARACTER SET WE8ISO8859P1
printing stored script: Memory Script
switch clone datafile all;
executing script: Memory Script
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=540710832 filename=/u03/oradata/clonedb/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=540710832 filename=/u02/oradata/clonedb/testtbs_01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=540710832 filename=/u02/oradata/clonedb/system02.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=540710832 filename=/u02/oradata/clonedb/rmantbs_01.dbf
printing stored script: Memory Script
set until scn 130734;
recover
clone database
delete archivelog
executing script: Memory Script
executing command: SET until clause
Starting recover at 28-OCT-04
using channel ORA_AUX_DISK_1
starting media recovery
channel ORA_AUX_DISK_1: starting archive log restore to default destination channel ORA_AUX_DISK_1: restoring archive log archive log thread=1 sequence=337 channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/arch/arc_DEMODB_20041027_06g3jef2_1_1 tag=TAG20041027T134050 params=NULL channel ORA_AUX_DISK_1: restore complete archive log filename=/u02/oradata/clonedb/arch/1_337.arc thread=1 sequence=337 channel clone_default: deleting archive log(s) archive log filename=/u02/oradata/clonedb/arch/1_337.arc recid=1 stamp=540710834 media recovery complete Finished recover at 28-OCT-04
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora';
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/28/2004 06:28:26
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
Recovery Manager complete.

HI,
# STBY:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 242208768 bytes
Fixed Size            2227176 bytes
Variable Size          184550424 bytes
Database Buffers       50331648 bytes
Redo Buffers            5099520 bytes
# PRIMARY:
RMAN> CONNECT TARGET sys/oracle@JOHN;
connected to target database: JOHN (DBID=1575580406)
RMAN> CONNECT AUXILIARY sys/oracle@JOHN_DB2;
Until this you did correct. now just in a run block, like
eg
run
allocate channel ....
allocate channel...
duplicate target database for standby from active database;

Java component - ora-01013 error when calling ws.createResultSetSQL

Running Content Server 11.1.1.5 on WLS 10.3.5 in 64bit Linux environment. Same component/code runs great in dev environment, but consistently get this error in production. In production, query runs against view in same schema as system database. I can run the same query in either SQL Developer or SQLPlus and the results return nearly immediate - about 1 second.
The query in the Java component times-out nearly every single time, even when very little load on the system (late at night).
getMessage() returns "!csDbUnableToCreateResultSet
I have already set the default query timeout in config.cfg to 120 seconds.
Any suggestions? Really perplexed on this one!
Thank you, Ken
Here is an example of the Java code used in the call.
{code}package com.example;
import intradoc.common.ExecutionContext;
import intradoc.common.ServiceException;
import intradoc.common.SystemUtils;
import intradoc.data.DataBinder;
import intradoc.data.DataException;
import intradoc.data.DataResultSet;
import intradoc.data.ResultSet;
import intradoc.data.Workspace;
import intradoc.provider.Provider;
import intradoc.provider.Providers;
import intradoc.shared.FilterImplementor;
import intradoc.util.IdcMessage;
public class Test implements FilterImplementor {
public int doFilter(Workspace ws, DataBinder binder, ExecutionContext cxt) throws DataException, ServiceException {
String value = "-1";
String xEMP_NUM ="";
String SQL = "";
String ResultSetName = "XEMPNUMCOUNT";
int rowcount = 0;
DataResultSet result = null;
DataException error = null;
ResultSet temp = null;
Workspace wsTemp = null;
SystemUtils.trace("filterdebug", "Starting doFilter for Test");
xEMP_NUM = binder.getLocal("xEMP_NUM");
xEMP_NUM = (xEMP_NUM == null) ? null : xEMP_NUM.trim();
SystemUtils.trace("filterdebug", "xEMP_NUM=" + xEMP_NUM);
if (xEMP_NUM != null && !xEMP_NUM.equalsIgnoreCase("0") && xEMP_NUM.length() > 0) {
SQL = "select emp_num, emp_lname, emp_mname, emp_fname from emps where emp_num = " + xEMP_NUM.trim();
SystemUtils.trace("filterdebug", "SQL=" + SQL);
if (ws == null) {
SystemUtils.trace("filterdebug", "ws is null, getting ws from call to getSystemWorkspace()");
ws = getSystemWorkspace();
SystemUtils.trace("filterdebug", "try-catch block to get ResultSet from SQL");
try {
SystemUtils.trace("filterdebug", "start: temp = ws.createResultSetSQL(SQL)");
temp = ws.createResultSetSQL(SQL);
SystemUtils.trace("filterdebug", "end: temp = ws.createResultSetSQL(SQL)");
result = new DataResultSet();
result.copy(temp);
rowcount = result.getNumRows();
SystemUtils.trace("filterdebug","rowCount=" + rowcount);
} catch (DataException de) {
error = de;
SystemUtils.trace("filterdebug", "de.getMessage()=" + de.getMessage());
} finally {
// ws.releaseConnection();
if (rowcount > 0){
try {
int fieldCnt = result.getNumFields();
SystemUtils.trace("filterdebug", "fieldCnt=" + fieldCnt);
result.first();
xEMP_NUM = result.getStringValue(0);
binder.putLocal("xEMP_NUM",xEMP_NUM);
String xEMP_LNAME = result.getStringValue(1);
binder.putLocal("xEMP_LNAME",xEMP_LNAME);
String xEMP_MNAME = result.getStringValue(2);
binder.putLocal("xEMP_MNAME",xEMP_MNAME);
String xEMP_FNAME = result.getStringValue(3);
binder.putLocal("xEMP_FNAME",xEMP_FNAME);
} catch (NumberFormatException nfe) {
SystemUtils.trace("filterdebug", "nfe.getMessage()=" + nfe.getMessage());
} else {
SystemUtils.trace("filterdebug", "Throw error since xEMP_NUM is not in the ems table");
throw new ServiceException("Invalid Employee Number provided!");
if (error != null) {
SystemUtils.trace("filterdebug", "Throw error since error condition exists.");
throw error;
SystemUtils.trace("filterdebug", "Ending doFilter for Temp");
return CONTINUE;
public Workspace getSystemWorkspace() {
Workspace workspace = null;
Provider wsProvider = Providers.getProvider("SystemDatabase");
if (wsProvider != null) {
workspace = (Workspace)wsProvider.getProvider();
return workspace;
{code}

From Console Output in the server
>filterdebug/6     01.24 21:42:46.004     IdcServer-6201     Starting doFilter for DCSDEmployeeCheckinValidation
filterdebug/6     01.24 21:42:46.005     IdcServer-6201     xEMP_NUM=2003076
filterdebug/6     01.24 21:42:46.005     IdcServer-6201     SQL=select emp_num, emp_lname, emp_mname, emp_fname, emp_natl_id, emp_stat_cd from dcsdemployees where emp_num = 2003076
filterdebug/6     01.24 21:42:46.005     IdcServer-6201     try-catch block to get ResultSet from SQL
filterdebug/6     01.24 21:42:46.006     IdcServer-6201     start: temp = ws.createResultSetSQL(SQL)
filterdebug/6     01.24 21:44:46.232     IdcServer-6201     de.getMessage()=!csDbUnableToCreateResultSet,select emp_num\, emp_lname\, emp_mname\, emp_fname\, emp_natl_id\, emp_stat_cd from dcsdemployees where emp_num = 2003076!$ORA-01013: user requested cancel of current operation
filterdebug/6     01.24 21:44:46.232     IdcServer-6201     Throw error since xEMP_NUM is not in the dcsdstudents table
services/3     01.24 21:44:46.239     IdcServer-6201     !csUserEventMessage,weblogic,ucmprod.dcsdk12.org!$ intradoc.common.ServiceException: Invalid Employee Number provided! services/3     01.24 21:44:46.239     IdcServer-6201     *ScriptStack CHECKIN_NEW_SUB
services/3     01.24 21:44:46.239     IdcServer-6201     3:doScriptableAction,dDocName=3:doSubService,dDocName=CHECKIN_NEW_SUB,dDocName=3:validateStandard,dDocName=DCS866569
services/3     01.24 21:44:46.239     IdcServer-6201             at org.dcsdk12.ucm.DCSDEmployeeCheckinValidation.doFilter(DCSDEmployeeCheckinValidation.java:112)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.shared.PluginFilters.filterWithAction(PluginFilters.java:114)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.shared.PluginFilters.filter(PluginFilters.java:68)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.DocServiceHandler.validateStandard(DocServiceHandler.java:1167)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
services/3     01.24 21:44:46.239     IdcServer-6201             at java.lang.reflect.Method.invoke(Method.java:597)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:86)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.ClassHelperUtils.executeMethodReportStatus(ClassHelperUtils.java:324)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceHandler.executeAction(ServiceHandler.java:79)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doCodeEx(Service.java:533)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doCode(Service.java:505)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1643)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doAction(Service.java:477)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1458)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doActions(Service.java:472)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.executeSubServiceCode(ServiceRequestImplementor.java:1322)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.executeSubServiceCode(Service.java:3866)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.executeServiceEx(ServiceRequestImplementor.java:1200)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.executeServiceEx(Service.java:3861)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.executeService(Service.java:3845)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doSubService(Service.java:3760)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
services/3     01.24 21:44:46.239     IdcServer-6201             at java.lang.reflect.Method.invoke(Method.java:597)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:86)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.ClassHelperUtils.executeMethodEx(ClassHelperUtils.java:310)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.ClassHelperUtils.executeMethod(ClassHelperUtils.java:295)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doCodeEx(Service.java:550)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doCode(Service.java:505)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1643)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doAction(Service.java:477)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doScriptableAction(Service.java:3807)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
services/3     01.24 21:44:46.239     IdcServer-6201             at java.lang.reflect.Method.invoke(Method.java:597)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:86)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.ClassHelperUtils.executeMethodEx(ClassHelperUtils.java:310)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.common.ClassHelperUtils.executeMethod(ClassHelperUtils.java:295)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doCodeEx(Service.java:550)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doCode(Service.java:505)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1643)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doAction(Service.java:477)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1458)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doActions(Service.java:472)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1391)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.executeActions(Service.java:458)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:737)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.Service.doRequest(Service.java:1890)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.ServiceManager.processCommand(ServiceManager.java:435)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.server.IdcServerThread.processRequest(IdcServerThread.java:265)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.idcwls.IdcServletRequestUtils.doRequest(IdcServletRequestUtils.java:1343)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.idcwls.IdcServletRequestUtils.processFilterEvent(IdcServletRequestUtils.java:1715)
services/3     01.24 21:44:46.239     IdcServer-6201             at intradoc.idcwls.IdcIntegrateWrapper.processFilterEvent(IdcIntegrateWrapper.java:222)
services/3     01.24 21:44:46.239     IdcServer-6201             at sun.reflect.GeneratedMethodAccessor209.invoke(Unknown Source)
services/3     01.24 21:44:46.239     IdcServer-6201             ... 35 more
(internal)/6     01.24 21:44:46.286     IdcServer-6201     File to be removed: /cms/ecm/vault/~temp/1897335874.txt

Run Time error 40002. ORA-01013

I have a run-time error 40002 when running an application (VB5). This is the following message I have when a selection query is executed(with 9 joins):S1T00:[Oracle][ODBC]ORA-01013: user requested cancel of current operation.
The query takes, wheter with ODBC test or Sql+, 5 minutes to be executed. This is too long for a user who is waiting for a result. I was wondering if there are otpions to set, or optimization rules or paramters to set, or if a patch exists for this bug
Thanks for any answer.
null

Your run-time error is probably being generated because the your query timeout is being exceeded. If your query takes 5+ minutes to run, this isn't unexpected.
There aren't any general parameters one can set to "make my queries run faster". There are, however, a number of tools you can use to try to change your query so that it's executed more quickly. The folks on the PL/SQL forum are probably a lot better versed on the art of query optimization than I am, so you may want to ask them for pointers. Alternately, any decent Oracle reference book will probably have a chapter on query optimization.
Justin

ORA-01013 with Oracle ODBC Driver 8.1.6.3

I have a very strange problem occuring with the latest Oracle 8.1.6 Driver. I am able to set up the ODBC connection and it tests correctly. I'll open an Access 97 database and attempt to link to a table in an Oracle 8.1.6 through ODBC. I can connect to the database fine and it brings back a list of the available tables. However, when I select a table and attempt to link to it, I get the following error:
ORA-01013: user requested cancel of current operation.
This behavior also occurs if I try this operation through VB 6.0 code.
Has anyone seen this before or better yet, have an answer as to why it is occurring?
P.S., I'm using MDAC 2.51

As an update, when I turn tracing on, here is the section of the log file that contains the error.
MSACCESS d5-cb ENTER SQLStatisticsW
HSTMT 01861988
WCHAR * 0x00000000 [ -3] <empty string>
SWORD -3
WCHAR * 0x01862528 [ 5] "HQ"
SWORD 5
WCHAR * 0x01862548 [ -3] "AS"
SWORD -3
UWORD 1 <SQL_INDEX_ALL>
UWORD 0 <SQL_QUICK>
MSACCESS d5-cb EXIT SQLStatisticsW with return code -1 (SQL_ERROR)
HSTMT 01861988
WCHAR * 0x00000000 [ -3] <empty string>
SWORD -3
WCHAR * 0x01862528 [ 5] "HQ"
SWORD 5
WCHAR * 0x01862548 [ -3] "AS"
SWORD -3
UWORD 1 <SQL_INDEX_ALL>
UWORD 0 <SQL_QUICK>
DIAG [S1T00] [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
(1013)

FOI error with ORA-01013

Has anyone encountered an error on displaying a Theme based FOI that results in
ORA-01013 user requested cancel of current operation
The FOI in question is displaying the 30 nearest points to where the click was made on the map.
This occurs when there is more than minimal load on the server, so it is so far impossible to replicate in a development environment.
Any suggestion for resolving this would be appreciated.
Thanks!

I forgot to mention the version of Mapviewer: Ver1033p5_B081010

ORA-01013: user requested cancel of current operation Disconnected from Ora

Similar Messages

Maybe you are looking for