• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

ORA-01013: user requested cancel of current operation

 
suresh sargar
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"ORA-01013: user requested cancel of current operation
" encountered while processing query to database .
Query: select a.tablespace_name, file_name, round(bytes/1048576,2), round(maxbytes/1048576,2), round((user_bytes - NVL(free_bytes,0))/1048576,2), autoextensible from dba_data_files a, dba_tablespaces b, (select file_id, sum(bytes) free_bytes from sys.dba_free_space group by file_id) c where contents = 'PERMANENT' and b.status = 'ONLINE' and a.tablespace_name = b.tablespace_name and bytes is not NULL and maxbytes is not NULL and user_bytes is not NULL and c.file_id (+)= a.file_id order by 1



i got this error to particular oracle database.this query works with terabyes of database. but certain databases giving above error.

i used this query with jdbcdriver in java. on SQL prompt of same machine query works fine.

please give me suggesion..what the root cause for failing through jdbc ?
 
Omar Al Kababji
Ranch Hand
Posts: 357
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ORA-01013 is known as an "information" error. It is letting you know that the operation has been cancelled by either:

* caused by the user (pressing CTRL-C or a different method like front-end application),
* caused by a response to congruent errors OR
* the result of timeouts.

Resolving ORA-01013 is dependant upon the reason for the operation to terminated. If ORA-01013 signifies that the operation has been explicitly shut down by the user, the error in simply informational and there is nothing that can be done, other than proceeding to the next operation.

ORA-01013 may also be caused by other errors, in which proceeding errors should be resolved.

The most common cause of ORA-01013 is timeouts. Timeouts can be a little more tricky to identify because they may not be specifically reported in connection with ORA-01013. . If a timeout is causing your ORA-01013 error in a SQL pass-through query, the properties in the timeout parameter should be altered to a higher value.
 
Bauke Scholtz
Ranch Hand
Posts: 2458
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It would be so kind if you mentioned the source of the above information: http://www.dba-oracle.com/t_ora_01013_user_requested_cancel_of_current_operation.htm
 
Omar Al Kababji
Ranch Hand
Posts: 357
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ooops sorry, next time ;)
 
suresh sargar
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
yes i agreed this is related to timeout. but even i increase time interval 15 min or 30 min .then still this error occours..

on SQL prompt query takes hardly less than 5 seconds... there is only one connection with jdbc..
 
Tharuka Sandaruwan
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Another Database connection has updated the same record, but not committed. Therefore you have to wait. This might be the reason.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic