My Oracle Support Banner

Datapatch failed with error “Queryable inventory could not determine the current opatch status” (Doc ID 2339328.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Standard Edition - Version 12.2.0.1 and later
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Information in this document applies to any platform.

Symptoms

Datapatch failed with error “Queryable inventory could not determine the current opatch status”

From sqlpatch_invocation.log
——————————

C:\Oracle\12.2.0\dbhome\OPatch>datapatch -verbose
SQL Patching tool version 12.2.0.1.0 Production on Fri Nov 3 16:04:02 2017
Copyright (c) 2012, 2017, Oracle. All rights reserved.

Log file for this invocation: C:\Oracle\cfgtoollogs\sqlpatch\sqlpatch_3916_2017_11_03_16_04_02\sqlpatch_invocation.log

Connecting to database…OK
Bootstrapping registry and package to current versions…done

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_3916_2017_11_03_16_04_02\sqlpatch_invocation.log
for the complete error.
Prereq check failed, exiting without installing any patches.

Please refer to MOS Note 1609718.1 and/or the invocation log
C:\Oracle\cfgtoollogs\sqlpatch\sqlpatch_3916_2017_11_03_16_04_02\sqlpatch_invocation.log
for information on how to resolve the above errors.

 

From qopatch_log.log
——————–

KUP-05007: Warning: Intra source concurrency disabled because the preprocessor option is being used.

Field Definitions for table OPATCH_XML_INV
Record format DELIMITED BY NEWLINE
Data in file has same endianness as the platform
Reject rows with all null fields

Fields in Data Source:

XML_INVENTORY CHAR (100000000)
Terminated by “UIJSVTBOEIZBEFFQBL”
Trim whitespace same as SQL Loader
KUP-04095: preprocessor command c:\Oracle\12.2.0\dbhome\QOpatch\qopiprep.bat encountered error “Argument(s) Error… Cannot use file “c:\Oracle\12.2.0\dbhome\rdbms\log\xml_file.xml” to generate XML output.
Specify path/filename and make sure filename doesn”

 



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!


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