Datapatch failed “LsInventorySession failed: Unable to create patchObject”
(Doc ID 2404955.1)
Last updated on FEBRUARY 13, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
While executing datapatch the following message is displayed :
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
/oracle/v12201/cfgtoollogs/sqlpatch/sqlpatch_55366_2018_04_24_08_24_57/sqlpatch_invocation.log
for the complete error.
Prereq check failed, exiting without installing any patches.
$ORACLE_HOME/QOpatch/qopatch_log.log has following messages
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 /oracle/v12201/QOpatch/qopiprep.bat encountered error “Inventory
load failed… OPatch cannot load inventory for the given Oracle Home.
LsInventorySession failed: Unable to create patchObject
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 |