Re: Dreaded PLS-123 Error

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