My Oracle Support Banner

Exadata Compute Node: Post ESS image upgrade to 19.3.4, PATH variable is missing /usr/local/bin directory (Doc ID 2685353.1)

Last updated on JULY 27, 2020

Applies to:

Oracle Exadata Storage Server Software - Version 19.3.0.0.0 to 19.3.9.0.0 [Release 12.2]
Information in this document applies to any platform.

Symptoms

+ Server upgraded to 19.3.4.0.0.200130

[root@node1 ~]# imageinfo

-------------
Kernel version: 4.14.35-1902.9.2.el7uek.x86_64 #2 SMP Mon Dec 23 13:39:16 PST 2019 x86_64
Image kernel version: 4.14.35-1902.9.2.el7uek
Image version: 19.3.4.0.0.200130
Image activated: 2020-04-07 01:28:14 +1000
Image status: success
Node type: COMPUTE
System partition on device: /dev/mapper/VGExaDb-LVDbSys1

-------------

+ On problem node (problemNode) Sessions spawned using sudo command as below missing "/usr/local/bin" in PATH variable:

-------------
$ sudo su oracle
$ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin
$

$ sudo su grid
$ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin
$
-------------

+ But, on a GOOD node (goodNode), shown below, also running at image and kernel level as bad node, PATH variable includes "/usr/local/bin"

--------------
$ sudo su oracle
$ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
$

$ sudo su grid
$ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin
$
---------------

+ In addition, another node, running different ESS image and kernel (ESS 18.1.9/OL6) also exhibiting same behavior as bad node.

Changes

+ Exadata compute node ESS image upgraded to 19.3.4.0.0.200130.
+ But, looking at symptoms above, patching is not likely to have introduced issue.

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.