NetApp: Using 'nolock' NFS Mount Option with non-RAC Systems Results in Database Corruption
(Doc ID 430920.1)
Last updated on FEBRUARY 14, 2022
Applies to:
Linux OS - Version 2.4.9 to 2.6.18-128Oracle Cloud Infrastructure - Version N/A and later
Linux x86
Linux x86-64
Linux Itanium
Linux Kernel - Version: 2.4.9 to 2.6.18-128.EL5
Symptoms
You are using NFS for datafile storage, without Real Application Clusters (RAC), and the mount point with the datafiles is using the 'nolock' NFS mount option. Then 2 nodes accidentally open the same database. Here are some symptoms you might see:
1) Database detects the other node, and fails during mount:
and you used the nolock NFS mount option to workaround the errors.
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 |
| How to Clear Stuck NFS Locks on NetApp Filer(s) |