OID And EM Agent Instances Unable To Start After Upgrading To April 2015 PSU (EECS 2.0.6.2.1) Or Later Versions

(Doc ID 2071226.1)

Last updated on APRIL 03, 2017

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.1 and later
Enterprise Manager Base Platform - Version 12.1.0.5.0 to 12.1.0.5.0 [Release 12.1]
Linux x86-64
Oracle Virtual Server x86-64

Symptoms

In Exalogic racks running Linux on bare metal (physical) or running in a Virtualized configuration, OID and EM agent instances (installed in compute nodes on physical and guest vServers on virtual) are unable to start after upgrading to April 2015 PSU (EECS 2.0.6.2.1) or later PSU versions.

OID instances do not start after upgrading due to insufficient permissions on "oiddispd". Both prior to and after applying the PSU, the "oiddispd" file is observed to have permissions of 4710 (-rws--x---). Updates in the PSU require additional permissions for the daemon process to start.

EM agents are unable to access the "nmo" files inside the <AGENT_HOME>/bin directory following the PSU upgrade. Both prior to and after applying the PSU, the "nmo" files inside the <AGENT_HOME>/bin are observed to have permissions of 4710 (-rws--x---). Updates in the PSU require additional permissions to enable access.

Changes

Upgrade to Exalogic Virtual April 2015 PSU (EECS 2.0.6.2.1) or later PSU versions.

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