Upgrade to version 17.2 and try again.
4.1.5 is old.
No matter whether you are running a script in Worksheet to create a package, or editing an existing package and hitting the Compile button, View > Log should display a Compiler tab with the errors, even in 4.1.5.
Clearly, upgrading to 17.2 (without migration of 4.1.5 user settings) will resolve the problem, and may even do so with migration of settings. Otherwise, staying on 4.1.5, you can try...
1. Window > Reset Windows To Factory Settings
2. Delete the system_cache folder under your system188.8.131.52.78 folder.
3. Or, finally, nuke system184.108.40.206.78 (after exporting your connection definitions!) and restart SQL Developer to initialize settings.
OK, I went ahead and installed Version 220.127.116.11. The only thing I imported was my connections.
So when I open a PL/SQL package i have saved on my hard drive and compile, I still do not get a Compiler tab with errors, same as with Version 18.104.22.168.
If I open the same PL/SQL package in the Connections navigator and compile from there, I do get a Compile tab with the compiler message listed.
So how do I get the Compiler tab to appear when I compile a package that I've opened from my hard drive?
Have you ticked the check box for Tools > Preferences... > Code Editor > Link Stored Procedures to Files
In addition, if I DROP PACKAGE.., then copy/paste the package spec into the worksheet and Run Script (F5), then copy/paste the associated package body (with some error in it) into the worksheet and Run Script (F5), the Compiler tab also displays with the error. Same thing if I both package spec and body are run together in the worksheet, or combined into one .sql file, then File > Open, then Run Script (F5). In the case of opening a .sql file, no Compile icon is available in the tool bar because by default .sql is associated in Tools > Preferences... > File Types with SQL Script (Worksheet) rather than PL/SQL (Code Editor).
Yes, that option was ticked at the start.
I'm not sure what you want me to do in the Edit: portion of your response above. I always want to work from my files saved on the file system....
This is all very bizarre, since this had been working properly for the longest time...
Anything else I can try?
I have edited my reply above a bit more, working through various other cases on 17.2.
Check how Tools > Preferences... > File Types is configured for the specific file extension(s) you are using for you PL/SQL files. If the answer is not there, I am not sure what else to recommend.
please post pictures of what you're doing, and include what the log panel is showing
now show us your editor with the file open, and show us what you see after a compile or F9 and of course include the log panel in your screenshot
Here is the editor with the file open (ERTS_UTILITIES_4.pkb). I commented out the first variable (outMessage1) and compiled, so I should get a compile error. Notice that the package is marked as errored in the Connections navigator, but no compiler tab that tells me what the error is:
Now, if I navigate to the ERTS_UTILITIES_4 Body tab and hit compile, I get the following. Notice there is a Compiler tab that gives me a list of errors:
So, that is what is going on. All I need is that compiler tab to show up when I compile the package from the file!
Any errors in the logging page?
Also if you save this as a .sql file and open it in a sql worksheet, does it not work there, either?
This is what the Logging Page looks like when compiling the the package from either source (I scratched out schema names):
If i take all of the above package code, put it in a SQL worksheet, and hit the Run Script statement, then it will compile, and I do get the Compiler tab at the bottom.
But taking all of the code and renaming the files is not an option.
Your last post nicely confirms what you have been saying all along. So here is what we know so far...
1. Issue only occurs in conjunction with Tools > Preferences... > Code Editor > Link Stored Procedures to Files
2. You use typical (seeded in Tools > Preferences... > File Types) file extensions (.pks and .pkb)
3. Not sure what Logging Page is telling us. The sort is not by Sequence, but you show some ExpiredTextBuffer messages, which presumably means something else is modifying that buffer. Some situation like:
ExpiredTextBufferExceptionis thrown when clients attempt to access an
ExpirableTextBufferSnapshotafter that snapshot has expired, due to the underlying text buffer being modified.
4. Starting with fresh, default user settings did not help, and the issue occurs on both 4.1.5 and 17.2.
What we do not know are things like...
1. Whether the files on disk are ordinary OS files, or files managed by version control software (Subversion?)
2. If the files are unusually large, if you have tried increasing the JVM memory limit in your product.conf file.
3. Other environmental factors like OS and Java version, and whether it came bundled with SQL Developer.
and any other unusual environmental factors you can think of. For example, one hard-to-determine issue got resolved by removing a bar-code printer's driver.
This is still an issue. If you have any more suggestions, or if anyone in the forum does, please let me know.