If the stored procedure is in the schema pointed to by your connection, then that is a bit strange. If it is in a schema under the Other Users node, then it is a matter of which privileges you have. That is, if you have no privilege to edit another user's procedure, then maybe the code editor will not display the code even if Quick DDL will show it due to some general dictionary viewing privilege you may have. Reading the following may help:
Can't see package body in SQL Developer version 220.127.116.11
SQL Developer Team
OK, so it likely has nothing to do with privileges then. Of course, a user can create many basic types of database object in his own schema without granting any extra, specific privileges.
Perhaps this could be something similar to the bug discussion (read from the top) in the following thread about an issue with Link Stored Procedures to Files -- not sure if that is still an outstanding bug:
Re: Serious SQL Developer bugs
Otherwise, all I can recommend is doing a retest on a clean SQL Developer install. By clean, I mean:
1. Unzip into an empty directory
2. Remove or rename the SQL Developer\system<3.n.n.n.n> directory with all your user preference settings.
3. Do not migrate settings when prompted after starting up the newly installed version for the first time.
All I can think of for the moment.
Thanks for the suggestions!
Unfortunately, I am seeing this issue from multiple instances of SQL Developer. Several people are accessing/developing in the same schema and use this procedure, and we have all seen this odd behavior from different computers.
If this problem is related to the bug you linked to, I don't know how, because I'm not doing anything with packages that I know of.
Curiouser and curiouser. If you see nothing in the Message log at that point, you might try seeing if anything comes out in a console window by following the initial steps in the How to collect debug info... instructions:
Also, although I doubt anything gets locked if two or more users open a stored procedure in write mode at the same time, you could try ticking the
Tools -> Preferences -> Code Editor -> Start in Read Only modecheckbox.
Hi, did you find a solution? I had the same issue. My sql developer version is 3.0 - so oracle suggested that the version is the issue. But i don't have issue with other databases. Please share your solution. Thanks
If you have a question or issue you need help with then create your own thread and post ALL of the particulars of your use case including: full sql developer version, database name and full version and an EXACT set of steps that you use to reproduce the problem.