Hi Marc! I had the same impression about the option to store files locally, but I had a conversation today with Oracle rep and he told me it that it is not possible not sure why.
This is why I opened this discussion. I am wondering that if initialy a shared file system like DBFS or other was not created, can it be added later to store files on it and solve the issue you brought up about files invisibility across the nodes?
I've definitely used UTL_FILE to store data on the local /u01 filesystem. While not intended for large files or large-volume I/O I can definitely tell you it works.
Although the Exadata configurator doesn't set up DBFS, it does create an ASM diskgroup for it, and yes, DBFS is an excellent way of storing files that are visible to both RAC nodes.
Hi , You can definitely store files generated in the UTL file DIR on the exadata machine temporarily however points to note are
1. as Exadata databases are most commonly RAC the files would be created on any one of multiple nodes depending on the compute node of the background process.
2. Oracle compute node disks are run in RAID 5 and are not meant for data storage ( 10K 600 gb sas)
3. If you use dbfs this is shared and can be accessed across multiple nodes but it cannot be NFS exported . we have also faced issues with DBFS not able to reclaim lob storage after large files are created and deleted from DBFS.
4. It might be simpler to just nfs mount a directory to all compute nodes and redirect utl )_file _dir to this shared location. If you use a multi headed NAs this will take care of availability requirements also.