Don't use SQL*Plus

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.

Comment on Don't use SQL*Plus

Replies are listed 'Best First'.
Re: Don't use SQL*Plus by pelagic (Priest) on Apr 16, 2004 at 19:22 UTC
You shouldn't say don't use SQL*Plus. I'm using that thing for years and once you know to handle it, it's ok for a lot of tasks. And maybe the logfile was created by sqlloader which is very efficient for large amounts of data. pelagic	[reply]
Re: Re: Don't use SQL*Plus by Steve_p (Priest) on Apr 16, 2004 at 20:18 UTC
Unfortunately, there are errors that SQLPlus will return a zero no matter what you do. Then, your script that is running SQLPlus needs to handle them. So, yes, it can be done; however, in most cases, it is a kluge to avoid writting a program that can do the same work, but only better.	[reply]