Safe compilation problem with version 10

[Philippe Malera]

We recently migrate from version 9 to 10 (10.0.1.1694) and we are facing a new problem which wasn't in version 9.

Now, sometime when we compile a package, we get compilation errors, but they are not displayed on screen, we have to compile them in SQL*Plus to see the real error.

This problem disappear when we disable the option "Safe compilation" in Program window setup.
So now, the only workaround is to disable safe compilation and reenable it after.
This problem doesn't appear for all compilation error (about 5%), but difficult to find a relation.

We are 15 developers facing the same problem.

 

[Marco Kalter]

We'll check it out. Do you have a source file you can send me that reproduces the issue?

 

[Claus Pedersen]

It could be related to a previously reported problem in the Oracle database, having the effect that only the first 20 warning/errors are shown. If there are too many warnings, the 'real' compilation errors are not shown.
Try disabling PL/SQL warnings by issuing the code

ALTER SESSION SET PLSQL_WARNINGS='ENABLE:ALL';

or turn off PL/SQL warnings from inside PL/SQL Developer.

Also, refer to the post Cannot see all compile errors in a program window or similar posts.