DNFS :12c Database Doesn't Display Dedicated Network Interface In V$dnfs_channels
(Doc ID 2272501.1)
Last updated on MARCH 23, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Our database server is configured with 4 private network interface to handle DNFS I/O to NAS storage cluster. The IPs are defined in oranfstab file on the server.
path: XXX.xx.xx.xxx
local: XXX.xx.xx.xx
path: XXX.xx.xx.xxx
local: XXX.xx.xx.xx
path: XXX.xx.xx.xxx
local: XXX.xx.xx.xx
path: XXX.xx.xx.xxx
local: XXX.xx.xx.xx
However we don't see these paths display in either v$dnfs_channels or in alert.log for 12c databases.
On the same server, the information is available in 11g's v$dnfs_channels and alert.log.
12c alert.log:
Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 4.0
2017-05-18T14:00:50.282172-05:00
Direct NFS: channel id [0] path [vs-nnnnnnnn5000] to filer [vs-nnnnnnnn5000] via local [] is UP
11g alert.log:
Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 3.0
Direct NFS: channel id [0] path [xxx.xx.xx.xxx] to filer [vs-nnnnnnnn5000] via local [xxx.xx.xx.xx] is UP
Direct NFS: channel id [1] path [xxx.xx.xx.xxx] to filer [vs-nnnnnnnn5000] via local [xxx.xx.xx.xx] is UP
Direct NFS: channel id [2] path [xxx.xx.xx.xxx] to filer [vs-nnnnnnnn5000] via local [xxx.xx.xx.xx] is UP
Direct NFS: channel id [3] path [xxx.xx.xx.xxx] to filer [vs-nnnnnnnn5000] via local [xxx.xx.xx.xx] is UP
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |