OT: base64 encoded messages

From time to time, we receive some people's postings as Base 64 encoded messages that are shown as:

$ head -3 qq

SSBoYXZlIGZvdW5kIGFuIGludGVyZXN0aW5nIHNpdHVhdGlvbiBoZXJlLCBhbmQgaGF2ZSBydW4g b3V0IG9mIGlkZWFzLgogQSBsb2dvbiB0cmlnZ2VyIHdhcyBjcmVhdGVkIChieSBhIGxvbmctZ29u ZSBjb2xsYWJvcmF0b3IpIGluIHRoZSBTWVMKc2NoZW1hIGFuZCB1c2luZyBwdWJsaWMgc3lub255

While the person posting the garbled message is notified and searches for a solution, those that can't read (like me) can use this trick to read:

$ cat base64decode.pl

#!/usr/bin/perl -w

use MIME::Base64 qw(decode_base64);

open(FILE, "qq") or die "$!";
while (read(FILE, $buf, 60*57)) {

    print decode_base64($buf);
}
$ ./base64decode.pl | more

I have found an interesting situation here, and have run out of ideas.  A logon trigger was created (by a long-gone collaborator) in the SYS schema and using public synonyms. It was removed by accident from our testing environment by the DBA, and recreated by copying the one in the production environment. Only it now fails to compile, alleging table not found.

I will appreciate any idea. Details follow below.

The trigger:
...

Yong Huang       

--
http://www.freelists.org/webpage/oracle-l