Compile gives errors but does not indicate them

[John Duffy]

Hi,
I am using PL/SQL Developer v7.0.3.1123 on Oracle 10g.
I've hit a problem I don't know how to get around:
I am compiling quite a large package, and it is failing to compile with the normal message "Compiled with errors".
However, the error(s) are not indicated by the usual yellow highlighted line. Consequently with about 5000 lines of PL/SQL code to work through, I am having trouble finding this error - whatever it is!
If I put a really dumb error in the code such as a random text string outside of a procedure then it finds and displays the error as I expect with a 4003 PLS-00103 "Encountered the sysmbol... when expecting". Any ideas? Thanks, John.

 

[Al Davis]

Hi John,

Sorry I've no PL/SQL Developer solution, but a work around might be to save the code to a file and then run the file in SQL*Plus. I've found that SQL*Plus can often supplement the error reporting from PL/SQL Developer or give another perspective and usually the line number of the errro. Hope it works for you.

 

[John Duffy]

Hi Al,
Thanks for this idea. I did think about something similar - I pushed the whole lot though the PL/SQL Developer command window but without it telling me anything new.
I'll try your idea in the morning.
Best wishes

John

 

[mike]

Just a thought...One thing that might help is to make sure the "Add debug information while compiling" preference is turned off in the Debugger preferences. Also, make sure the "Safe Compilation" preference is turned off in the Program Window preference.

 

[John Duffy]

Hi,

Thanks Mike, for your thoughts. Unfortunately no change!

I have since pushed the file through SQLPlus and basically get the same result. The errors I can see with "show errors" are just the same hints that PL/SQL Developer gives me. My only recourse at present is to cut the source into "halves" and try and isolate the error that way.

I see a fairly tedious day ahead so if anyone else can weigh in then please do!

Regards

John

 

[John Duffy]

Just to let you know that this problem has (think goodness) mysteriously gone away - at least for the present!
All I was doing was tweaking code to reduce the number of compiler hints and warnings in case there was some kind of limit or something was masking an error.. Desperate I know!
Interesting...

Regards
John

 

[Theod]

Hi,

look here please.
https://forums.allroundautomations....=39876&Searchpage=1&Main=10259&Words=compiler+hint&Search=true#Post39876

"There is a sql script in the "Program Files\PLSQL Developer" folder alled "AfterConnect.sql" - this contains the following line:

ALTER SESSION SET PLSQL_WARNINGS='ENABLE:ALL';

Changing the ENABLE to a DISABLE gets rid of all the duff warnings and allows the 'real' cause of the compilation error to be displayed."