Datapatch errors at "SYS.DBMS_QOPATCH"
(Doc ID 1599479.1)
Last updated on MARCH 23, 2019
Applies to:Oracle Database - Standard Edition - Version 22.214.171.124 to 126.96.36.199 [Release 12.1]
Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
The following list of errors could be encountered when datapatch is run to complete post-patch SQL actions:
ORA-20001 : Latest xml inventory is not loaded into table.
ORA-20002 : Directory creation failed.
ORA-20003 : Configuration of a job on a node failed.
ORA-20004 : Job configuration failed as node is inactive.
ORA-20005 : Job is not configured with given node, instance name.
ORA-20006 : Number of RAC active instances and opatch jobs configured are not same.
ORA-20007 : Job configuration failed as node and instance is not active.
ORA-20008 : Timed out, Job execution time is more than 120Secs.
ORA-20009 : Job execution failed.
ORA-20010 : Node is inactive and job cann't be executed.
ORA-20011 : Job name is NULL and inventory cann't be loaded.
ORA-20012 : Job_queue_processes set to zero and Inventory can not be loaded.
ORA-20013 : DBMS_QOPATCH ran mostly in non install area
datapatch is executed to perform post install steps
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Workaround 1: Apply the patch using the -force option|
|For bundle patches (i.e. PSU)|
|For non-bundle patches|
|Workaround 2: Manually apply / rollback the patch - 220.127.116.11 only|
|Workaround 3: Manually apply / rollback the patch - 18.104.22.168 and later|