Equest111 has asked for the wisdom of the Perl Monks concerning the following question:
I recently joined a new team that uses perl as a 'driver' to execute n number of SQL files (Oracle). However, the team is manually scripting logs prior to executing the scripts. And they are manually grepping log files for errors because flushing the buffer in the script so perl can do the grepping is too complicated. They've said it's impossible, or too hard, to have the perl script generate the log, capture stdin/std err/stdout to log file and print to screen, and grep log file up to most recent command. I'm not terribly experienced with PERL but moderately versed in other shells. This doesn't seem hard to solve but need some specific guidance so I can propose working solution to a group that will only consider a solution once and if it doesn't work will 'told you so'. Have tried t command and hot file handler. We're having trouble capturing sqlplus to log. Much Thx - living in the dark ages
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Logging and and capturing sqlplus parameters and results in log
by afoken (Chancellor) on Sep 09, 2011 at 06:02 UTC | |
|
Re: Logging and and capturing sqlplus parameters and results in log
by FunkyMonk (Bishop) on Sep 10, 2011 at 14:24 UTC |