Database Alert Log entries: Direct NFS: Failed to set socket buffer size.wtmax=[1048576] rtmax=[1048576], errno=-1
(Doc ID 1352886.1)
Last updated on APRIL 25, 2024
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.
Symptoms
Database alert log shows these 'Direct NFS: Failed to set socket buffer size.wtmax=[1048576] rtmax=[1048576], errno=-1' entries:
alert_ORCL.log
~~~~~~~~~~~
...
Mon Aug 08 21:04:00 2011
Adjusting the default value of parameter parallel_max_servers
from 320 to 185 due to the value of parameter processes (200)
Starting ORACLE instance (normal)
...
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
...
Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 3.0
...
Mon Aug 08 21:05:19 2011
Direct NFS: Failed to set socket buffer size.wtmax=[1048576] rtmax=[1048576], errno=-1 <-- here
...
~~~~~~~~~~~
...
Mon Aug 08 21:04:00 2011
Adjusting the default value of parameter parallel_max_servers
from 320 to 185 due to the value of parameter processes (200)
Starting ORACLE instance (normal)
...
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
...
Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 3.0
...
Mon Aug 08 21:05:19 2011
Direct NFS: Failed to set socket buffer size.wtmax=[1048576] rtmax=[1048576], errno=-1 <-- here
...
Changes
N/A
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 |