Oracle Database / Sessions, Locks & Transactions
ORA-01013: distinguish user cancellation from the cause of slowness
A cancelled operation may be reported after a user action, driver timeout or application cancellation. The cancellation message does not explain why execution took too long.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT sid, serial#, sql_id, event, module, action FROM v$session WHERE username = 'APP_USER';Read the result
A surviving session may show its current or subsequent activity rather than the cancelled statement. Correlate SQL ID and timestamp with client evidence.
Resolve and verify
Identify the cancellation source and original execution duration. Investigate the statement's waits or plan separately and make transaction cleanup explicit in the application.
Operational precautions
Do not simply disable client timeouts or retry updates without checking transaction outcome.