Re: dbmf_output.put_line question

"Karsten Farrell" <kfarrell_at_belgariad.com> wrote in message news:<IDIN9.54742$vb3.2192344_at_news2.west.cox.net>...
> "Ubiquitous" <weberm_at_polaris.net> wrote in message
> news:au7j6s$4fm$1_at_news.utelfla.com...
> > I am encountering a really weird problem and wonder if someone
> > can suggest what might be causing it...
> >
> > I created some stored procedures and scripts in PL/SQL which
> > use dbmf_output.put_line to display messages when they are run.
> > The scripts and prcos both use dbmf_output.enable and are invoked
> > in a UNIX shell script which pipes the output to a log file
> > which is then emailed to the analyst and DBA as a daily report
> > on that night's run of the job.
> >
> > I ran and tested the job in a TEST instance to my satisfaction
> > (it runs with the put_line messages just fine), but when I copied
> > the scripts to our PROD instance (only making changes so it reads
> > the correct tables) and ran it, the display statemnets no longer
> > appear. Even more puzzling is that if I run the scripts in a SQL*PLUS
> > session on both instances, the display statemnets are produced!
> >
> > I am going to assume there is something different about the way the
> > two instances are configured but have no clue as to what it could
> > be. Does anyone have any ideas?
> >
> > Thank you!
> >

If the primary objective is to write stuff to a file then another approach to what you are doing is to use DBMS_FILE package to explicitly open a file and ONLY write to file what you need to instead of any junk that may appear with spool command.

Just a thought!

Regards
/Rauf Sarwar Received on Wed Dec 25 2002 - 15:29:23 CST