Some suggestions...

First, if this is a program reading in a log created by another real program (not the output from SQL*Plus), change the program to not report the error.

Second, if this is SQL*PLUS, and this script will be run more than once or you want to run it in a batch mode on a production system, stop what your doing with the log reading script and start writing a program that will do the work instead. SQL*Plus does not have the error handling capabilities to handle problems in a production system. You are setting your self up for a life of misery if you are attempting to use an interactive tool in a batch mode. Its fine for testing or development, but if you don't want to waste your company's or customers' money on an expensive outage, don't use SQL*PLUS.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.