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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
