Direct NFS Setup

This post shows steps for setting up directNFS for 11.2 and 12.1 (steps are identical). For 11.1 please refer here.
Direct NFS requires a working NFS setup to already exists. Create a NFS setup and mount the NFS on the local server with oracle recommended nfs mount options (refer 359515.1) For this test case (tested with 11.2 and 12.1 both SE, SE2 and EE) nfs mount is as follows

# mount
...
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
192.168.0.104:/opt/backup on /usr/local/ochm/nfsdir type nfs (rw,hard,rsize=32768,wsize=32768,nfsvers=3,nointr,timeo=600,tcp,nolock,actimeo=0,addr=192.168.0.104)

Add an entry to fstab as well

# cat /etc/fstab
...
192.168.0.104:/opt/backup /usr/local/ochm/nfsdir        nfs     rw,hard,rsize=32768,wsize=32768,nfsvers=3,nointr,timeo=600,tcp,nolock,actimeo=0,addr=192.168.0.104 0 0

Test to see if the oracle user has write permission on the nfs mount point by creating dummy files. When the nfs is working without any issues configure the oracle to use direct nfs.
Enable direct nfs by executing the rdbms make with dnfs on.

cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dnfs_on
rm -f /opt/app/oracle/product/12.1.0/std2/rdbms/lib/odm/libnfsodm12.so; \
    cp /opt/app/oracle/product/12.1.0/std2/lib/libnfsodm12.so /opt/app/oracle/product/12.1.0/std2/rdbms/lib/odm/libnfsodm12.so

To disable direct NFS use

make -f ins_rdbms.mk dnfs_off
rm -f  /opt/app/oracle/product/12.1.0/std2/rdbms/lib/odm/libnfsodm12.so

Verify if the oradism is owned by root and has setuid.

# ls -l $ORACLE_HOME/bin/oradism
-rwsr-x--- 1 root oinstall 71758 Sep 17  2011 /opt/app/oracle/product/12.1.0/std2/bin/oradism

If oradism has wrong permission or ownership correct it as follows

# chown root:oinstall $ORACLE_HOME/bin/oradism
# chmod 4755 $ORACLE_HOME/bin/oradism

Direct NFS searches for mount entries in following files in the given order

1.$ORACLE_HOME/dbs/oranfstab
2. /etc/oranfstab
3. /etc/mtab

In this case an oranfstab file is created as follows

cat oranfstab
server: hpc1nfsmount
local: 192.168.0.66
path:   192.168.0.104
export: /opt/backup mount: /usr/local/ochm/nfsdir

local: 192.168.0.66 is the IP of the local server where the database is running. path: 192.168.0.104 is the IP of the server which provides the NFS storage (i.e. NFS server). export: /opt/backup is the export location on the NFS server. mount: /usr/local/ochm/nfsdir is the mount point local server.

Once the dnfs is enabled start the database. If the dnfs is in use the alert log will have the following line

Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 3.0

However there won't be any dnfs related info available on the views

SQL> select * from v$dnfs_servers;

no rows selected

SQL> select * from v$dnfs_files;

no rows selected

Create a tablespace using the nfs location.

SQL> create tablespace nfstbs datafile '/usr/local/ochm/nfsdir/nfs.dbf'  size 10m;

When the tablespace is being created the alert log will show the dnfs being used

Fri Oct 09 11:16:01 2015
create tablespace nfstbs datafile '/usr/local/ochm/nfsdir/nfs.dbf'  size 10m
Fri Oct 09 11:16:02 2015
Direct NFS: channel id [0] path [192.168.0.104] to filer [192.168.0.104] via local [] is UP
Completed: create tablespace nfstbs datafile '/usr/local/ochm/nfsdir/nfs.dbf'  size 10m

Once the tablespace is created the dnfs views will show the relevant information

SQL> select * from v$dnfs_servers;

        ID SVRNAME              DIRNAME                           MNTPORT    NFSPORT      WTMAX      RTMAX
