In trying to find out the cause of a DBFS issue, I learned what is expected (or helpful) when working with Support on DBFS issues.
1) Logon trigger for dbfs user to create a trace file..
1) Logon trigger for dbfs user to create a trace file..
CREATE OR REPLACE TRIGGER DBFS_LOGON
AFTER LOGON
ON DATABASE
declare
username VARCHAR2(30);
BEGIN
username:=SYS_CONTEXT('USERENV','SESSION_USER');
IF username like 'FOO' then
dbms_dbfs_content.setTrace(3);
execute immediate 'alter session set events ''45050 trace name context forever, level 0xfffff'' ';
END IF;
EXCEPTION
WHEN OTHERS THEN
NULL;
END;
/
2) Start the DBFS client with tracing turned on. (-otrace_file=
Remember if you are running DBFS, you are probably on a multi-node clustered environment, so you only need to do these steps on one of the nodes to gather the data. I turned the logon trigger on, remounted the FS with tracing.. reproduced issue. Verified the log files were created, disabled trigger, remounted without tracing.. I did this on only one node, and gathered what I needed with minimal issues.