Common issue with RMAN while working with NFS mount points (Linux/Solaris).
Reason :
a) The mount table (eg; /etc/mnttab) can be read to check the mount options
b) The NFS mount is mounted with the "hard" option
c) The mount options include rsize>=32768 and wsize>=32768 (in /etc/fstab)
Example 192.168.3.1:/oracle/backup/rman /oracle/backup/rman nfs rsize=32768,wsize=32768,timeo=14,intr,bg,retry=16
d) For RAC environments, where NFS disks are supported, the "noac" mount option is used.
Workaround :
Reason :
Oracle
10G R2 onwards, Oracle checks the options with which a NFS mount is mounted on
the filesystem to ensure that no corruption of the database.
There are no single set of NFS mount options that work across all Oracle platforms
Check :
The exact checks used for an NFS mounted disk vary between platforms but in general the basic checks will include the following checks
There are no single set of NFS mount options that work across all Oracle platforms
Check :
The exact checks used for an NFS mounted disk vary between platforms but in general the basic checks will include the following checks
a) The mount table (eg; /etc/mnttab) can be read to check the mount options
b) The NFS mount is mounted with the "hard" option
c) The mount options include rsize>=32768 and wsize>=32768 (in /etc/fstab)
Example 192.168.3.1:/oracle/backup/rman /oracle/backup/rman nfs rsize=32768,wsize=32768,timeo=14,intr,bg,retry=16
d) For RAC environments, where NFS disks are supported, the "noac" mount option is used.
Workaround :
sql> alter system set
events '10298 trace name context forever, level 32';
or
sql> alter system set
events '10298 trace name context forever, level 32' scope=spfile;
or
Set the following event in the init.ora
event="10298 trace name context forever, level 32"
event="10298 trace name context forever, level 32"
Wonderful blog.. Thanks for sharing informative Post. Its very useful to me.
ReplyDeleteOracle Apps DBA Training in Hyderabad