Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!news.he.net!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: rjparker42@yahoo.com (jparker)
Newsgroups: comp.databases.oracle.tools
Subject: Extracting with sqlplus - what about errors?
Date: 12 Dec 2002 10:39:58 -0800
Organization: http://groups.google.com/
Lines: 9
Message-ID: <9c3d7f60.0212121039.190d870c@posting.google.com>
NNTP-Posting-Host: 216.177.27.160
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1039718398 15868 127.0.0.1 (12 Dec 2002 18:39:58 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 12 Dec 2002 18:39:58 GMT
Xref: newsfeed1.easynews.com comp.databases.oracle.tools:55347
X-Received-Date: Thu, 12 Dec 2002 11:51:29 MST (news.easynews.com)

Running an extract through sqlplus.  Our client has an environment in
which disk tends to fill up.  So checking what happens when sqlplus
cannot 'spool' to a file I find that I don't get an error, the process
just completes and goes on it's merry way.  This is in spite of an
'whenever error' clause which one would think would trap an OS error
like that.  Any thoughts?

cheers
j.