Re: Stored Package
Date: 1996/03/13
Message-ID: <Do8Btr.Ds9_at_statcan.ca>#1/1
Tony Damon (bfntd_at_aimnet.com) wrote:
: Matt Marrow (marrowm_at_logica.com) wrote:
: : Dear ¤_at_ ¶§ «ü (!!)
: :
: : After a package fails to compile, type show errors at the SQL*Plus prompt.
: :
: : This will give you the error and the line number (which corresponds to the
: : line numbers in USER_SOURCE, not necessarily the line number in the
: : file you were building the package from (if you were using a file of course))
: :
: To help us find the correct line number we do the following:
: set echo on
: set termout off
: spool myfile.list
: create procedure ....
: ...
: ...
: ...
: /
: set termout on
: show errors
: spool off
: Then if there are errors you can view myfile.list. The echo command
: will show the line numbers (including blank lines) so the line
: number displayed by "show errors" corresponds to the statement
: in question.
: HTH,
: Tony Damon
maybe I'm missing something here but ... When we compile packages within PL/SQL, one at a time and there is a problem, it is simple to find. Simply list the contents of the buffer (this includes line numbers that PL/SQL references) then show errors. Having a window that scrolls enough to include the whole package helps.
PGY (Opinions expressed are mine and mine alone)
################################################################ # Paul Young # # youngpa_at_statcan.ca # # Statistics Canada # ################################################################Received on Wed Mar 13 1996 - 00:00:00 CET