Deploying Oracle Direct NFS for Oracle AI Database
Complete these procedures to use file system storage for Oracle AI Database.
If you plan to place storage on Network File System (NFS) protocol devices, then Oracle recommends that you use Oracle Direct NFS (dNFS) to take advantage of performance optimizations built into the Oracle Direct NFS client.
For optimal database organization and performance, Oracle recommends that you install data files and the Oracle AI Database software in different disks.
Related Topics:
Configuring NFS Buffer Size Parameters for Oracle AI Database
Set the values for the NFS buffer size parameters rsize and wsize to at least 32768.
For example, to use rsize and wsize buffer settings with the value 32768 for an Oracle AI Database data files mount point, set mount point parameters to values similar to the following:
nfs_server:/vol/DATA/oradata /home/oracle/netapp nfs\
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600
Direct NFS Client issues writes at wtmax granularity to the NFS server.
Related Topics
Checking TCP Network Protocol Buffer for Direct NFS Client
Check your TCP network buffer size to ensure that it is adequate for the speed of your servers.
By default, the network buffer size is set to 1 MB for TCP, and 2 MB for UDP. The TCP buffer size can set a limit on file transfers, which can negatively affect performance for Direct NFS Client users.
To check the current TCP buffer size, enter the following command:
# sysctl -a |grep -e net.ipv4.tcp_[rw]mem
The output of this command is similar to the following:
net.ipv4.tcp_rmem = 4096 87380 1056768
net.ipv4.tcp_wmem = 4096 16384 1056768
Oracle recommends that you set the value based on the link speed of your servers. For example, perform the following steps:
As
root, use a text editor to open/etc/sysctl.conf, and add or change the following:net.ipv4.tcp_rmem = 4096 87380 4194304 net.ipv4.tcp_wmem = 4096 16384 4194304Apply your changes by running the following command:
# sysctl -pRestart the network:
# /etc/rc.d/init.d/network restart
Creating an oranfstab File for Direct NFS Client
Direct NFS uses a configuration file, oranfstab, to determine the available mount points.
Create an oranfstab file with the following attributes for each NFS server that you want to access using Direct NFS Client:
serverThe NFS server name.
For NFS setup with Kerberos authentication, the
serverattribute name must be the fully-qualified name of the NFS server. Thisserverattribute name is used to create service principal for Ticket Granting Service (TGS) request from the Kerberos server. If you are configuring external storage snapshot cloning, then the NFSservername should be a valid host name. For all other scenarios, the NFSservername can be any unique name.localUp to four paths on the database host, specified by IP address or by name, as displayed using the
ifconfigcommand run on the database host.pathUp to four network paths to the NFS server, specified either by IP address, or by name, as displayed using the
ifconfigcommand on the NFS server.exportThe exported path from the NFS server.
mountThe corresponding local mount point for the exported volume.
mnt_timeoutSpecifies (in seconds) the time Direct NFS Client should wait for a successful mount before timing out. This parameter is optional. The default timeout is 10 minutes (600).
nfs_versionSpecifies the NFS protocol version used by Direct NFS Client. Acceptable values are NFSv3, NFSv4, NFSv4.1, and pNFS. The default version is NFSv3. If you select NFSv4.x, then you must configure the value in
oranfstabfornfs_version.Specify
nfs_versionaspNFS, if you want to use Direct NFS with Parallel NFS. Direct NFS supports only the defaultsyssecurity authentication with Parallel NFS. Direct NFS does not support Parallel NFS when combined with any of the Kerberos authentication parameters.security_defaultSpecifies the default security mode applicable for all the exported NFS server paths for a server entry. This parameter is optional.
sysis the default value. See the description of the security parameter for the supported security levels for the security_default parameter.securitySpecifies the security level, to enable security using Kerberos authentication protocol with Direct NFS Client. This optional parameter can be specified per export-mount pair. The supported security levels for the security_default and security parameters are:
sys: UNIX level security AUTH_UNIX authentication based on user identifier (UID) and group identifier (GID) values. This is the default value for security parameters.krb5: Direct NFS runs with plain Kerberos authentication. Server is authenticated as the real server which it claims to be.krb5i: Direct NFS runs with Kerberos authentication and NFS integrity. Server is authenticated and each of the message transfers is checked for integrity.krb5p: Direct NFS runs with Kerberos authentication and NFS privacy. Server is authenticated, and all data is completely encrypted.
The security parameter, if specified, takes precedence over the security_default parameter. If neither of these parameters are specified, then sys is the default authentication.
For NFS server Kerberos security setup, review the relevant NFS server documentation. For Kerberos client setup, review the relevant operating system documentation.
dontrouteSpecifies that outgoing messages should not be routed by the operating system, but instead sent using the IP address to which they are bound.
Note:
The
dontrouteoption is a POSIX option, which sometimes does not work on Linux systems with multiple paths in the same subnet.managementEnables Direct NFS Client to use the management interface for SNMP queries. You can use this parameter if SNMP is running on separate management interfaces on the NFS server. The default value is the server parameter value.
communitySpecifies the community string for use in SNMP queries. Default value is
public.
The following examples show three possible NFS server entries in oranfstab. A single oranfstab can have multiple NFS server entries.
Example: Using Local and Path NFS Server Entries
The following example uses both local and path. Because they are in different subnets, you do not have to specify dontroute.
server: MyDataServer1
local: 192.0.2.0
path: 192.0.2.1
local: 192.0.100.0
path: 192.0.100.1
export: /vol/oradata1 mount: /mnt/oradata1
Example: Using Local and Path in the Same Subnet, with dontroute
Local and path in the same subnet, where dontroute is specified:
server: MyDataServer2
local: 192.0.2.0
path: 192.0.2.128
local: 192.0.2.1
path: 192.0.2.129
dontroute
export: /vol/oradata2 mount: /mnt/oradata2
Example: Using Names in Place of IP Addresses, with Multiple Exports, management and community
server: MyDataServer3
local: LocalPath1
path: NfsPath1
local: LocalPath2
path: NfsPath2
local: LocalPath3
path: NfsPath3
local: LocalPath4
path: NfsPath4
dontroute
export: /vol/oradata3 mount: /mnt/oradata3
export: /vol/oradata4 mount: /mnt/oradata4
export: /vol/oradata5 mount: /mnt/oradata5
export: /vol/oradata6 mount: /mnt/oradata6
community: private
Example: Using Kerberos Authentication with Direct NFS Export
The security parameter overrides security_default:
server: nfsserver
local: 192.0.2.0
path: 192.0.2.2
local: 192.0.2.3
path: 192.0.2.4
export: /private/oracle1/logs mount: /logs security: krb5
export: /private/oracle1/data mount: /data security: krb5p
export: /private/oracle1/archive mount: /archive security: sys
export: /private/oracle1/data1 mount: /data1
security_default: krb5i
Related Topics
Enabling and Disabling Direct NFS Client Control of NFS
Use these commands to enable or disable Direct NFS Client Oracle Disk Manager Control of NFS.
By default, Direct NFS Client is installed in an enabled state. However, if Direct NFS Client is disabled and you want to enable it, complete the following steps on each node. If you use a shared Grid home for the cluster, then complete the following steps in the shared Grid home:
- Log in as the Oracle Grid Infrastructure installation owner.
- Change directory to
Grid_home/rdbms/lib. Enter the following command:
$ make -f ins_rdbms.mk dnfs_on
Note:
If you remove an NFS path that an Oracle AI Database is using, then you must restart the database for the change to take effect.
Enabling Hybrid Columnar Compression on Direct NFS Client
Perform these steps to enable Hybrid Columnar Compression (HCC) on Direct NFS Client:
Ensure that SNMP is enabled on the ZFS storage server. For example:
$ snmpget -v1 -c public server_name .1.3.6.1.4.1.42.2.225.1.4.2.0 SNMPv2-SMI::enterprises.42.2.225.1.4.2.0 = STRING: "Sun Storage 7410"- If SNMP is enabled on an interface other than the NFS server, then configure
oranfstabusing the management parameter. - If SNMP is configured using a community string other than public, then configure
oranfstabfile using the community parameter. - Ensure that
libnetsnmp.sois installed by checking ifsnmpgetis available.