Bug 27695334 - CVU Fails To Check Maximum Locked Memory With Error PRVE-0059 (Doc ID 27695334.8)

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

10/26/2020 Document 27695334.

8
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Bug 27695334 - CVU Fails to Check "Maximum locked memory" With Error PRVE-0059 (Doc
ID 27695334.8)
Modified: Jan 16, 2020 Type: PATCH

Bug 27695334 CVU Fails to Check "Maximum locked memory" With Error PRVE-0059

This note gives a brief overview of bug 27695334.


The content was last updated on: 15-JAN-2020
Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (OPSM)


Range of versions believed to be affected Versions BELOW 19.1

18.1.0
Versions confirmed as being affected 12.2.0.1 (Base Release)
12.1.0.2 (Server Patch Set)

Platforms affected Generic (all / most platforms affected)

Fixed:

19.1.0
OCW Release Update 18.6.0.0.190416 (Apr 2019)
OCW Release Update 12.2.0.1.200114 (Jan 2020)
12.2.0.1.190416 (Apr 2019) OCW Apr2019 Release Update
(OCW RU)
The fix for 27695334 is first
12.2.0.1.200114 (Jan 2020) OCW Release Update
included in
Revision(OCW RUR)
12.2.0.1.200114 (Jan 2020) OCW Release Update
Revision(OCW RUR)
12.1.0.2.190416 (Apr 2019) Grid Infrastructure Patch Set
Update (GI PSU)

Interim patches may be available for earlier versions - click here to check.

Symptoms: Related To:

Error May Occur


Cluster Ready Services / Parallel Server Management
PRVE-0059

Description
CVU(Cluster Verification utility) may fail checking "Maximum locked memory".

Rediscovery Notes

1. Execute CVU like:

cluvfy stage -pre dbinst -allnodes

2. The tool reports the errors:

Verifying Maximum locked memory check ...FAILED

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=ic80cmy4c_4&id=27695334.8 1/2
10/26/2020 Document 27695334.8
<MACHINE>: PRVE-0059 : no default entry or entry specific to user "<USER>" was
found in the configuration file "/etc/security/limits.d/*.conf"
when checking the maximum locked memory limit on node "<MACHINE>"

3. But the limit is set at /etc/security/limits.conf

Workaround

None

Please note: The above is a summary description only. Actual symptoms can vary. Matching to
any symptoms here does not confirm that you are encountering this problem. For questions
about this bug please consult Oracle Support.

References

Bug:27695334 (This link will only work for PUBLISHED bugs)


Note:245840.1 Information on the sections in this article

REFERENCES

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocContentDisplay?_adf.ctrl-state=ic80cmy4c_4&id=27695334.8 2/2

You might also like