Essbase: OPatch failed with error code 55 - OPatch was not able to find the Middleware Home's directory "/essbase/Middleware/utils" to configure Oracle Configuration Manager (OCM)" (Doc ID 2876521.1)

Last updated on JUNE 09, 2023

Applies to:

Hyperion Essbase - Version 11.1.2.4.000 and later
Information in this document applies to any platform.

Symptoms

While applying the Essbase Server latest patch, the following error occurs -

[Error during Patch conflict detection for apply patch Phase]. Detail: OPatch failed: ApplySession failed but Oracle Home has not been modified.
OPatch was not able to find the Middleware Home's directory "/opt/essbase/Middleware/utils" to configure OCM.
System is intact, OPatch will not restore the system

Recommended actions : There are conflicts between the incoming patch and the already-installed patched. Please see the log file for details.

OPatch failed with error code 55

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

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

Essbase: OPatch failed with error code 55 - OPatch was not able to find the Middleware Home's directory "/essbase/Middleware/utils" to configure Oracle Configuration Manager (OCM)" (Doc ID 2876521.1)

Applies to:

Symptoms

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!