OPatch apply or rollback fails with com.oracle.cie.gdr.libraries.LibraryException: com.oracle.cie.gdr.utils.GdrException: Failed to apply xml diff to component definition error in WebLogic PSU (Doc ID 2088228.1)

Last updated on JULY 30, 2017

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

OPatch fails with the following errors while applying any WebLogic PSU (For Example: 12.1.3.0.5 (<Patch 21370953>) :

Error during Update inventory for apply phase ] Detail: OUI-67073:OPatch failed: ApplySession failed in system modification phase... 'ApplySession::apply failed: Check if library regeneration is needed with error message: com.oracle.cie.gdr.libraries.LibraryException: com.oracle.cie.gdr.utils.GdrException: Failed to apply xml diff to component definition /oracle/Middleware/Oracle_Home/inventory/Components/oracle.wls.libraries/12.1.3.0.0/compDef.xml'

Instead of applying the new PSU to override the old PSU, even if we try to rollback previous WLS PSU patches (For Example: <Patch 20223202> manually we see the following errors :

[ Error during Update inventory for rollback Phase]. Detail: RollbackSession failed: RollbackSession failed in system modification phase... 'Check if library regeneration is needed with error message: com.oracle.cie.gdr.libraries.LibraryException: com.oracle.cie.gdr.utils.GdrException: Failed to apply xml diff to component definition /oracle/Middleware/Oracle_Home/inventory/Components/oracle.wls.libraries/12.1.3.0.0/compDef.xml'

The above sample errors for a WLS 12.1.3 PSU but the issue can be seen in older WLS PSU version 12.1.2 or newer versions 12.2.1, 12.2.1.1, 12.2.1.2 or upcoming releases.

While we saw the issue first in WLS PSU 12.1.3 PSU but issues have been reported in later WLS versions too. So, this document and its workaround is applicable to customers on any of the above versions.

Changes

As of now, the issue can't be categorized as a product Bug even if multiple Bugs were filed because this issue is not reproducible in any environment in house and is mostly because of a corrupted inventory in the customer's environment. This happens on all versions for the unknown root cause the bugs provide and has only been reproducible by customers.

Cause

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 hundreds of Community platforms