PL/SQL batch jobs and error reports handling

Question

Has anyone ever had to write exception and statistics reports from a PL/SQL batch job and how have those been handled? I have 3 options below not but sure what is best (or is there another) way to do this.
I have a series of batch jobs that are written in PL/SQL. A unix script will invoke a SQL*Plus script that calls a stored procedure. The stored procedure may call other procedures and functions. I'd like to collect all the errors and write them out a report that the user can review. I was thinking of just writing a message using DBMS_OUTPUT and spool that to a file in my script, but I have concerns that other message in the buffer may end up in the report. The other thought was to use UTL_FILE but then I would have to make sure the file handle got passed thru all the procedures and functions appropriate. The last thought was to write to a table ( a temporary PL/SQL table) , and then read that table and write to a file using UTL_FILE (don't have to pass file handles that way) - but I'm not sure if a called function or procedure can access that table.
null

Answer 1

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by mirp:
Has anyone ever had to write exception and statistics reports from a PL/SQL batch job and how have those been handled? I have 3 options below not but sure what is best (or is there another) way to do this.
I have a series of batch jobs that are written in PL/SQL. A unix script will invoke a SQL*Plus script that calls a stored procedure. The stored procedure may call other procedures and functions. I'd like to collect all the errors and write them out a report that the user can review. I was thinking of just writing a message using DBMS_OUTPUT and spool that to a file in my script, but I have concerns that other message in the buffer may end up in the report. The other thought was to use UTL_FILE but then I would have to make sure the file handle got passed thru all the procedures and functions appropriate. The last thought was to write to a table ( a temporary PL/SQL table) , and then read that table and write to a file using UTL_FILE (don't have to pass file handles that way) - but I'm not sure if a called function or procedure can access that table.
<HR></BLOCKQUOTE>
Just a thought
If You use utl_file, You can write all opeations with files in a separate package with public variables of file handles and so on. Not necessary to pass all variables to each procedure and function