My Oracle Support Banner

Error Encountered: XMLParseException Missing '=' Attribute While Running OPatch Prereq CheckCommand (Doc ID 3042003.1)

Last updated on AUGUST 16, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.17.0.0.0 and later
Information in this document applies to any platform.

Symptoms

 

There is a requirement to apply an older DB RU version, specifically Patch 19.22.0.0.240116. However, while running the following command: $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./, the following error was encountered

 

Checking Patch Conflict

Oracle Interim Patch Installer version 12.2.0.1.43

Copyright (c) 2024, Oracle Corporation. All rights reserved.

PREREQ session

Oracle Home : /u01/app/ora/prod/19.0.0.0

Central Inventory : /u01/app/ora/oraInventory

from : /u01/app/ora/prod/19.0.0.0/oraInst.loc

OPatch version : 12.2.0.1.43

OUI version : 12.2.0.7.0

Log file location : /u01/app/ora/prod/19.0.0.0/cfgtoollogs/opatch/opatch2024-06-01_33-22-11AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Interim Patch metadata parsing failure... 'Unable to parse the xml file.'

Prereq "checkConflictAgainstOHWithDetail" is not executed.

The details are:

Unable to create Patch Object.

Exception occured : Unexpected error :

oracle.xml.parser.v2.XMLParseException; systemId: file:/orasoft/Linux_i386_64/rdbms/B19.0.0.0/RU19.22.0.0.240116/35943157/etc/config/inventory.xml; lineNumber: 5836; columnNumber: 77; '=' missing in attribute.

OPatch failed with error code 2

OPATCH Conflict Verification is Success.

 

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


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