a. query error, ORA-01013: user requested cancel of current operation
This is an error seen for a Database monitor running against an Oracle database. Change the value of the timeout for the monitor. Either increase the value or set the value to 0. If you choose to set the value to 0, be careful it may cause monitors to skip.
b. But in Oracle 8i Document --
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.
If Item a. is correct, where could I find the parameter of Timout value for the monitor to setup. Our program is using nohup or corntab to
run cgi program which connect Oracle DB for indexing some columns of a large tables.
Oracle version 8.x servers seem to have a bug which manifests itself as occasional "ORA-01013 - user requested cancel of current operation" errors. This error (ORA-01013) is normally produced when one of the following occurs: 1) The user presses the Ctrl-C key (actually, the process receives a SIGINT) 2) The application (Appx) calls the OCIBreak() function to cancel an operation. Neither of these is happening - Oracle considers this a bug. To try to recover from this problem, the Appx/Oracle interface has been modified to retry a query operation if an ORA-01013 is encounterd. You can control the number of retries by setting the APPX CANCEL RETRIES environment variable to a number greater than 0. Important note - the default is 0 meaning that Appx will NOT retry queries which produced an ORA-01013 error. You must set APPX CANCEL RETRIES to a number greater than zero in order to force Appx to retry failed queries. (#5969)