

My main reason for a device was to save energy, however 2x 2 drive nas's = more than a 80+% psu on a celeron system. I tested many NAS's devices and only got a maximum of 10Mb/s on a gigabit port, and that was rare, typically it was around 3-4. This is interesting because the EXAMPLE1 instance can see NFS files mounted by ASM.I have been using freenas on a spare machine with 4x 1TB hard drives (2 raid 1's, so 2TB usable). The EXAMPLE database now successfully uses DirectNFS as shown by the alert log, and the contents of v$dnfs_servers: ID SVRNAME DIRNAME MNTPORT NFSPORT WTMAX RTMAXġ freenas-nas /mnt/PENRITH/ASMDATA 623 2049 32768 32768Ģ freenas /mnt/PENRITH/NFSDATA 623 2049 32768 32768 The initialization parameter was changed as follow: alter system set filesystemio_options="directIO" scope=spfile The $ORACLE_HOME/dbs/oranfstab has been changed to: server: freenas V$dnfs_channels shows: PNUM SVRNAME PATH CH_ID SVR_ID SENDS RECVS PINGS V$dnfs_files shows: FILENAME FILESIZE PNUM SVR_ID V$dnfs_servers shows: ID SVRNAME DIRNAME MNTPORT NFSPORT WTMAX RTMAXġ freenas /mnt/PENRITH/ASMDATA 623 2049 32768 32768 Later on, there is: Direct NFS: mount complete dir /mnt/PENRITH/ASMDATA on freenas path 192.168.2.1 mntport 623 nfsport 2049 I also corrected the $ORACLE_HOME/dbs/oranfstab as follows: server: freenasĪfter restarting ASM, I see the following message in the +ASM1 alert log: Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 2.0 The following is added to the pfile, $ORACE_HOME/dbs/init+ASM1.ora,: FILESYSTEMIO_OPTIONS = directIO The actual parameter is FILESYSTEMIO_OPTIONS. So ensure ALL the places where are located your database files (including pfile/spfile, logs.) are configured to accept Direct IO. There is no way to only enable direct IO for certain files and exclude others. The DNFS Guide says to enable the init.ora param filesystem_io to enable direct I/O support.ĭoing this, all DB access to all files will be via DIO. Step by Step - Configure Direct NFS Client (DNFS) on Linux (Doc ID 762374.1) says that: P>I created a tablespace called NFSTEST with a datafile on /u08, and there are still no rows in the V$DNFS_* views. sudo su -Ĭat >/etc/fstab dbs]$ cd dbs]$ cat >oranfstab server: freenas-nas Update the /etc/fstab to allow the mounting of the ZFS Dataset ( /mnt/PENRITH/NFSDATA) as /u08. Create Mount Point on PENRITH1Ĭreate the /u08 directory on PENRITH1: sudo su. I also created a NFS Share for /mnt/PENRITH/NFSDATA for access only by the 192.168.2.0/24 network and having a Maproot User of root. Using the FreeNAS Web Gui at, I created a ZFS dataset called NFSDATA which is 1GB in size, and is owned by asm:asmdba. I plan to practice to set up a data file on NFS. One of the OCM 11G objectives to use DirectNFS driver. Step by Step - Configure Direct NFS Client (DNFS) on Linux (Doc ID 762374.1). Enabling Direct NFS Client Oracle Disk Manager Control of NFS.
