UTL_FILE in a trigger or calling a stored procedure within a trigger

Question

Hello,
We are using Oracle 8i version where I need to either call a SP within a trigger or use UTL_FILE within a trigger.
1. SP runs fine by itself to write to a file but when I try calling SP within a trigger-> I get INVALID Path - is there some kind of restriction with DB triggers and UTL_FILE options
create or replace trigger testtrig
after insert on test_table
for each row when (new.stat_code = '99')
BEGIN
utl_file_test_write;
EXCEPTION
WHEN others THEN
raise_application_error(-20000, sqlerrm);
END;
2. use UTL_FILE with a trigger
create or replace trigger testtrig
after insert on test_table
for each row when (new.stat_code <> '99')
DECLARE
v_line varchar2(32767);
v_location varchar2(80) :='/u01/oraadmin/udump';
v_filename varchar2(80) := 'KC11.txt';
v_handle utl_file.file_type;
BEGIN
dbms_output.put_line('Location is'||v_location);
dbms_output.put_line('Location is'||v_filename);
v_filename := :new.emp_id;
v_handle := utl_file.fopen(v_location, v_filename,'W',32767);
v_line := :new.emp_id;
utl_file.put_line(v_handle,v_line);
utl_file.fclose(v_handle);
EXCEPTION
WHEN TOO_MANY_ROWS THEN
dbms_output.PUT_LINE('Too Many Rows');
WHEN NO_DATA_FOUND THEN
dbms_output.PUT_LINE('No Data Found');
--WHEN utl_file.invalid_path THEN
-- RAISE_APPLICATION_ERROR(-20000, 'utl_file.invalid_path');
WHEN utl_file.invalid_mode THEN
RAISE_APPLICATION_ERROR(-20000, 'utl_file.invalid_mode');
WHEN utl_file.invalid_filehandle THEN
RAISE_APPLICATION_ERROR(-20000, 'utl_file.invalid_filehandle');
WHEN utl_file.invalid_operation THEN
RAISE_APPLICATION_ERROR(-20000, 'utl_file.invalid_operation');
WHEN utl_file.read_error THEN
RAISE_APPLICATION_ERROR(-20001, 'utl_file.read_error');
WHEN utl_file.write_error THEN
RAISE_APPLICATION_ERROR(-20001, 'utl_file.write_error');
WHEN utl_file.internal_error THEN
RAISE_APPLICATION_ERROR(-20001, 'utl_file.internal_error');
End;
I still get INVALID_PATH. What am I missing?
Any help is greatly appreciated.
Thanks.

Answer 1

Hi,
from docs on UTL_FIL.FOPEN:
location:
Directory location of file. This string is a directory object name and is case sensitive. The default is uppercase. Read privileges must be granted on this directory object for the UTL_FILE user to run FOPEN.This, '/u01/oraadmin/udump' does not look like the name of a DIRECTORY object.
Besides, the whole idea of having UTL_FILE commands directly in a trigger body sucks. At the least stay with a stored procedure.
And have you considered what should happen with that file in case the transaction is rolled back?
Regards
Peter