![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 781349.1 : ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
In this Document
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.7 [Release 10.1 to 11.1]Oracle ZFS Storage ZS3-2 Information in this document applies to any platform. ***Checked for relevance on 14-Mar-2014*** SymptomsYou are transferring your database/installation to a NetApps NFS mount point. The following error occurs on database startup: ORA-01503: CREATE CONTROLFILE failed The current mount point is mounted as: rw,bg,rsize=32768,wsize=32768,hard,vers=3,nointr,timeo=600,proto=tcp,suid 0 0 CauseThe correct mount point options are being used but they are not in the correct order per oracle docs on correctly mounting NFS mounts for oracle software. The correct setting should be: rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,proto=tcp,suid NOTE: the location of the parameter 'hard' NOTE: As per <Bug 11812928>, the 'intr' & 'nointr' are deprecated in UEK kernels, as well as Oracle Linux 6. It is harmless to still include it, you will get a notice.. SolutionMount the NFS mount point with the recommended options in the exact order specified in oracle documentation. NOTE: if settings revert back to original settings after remount, check auto-mounter options/settings. For more info on auto-mounter, please contact the OS vendor. Additional Resources Still have questions? Use the above community to search for similar discussions or start a new discussion on this subject. References<NOTE:359515.1> - Mount Options for Oracle files when used with NFS on NAS devicesAttachments This solution has no attachment |
||||||||||||||||||
|