Support Article
Message: ORA-01013: user requested cancel of current operation
SA-12220
Summary
Message: ORA-01013: user requested cancel of current operation is observed.
Error Messages
Message: ORA-01013: user requested cancel of current operation.
Steps to Reproduce
Not Applicable
Root Cause
The root cause of this problem is defect/misconfiguration in the operating environment.
The primary key on table pr_sys_ruleset_index, a table involved in managing the application ruleset cache, was missing.
Without this index access to the cache is slowed and duplicates are allowed to be added.
The SQL causing the problem is as follows:
WITH app_rulesets_pc0
...
FROM PRPCRULES.pr_sys_ruleset_index "i" WHERE "i".pzRuleSetListHash = ?
...
INNER JOIN resolved_rules_pc0 "resolved_rules_pc0" ON ("PC0".pzInsKey = "resolved_rules_pc0".pzInsKey) INNER JOIN PRPCRULES.pr_index_warnings "W" ON ( ( "PC0".PZINSKEY = "W".PXREFERENCINGRULEINSKEY ) AND "PC0".PXOBJCLASS = ? AND "W".PXOBJCLASS = ? ) WHERE ( "W".PXWARNINGCREATEOPERATOR = ? AND "W".PXWARNINGCREATEDTIME BETWEEN ? AND ? AND "PC0".PYRULESET NOT LIKE ? ) GROUP BY "W".PXWARNINGSEVERITY ORDER BY 1 ASC
The above SQL has been edited for clarity. Use this to identify whether you are experiencing the same issue.
If it is determined to be the same issue using the SQL signature above as a reference, then review whether the primary key index is in place on table pr_sys_ruleset_index .
Resolution
This issue is resolved through the following local-change:
Add the primary key index.
ALTER TABLE <RULES_SCHEMA>.pr_sys_ruleset_index
ADD CONSTRAINT pr_sys_ruleset_index_PK PRIMARY KEY
(
pzInsKey
)
ADD CONSTRAINT pr_sys_ruleset_index_PK PRIMARY KEY
(
pzInsKey
)
Published July 22, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.