ORA-0314 not connected to Oracle

[soldado]

I am having problems compiling my packages in the program file editor. When i try to compile a package i get the ORA-0314 not connected to Oracle error. I am able to successfully compile the same package using the command file editor. Not sure what's going on ? Have any of you run into this problem? I recently downloaded the new PL/SQL developer 7.0 version.

Best Regads,

 

[jto]

hello,
I've experienced the same problem but only on one database.
PLSQL Dev 7.0.0.1050
Oracle Client 10.1.0.4

Db version 10.1.0.4 - no problems
Db version 9.2.0.6 - one db - no problems, another one exactly the same behaviour as you have described.

there is nothing in the database log files and I have no problems with SQL Navigator...
best regards
Jiri

 

[Marco van der Linden]

Is 'Preferences/Debugger/Add Debug information when compiling' checked? If so, uncheck it and then try to compile.

 

[jto]

yep, if I switch it off, everything is compiled without any problem.
now of course the question - how can I make it run with the debug info?

regards

 

[soldado]

Myd database version is 9.2.0.5 I tried unchecking the Preferences/Debugger/Add Debug information but still no luck. Not sure what's going on. I emailed support already.

JTO,
Try right clicking on the package body and selecting add debug information. It used to work for me on previous releases.

 

[soldado]

I finally got it to compile. These are the steps that I took to get it to compile:

1. Backed up the preferences directory.
2. Uninstalled PL/SQL Developer.
3. Deleted the PL/SQL DEveloper folder under the Program Files directory.
4. Re-installed PL/SQL Developer.
5. Modified the preferences to uncheck the "Add debug information when compiling" check box.
6. Compiled the packages successfully.
7. Updated the preferences to check the "Add debug information when compiling" check box.
8. Unable to compile packages. ORA-0314: not connected to Oracle error raised.
9. Exited out of the PL/SQL Developer program.
10. Opened the PL/SQL Developer program and unchecked the "Add debug information when compiling" check box.
11. When directly to the package object, righ clicked and selected the "Add Debug Information" option. (WORKAROUND).
12. Was able to debug package successfully.

The next thing I'm going to try is add my preferences back into the preferences folder.

 

[soldado]

I added my preferences and the problem returned. I was unable to compile packages either way. The infamous ORA-0314: not connected to Oracle returned.

Replaced the original preferences that come when you first install the application and i was once again able to compile my packages. However,
I still have to use the workaround that I described earlier because I am unable to compile packages if I check the "Add Debug INformation when compiling" check box.

 

[Marco Kalter]

That is strange. I can only imagine the following preference settings affect these low-level compilation issues:

1. Program Window > Background compilation.
2. Program Window > Safe compilation.
3. Connection > Session mode.
4. Connection > Oracle Home (or OCI Library).

Can you verify if these preferences are set differently and affect the problem?

 

[ThomyKay]

I've seen the same issue today with 1 package. Will verify the settings tomorrow morning.

 

[soldado]

The seeting between my preferences and the original setting are the same. See below.

1. Program Window > Background compilation. UNCHECKED

2. Program Window > Safe compilation.
UNCHECKED
3. Connection > Session mode.
EMPTY
4. Connection > Oracle Home (or OCI Library). EMPTY

 

[ThomyKay]

My settings:
Program Window - Background Compilation - UNCHECKED
Program Window - Safe Compilation - UNCHECKED
Connection - Session Mode - Dual Session
Connection - Oracle Home - emtpy (using default)
Connection - OCI Library - empty (using default)

btw: The package compiles successfully when executing it in Command windows

 

[ThomyKay]

Marco, that issue seems to be introduced with the final release version. it wasn't there in Beta6. I get the error now with most (not all) of my packages and types.

 

[Marco Kalter]

Nothing relevant has changed between beta 6 and the final release. To ensure that it's not the database state, can you shutdown and restart the database instance?