 Posted 6/11/2010 11:48:57 AM
|
|
|
|
| ORA-01013 user requested cancel of current operation 01013, 00000, "user requested cancel of current operation"
// *Cause:
// *Action:
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.
|
|
|
Posted 6/11/2010 11:50:15 AM
|
|
|
|
| This ora error is an 'information' error from Oracle, indicating that the current operation has been cancelled. This error will be generated if the user cancels the current operation. It can also be generated in response to other errors (such as timeouts). If this error is generated in response to the user cancelling their current operation then the message is correct and no remedial action is required. (Although it may be pertinent to understand why the user cancelled the operation.) If the error is preceded by any other error then it is likely that it is the preceding error which needs to be investigated. Timeouts (whether explicitly or implicitly specified or reported) are a frequent cause of ORA-01013. This can be difficult to identify because a timeout may not be explicitly reported as part of the error. - The Oracle 8 ODBC driver implements a timeout, the previous Oracle 7 ODBC driver did not.
- SQL*Net also implements a timeout. This is specified via the '
sqlnet.expire_time' parameter in the 'sqlnet.ora' file.
|
|
|
Posted 6/11/2010 11:52:13 AM
|
|
|
|
| If I create a query, join the two tables together and run it, I get this ora error: ORA-01013 user requested cancel of current operation (#1013). I have even taken a database connection which I know works fine, taken out all the linked tables and queries and added my 2 tables and query. When I try to run my query again and it still doesn't work. I get the same error. Fixed: I was getting the ORA-01013 error because too many records were coming back. I have heard that there is a setting in Access that limits how many records it brings back. I am not sure of where it is yet but I will post it once i find out in case anyone else has this problem.
|
|
|
Posted 6/11/2010 12:04:51 PM
|
|
|
|
| VB also has a similar time out setting. When you are getting the ORA-01013 ora error in vb it means your VB app is connecting just fine to Oracle, but when the query is run it get's cancelled midway. Most likely it might just be a timeout. ORA-01013 ora error is most commonly cause by timeouts for your query so maybe your query is just timing out. I would suggest trying out the queries directly on the database first in SQL Plus and see what happens. If all ok , then check the VB app settings. Hope that helps.
|
|
|
|