---------- -------------------- ------------------------------ ---------- ---------- ---------- ----------
         1 192.168.0.104        /opt/backup                         56904       2049    1048576    1048576
   
SQL> select * from v$dnfs_files;

FILENAME                         FILESIZE       PNUM     SVR_ID
------------------------------ ---------- ---------- ----------
/usr/local/ochm/nfsdir/nfs.dbf   10493952         10          1

The same servers and setup was used to test the direct nfs on 11.1 SE as well. The dNFS ODM version is lower than 11.2 and 12.1

Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 2.0

The NFS version was v3

# nfsstat | grep nfs
Server nfs v3:
Client nfs v3:

However this did not succeed creating tablespaces in the 11.1 even after mounting the nfs with a lower version

192.168.0.104:/opt/backup on /usr/local/ochm/nfsdir type nfs (rw,hard,rsize=32768,wsize=32768,nfsvers=2,nointr,timeo=600,tcp,nolock,actimeo=0,addr=192.168.0.104)

Related Post
RMAN Backups on NFS

Parameterizing Backup Tags

At times it may be necessary to customize the back tag value. This could be achieved in two ways.
First method is used when a backups are run using a separate rman backup script file, which is used by the session invoking the rman. In this case the customized backup tags could be passed with the "USING" clause. Below is a simple rman backup script which takes a full database backup and archive log

cat backup.rmn
run {
backup database tag='&1' plus archivelog tag='&2';
delete noprompt obsolete;
}

Tags has been parameterized with the use of '&n'. Values for these are passed via the shell script that invokes rman

cat backup.sh
export ORACLE_SID=racse11g2
...
today_date=$(date +%F)
arctag=arch_bkp_$(date +%Y_%m_%d)
bkptag=full_bkp_$(date +%Y_%m_%d)
logfile=$ORACLE_SID"_"$today_date".log"
rman target / @/home/oracle/cronjobs/backup.rmn log /home/oracle/cronjobs/logs/$logfile using $bkptag $arctag

Result of this is customized tags for each days backup.

List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
79      B  A  A DISK        06-OCT-15       1       1       NO         ARCH_BKP_2015_10_06
80      B  F  A DISK        06-OCT-15       1       1       NO         FULL_BKP_2015_10_06
81      B  A  A DISK        06-OCT-15       1       1       NO         ARCH_BKP_2015_10_06
...
179     B  A  A DISK        07-OCT-15       1       1       NO         ARCH_BKP_2015_10_07
180     B  F  A DISK        07-OCT-15       1       1       NO         FULL_BKP_2015_10_07
181     B  A  A DISK        07-OCT-15       1       1       NO         ARCH_BKP_2015_10_07

Second method is used when rman is invoked within a shell script. In this case customized tag is appended to a string

cat backupdisk.sh
export ORACLE_SID=racse11g1
...
logfile="disk_"$ORACLE_SID"_"$today_date".log"
tag=$(date +%Y_%m_%d)

rman target / log /home/oracle/cronjobs/logs/$logfile <<EOF
run
{
backup  database tag = 'full_disk_$tag' format '/backup/full_bkp_%d_%T_%U'  plus archivelog tag = 'full_arc_disk_$tag' format '/backup/full_arc_%d_%T_%U';
delete noprompt obsolete;
}
exit;
EOF

This will create customized tags as follows

List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
83      B  A  A DISK        06-OCT-15       1       1       NO         FULL_ARC_DISK_2015_10_06
84      B  F  A DISK        06-OCT-15       1       1       NO         FULL_DISK_2015_10_06
85      B  A  A DISK        06-OCT-15       1       1       NO         FULL_ARC_DISK_2015_10_06
...
183     B  A  A DISK        07-OCT-15       1       1       NO         FULL_ARC_DISK_2015_10_07
184     B  F  A DISK        07-OCT-15       1       1       NO         FULL_DISK_2015_10_07
185     B  A  A DISK        07-OCT-15       1       1       NO         FULL_ARC_DISK_2015_10_07