Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.
Notice: I'm taking a break from blogging to focus on Atari Gamer . com, check it out!

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
We've updated some of our databases to 12c recently, at the same time I was working on an issue in some of the PL/SQL packages that I've built and running some tests on these. To my surprise when I tried to run my test PL/SQL procedure, SQL Developer was not showing in its run dialog.

I tried to see if the same procedure would execute by writing an anonymous PL/SQL block and it did.

This is what SQL Developer (4.0.2) was showing me...The package clearly defines a procedure, but it is not visible in the run dialog box, instead SQL Developer is reporting an empty package definition (no public members).

I checked the DB version and the results were

Thinking this is a 12c related problem, I connected to a different database that has not been upgraded, still at 11gR2 level, lo and behold, my procedure was visible in the run dialogue again. Definitely a 12c related issue then.

The DBA suggested that I try SQL Developer 4.1 Early Adopter to see if that helps. It did! Looks like SQL Developer 4.0.x is not fully compatible with version of the database.

The fixed bug list confirms this...

Looking deeper into the bug it only seems to affect database version, if you are on, this problem does not show up.

So there you go, if you got the latest DB version, the latest SQL Developer fixes this little problem!


Skip down to comments...
A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. If you spot something out of place, please do let me know.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
comments powered by Disqus
Other posts you may like...