1 person found this helpful
So what you have is a script, where 2 database objects are being created/updated/compiled/whatever.
Our procedure editor wants one object per file.
You'll need to split your one script to two files, one with your package spec and one with your package body.
Your alternative would be to run the code through our worksheet as a script. You'll just have to add a show err to your script if you want to see your compilation errors.
Thanks for your answer.
Can you make SQL Developer ignore specific signs?. Like for instance "/". It looks as if you can do a lot of personalizations in "Preferences".
I can always take a database package from the database and save it locally as a .pls file (or .pks/.pkb) but it means extra work when I already have it locally on the .pck format.