Re: Trigger Compilation Errors

From: Neville Sweet <sweet.neville.nj_at_bhp.com.au.no_junk_today_thanks>
Date: 1998/03/18
Message-ID: <01bd521f$9a740340$45f11286_at_itwol-pc3963.itwol.bhp.com.au>#1/1


Mark,

In SQL/Plus, issue:
show error
immediately after attempting to compile. This gives you a line number that won't directly correspond to the line number in a text editor, because all completely empty lines are ignored. To make life easier, before attempting to compile issue: set echo on
which will output line numbers and your PL/SQL when you compile. If your trigger is huge then you can send the output to a file by specifying a spool file (Alt-F,L,F).

In the proper sequence:

set echo on
Alt-F,L,F, compile.txt
_at_your_trigger assuming the trigger is stored in a '.sql' file show error
edit compile.txt

Mark Cudmore <mcudmore_at_kamloops.env.gov.bc.ca> wrote in article <1998Mar17.140013.10044_at_vmsmail.gov.bc.ca>...
> Hi all, I am trying to create a trigger on a table in SQL*PLUS, and it
 says
> that it creates the trigger with compilation errors. Now how do I see
 those
> compilation errors so I can debug my trigger???
>
> This is driving me batty, please help!!
>
> --
> Mark Cudmore
> email: mcudmore_at_kamloops.env.gov.bc.ca
>
>
>
>
Received on Wed Mar 18 1998 - 00:00:00 CET

Original text of this message