SQL Developer says Compile sucessful but it is not

Question

I am trying to compile a procedure on a 10g instance. When I compile it, using any number of means to do so, it always says the compile was successful. Then when I try to view the changes in TOAD, they are not there. What is happening here? I using version 1.1.2.25 of SQL Developer.

Answer 1

True - but while I may be able to reproduce the problem on my database I can't provide the example without the 600Gb of underlying data.
Anyway, I've just located the package that was a problem last week and it was marked with a red cross indicating it was invalid - also double-checked that it had a status of INVALID in DBA_OBJECTS. (BTW - the problem was due to a dependent package having a duplicate variable declaration - but was still valid despite this being 'illegal')
So I right-click and select compile and this results in "SR_POLICY Compiled" being displayed in the Message Log pane. When I attempt to refresh the connections tree the staus flag does not change. Requery DBA_OBJECTS confirms that the status is still INVALID.
Then I right-click against the package in the connection tree and select Compile. This time I get the following message(s) ...
SR_POLICY Compiled
SR_POLICY Body Compiled
Also, the status in the connection tree has changed and the invalid flag has disappeared. The query against DBA_OBJECTS also confirms that the package is now valid.
Nobody else on the server, no changes to the underlying code, but the first attempt to compile fails.
It would be useful if others could contribute if they have come across similar examples on this sort of problem.