Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Dreaded PLS-123 Error

Re: Dreaded PLS-123 Error

From: Ethan Post <post.ethan_at_gmail.com>
Date: Thu, 9 Nov 2006 14:00:39 -0600
Message-ID: <357b48a90611091200i54c01fd8h9d4ddbddc778e372@mail.gmail.com>


Yes we can, however since you can not guarantee order of trigger fire this is a "poor" solution. It will result in two audit id's because it will be seen as two transactions. We can do it but not ideal. I was hoping someone would reply, "oh you poor yank, just set compatibility=... and that will fix it".

This is a weakness because it is not always just the size of the column, but has to do with the size of the dependencies in the size of the stack (*or something thereabouts*) so in theory you could have a very small trigger which would not compile also.

On 11/9/06, Reidy, Ron <Ron.Reidy_at_arraybiopharma.com> wrote:
>
> Can you split the trigger into smaller PL/SQL compilation units?
>
>
> ------------------------------
>

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Nov 09 2006 - 14:00:39 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US