Re: SQL*Plus Problem--Pls help !!

If there are few cursors and you want to test the program code without data changing, I have inserted a boolean "program_debug_parameter" and then tried it to find program erors without changing any data - but it is only for relatively simple programs:

v_Only_program_code boolean := TRUE;

cursor xxxx is ....
where ...
and v_Only_program_code = FALSE;
(the oracle optimizer can handle this expression without problems).

This ensures that no data is fetched from the cursor - but even this method has several downfalls.

akarb_at_xinfo.dk

agichen wrote in message <0221c012.7ffe3755_at_usw-ex0101-007.remarq.com>...
>Hello,
> I have some weekly and monthly routine jobs.
> Usually,I schedule my job via crontab launching sql*plus.
> My scripts have lots of DML(DDL) statements,now the problem is
> how should I know that my script is correct without any syntax
>error or mistyping(ex. just loss a semicolon) ??
> I always find some errors after executing the script,is there any
>method can be used to detect any errors before running the script ??
>
> Thanks for any suggestions !!
> Any idea ?
>
>Rgds,
>Agi
>
>
>* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network
*
>The fastest and easiest way to search and participate in Usenet - Free!
>
Received on Tue Jan 04 2000 - 01:55:48 CET