My Oracle Support Banner

Direct NFS: Channel Id Path to Filer Ping Timeout (Doc ID 1427921.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms


All production databases using dNFS have slow performance or server seems to hang when starting the media recovery (which is I/O intensive workload).
NetApp Filers data ONTAP 7.3.4 with NFS ver3.

11gR2 database alert log shows :


Thu Jan 19 14:29:59 2012
RSM0 started with pid=32, OS id=32549
Thu Jan 19 14:30:02 2012
Direct NFS: channel id 0 path filer<NAME> to filer filer<NAME> PING timeout
Thu Jan 19 14:30:02 2012
Direct NFS: channel id 0 path filer<NAME> to filer filer<NAME> PING timeout
....


 

Changes

Starting Dataguard on a remote Oracle cluster

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.