DBFS Takes a long time to do an ls (or stat) on a directory while other file activity is going on
(Doc ID 1466378.1)
Last updated on MAY 24, 2021
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Exadata Hardware - Version 22.214.171.124 and later
Oracle 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 Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
During a period when concurrent session are adding new files and an ls or 'stat' is taking place on the DBFS fie system you may see.
a. The DBFS file system gets unmounted
b. Very slow performance.
The unmounts are due to either
The value of the environment variable
PERL_ALARM_TIMEOUT being exceeded (default is 15)
If DBFS is controlled by a OCR resource the CHECK_INTERVAL is exceeded. (The default 30)
More information can be obtained by mounting the DBFS file system with these additional options.
-o trace_file=/tmp/dbfs_client.log -o trace_level=1 -o trace_size=500 /dbfs
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!