Utl_mail attachments

Question

I'm using Oracle 10g, Linux Redhat.
I spooled a query to the '/tmp/errlog.txt' and want to email the results.
I'm using this statement to email the results.
BEGIN
EXECUTE IMMEDIATE 'ALTER SESSION SET smtp_out_server = ''smtp.fmi.com:25''';
UTL_MAIL.SEND_ATTACH_VARCHAR2(
sender => '[email protected]',
recipients => '[email protected]',
subject => 'PR1 Trigger Error Log',
message => 'Attached is the PR1 Trigger Error Log',
attachment => '/tmp/errlog.txt');
END;
I'm getting the email but the attachment?
Any advice?
Thanks in advance.

Answer 1

The parameters that need to be provided are:
attachment
The manual says +"Text attachment+". In other words, the contents of the text file.
att_mime_type
Specifies the type of attachment. Default is plain text. Mime type can be html text, or in the case of binary attachments, pictures, video, audio and so on.
att_filename
What the attachment is called (e.g. filename). This does NOT mean point to a file somewhere on local disk (or the network) and the file automagically attaches itself to the e-mail.
The result of this is a Mime body that contains both e-mail contents and attachment contents. Have a look at {message:id=4402801}. It shows how the actual Mime body (that constitutes the e-mail header, message and attachment) looks like.
This is what you need to create using code... and then deliver using SMTP. The UTL_MAIL package is a very primitive (and poorly written) interface that creates such a Mime body for you and delivers it for you by calling the UTL_SMTP package.
I suggest that you familiarise yourself with the basics of Mime and how attachments works and what the formatting requirements are. The easiest is crafting the type of e-mail that you want to send using your favourite mail reader and then e-mail that to yourself. After receiving that e-mail, look at the "source" view (raw format view) of that e-mail to see how it looks like.
And what you see is what you will need to create - using UTL_MAIL to do it, or (even better), coding it yourself (e.g. HTML report e-mails with gif attachments that serve as embedded graphics in the e-mail, and so on).
It is not that difficult. It simply requires basic understanding and not assuming that a parameter does something that is obviously does not do.