My Oracle Support Banner

EM 13c: Database Cloning on Windows Failing with: Queryable Inventory Could not Determine the Current Opatch Status. (Doc ID 2757719.1)

Last updated on MAY 03, 2021

Applies to:

Enterprise Manager for Oracle Database - Version 13.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Trying to close a 12.2 DB on the same Windows server (different home), will fail with this error in the Deployment Procedure step output:

Queryable inventory could not determine the current opatch status.
Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual'
and/or check the invocation log
C:\Oracle\cfgtoollogs\sqlpatch\sqlpatch_3744_2020_12_29_11_54_55\sqlpatch_invocation.log
for the complete error.

Prereq check failed, exiting without installing any patches.

The same error can be seen by running this command in the new (cloned) database:

Checking the alert log file on the cloned database, this error will be seen:

2021-01-12T13:33:13.232677+02:00
Unable to obtain current patch information due to error: 20001, ORA-20001: Latest xml inventory is not loaded into table
ORA-06512: at "SYS.DBMS_QOPATCH", line 777
ORA-06512: at "SYS.DBMS_QOPATCH", line 864
ORA-06512: at "SYS.DBMS_QOPATCH", line 2222
ORA-06512: at "SYS.DBMS_QOPATCH", line 740
ORA-06512: at "SYS.DBMS_QOPATCH", line 2247

===========================================================
Dumping current patch information
===========================================================
Unable to obtain current patch information due to error: 20001
===========================================================

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.