The problem is you have data on two lines but you are reading the file in a line at a time. You need to remember your state if you want to do it linewise. There are other ways to do it, possibly with split or by setting $/. Here is an example:

while(<DATA>){ chomp; if ( m/^ERROR/ ) { $error = 1; push @errors, $_; } else { next unless $error; $error = 0; if ( m/ORA\-00001/ ) { pop @errors; # ignore values and pop off @errors stack; } else { $errors[-1] .= " $_"; # add error string to line msg } } } print "$_\n" for @errors; __DATA__ ERROR at line 2: ORA-00002: blah2 junk line junk line junk line ERROR at line 1: ORA-00001: unique constraint (TBUSOP_1UQ) violated junk line junk line junk line ERROR at line 3: ORA-00003: blah3

cheers

tachyon


In reply to Re: greping DB ERROR by tachyon
in thread greping DB ERROR by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.