PRVG-2029 : Octal permissions of file “filename” are inconsistent across nodes

Following entries were logged in CRS/GRID alert.log

2016-10-23 16:24:49.048 [SRVM(4849748)]CRS-10051: CVU found following errors with Clusterware setup :
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_asym.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_base.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_base_non_fips.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_ecc.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_ecc_accel_fips.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_ecc_accel_non_fips.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libccme_ecc_non_fips.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libcryptocme.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libldapjclnt12.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]
PRVG-2029 : Octal permissions of file “/u01/product/12.1.0.2/grid/lib/libowm2.so” are inconsistent across nodes. [Found = “{0644=[db01], 0755=[db02]}”]

This would typically happen, when we are doing opatch operation. One of the node is patched and another one is in progress or not patched. Some file permissions may change as part of PSU patching.

Check patch levels using opatch lsinventory. In the last section “Patching Level” column would show current state.

Patch level status of Cluster nodes :

Patching Level Nodes
————– —–
0 db01
1505651481 db02

This means db02 is patched and on higher level. We can ignore these messages, if they are logged when patching is in progress.

But if they are logged post patching i.e. “Patching Level” are same, we should contact Oracle support.

Advertisements
This entry was posted in Oracle OPatch and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s