Re: Strange PL/SQL error

mickel_at_sulaco.OES.ORST.EDU (Paul Mickel) writes:
>Greetings,
>
>My co-worker and I found an interesting PL/SQL error not too long ago in one of
>our triggers. The error is:
>
> "PL/SQL Check #20112: Contact your Oracle Representative ... "
>
>Anyone know of this error, what might have caused it, etc. We tried to debug it
>but decided it was more cost-effective to rewrite the trigger. Any help apprec-
>iated.

Any other error condition that does not generate a specific error. Aren't I helpful. :)

Seriously, this generally means that the compiler is not sure how to interpret some of the code. It could be a lot of things (i.e. procedure specification, ambiguous declaration, type mismatch, etc.). Using default parameters in a procedure or function declaration improperly can do this. What I mean by ambiguous declalration is having a veriable with the same name as a field name.

The best way to locate the error is to comment out the code except for the procedure specification if applicable. Uncomment one line at a time and try to compile. Repeat the process until the error occurs.

These errors are very hard to lock because the code itself looks currect. Good luck and I hope you find it.

Later,
Steven Whatley Received on Wed May 18 1994 - 15:30:24 CEST