EOF on compilation

[gulhaugen]

We have a problem with compilation of packages:
1. Oracle 9iR2 on Windows 2003 (with patchset)
2. PLSQLDev 5.1.3.704
3. Everyone is happy until suddenly, every developer experiences EOF and NOT CONNECTED ORACLE when they try to compile. (on very different packages, different db's)
4. If one saves the package to disk, and compile it trough the command prompt, everything is fine.
5. Restart of the database service, everything is ok again.

Question:
Why? I quess it has something to do with memory on the server, but I do not understand why, especially since one can compile through command window.

Also, this seems to happen after the server has been running a while.

Please help

Estimated time to recurrence, 5 days.

So

 

[Marco Kalter]

Though I do not know why restarting the database instance fixes the problem, the difference between a Command Window compilation and a Program Window compilation indicates an Oracle Server bug regarding the "Add debug information when compiling" preference (Tools > Preferences > Debugger tab page). The next time this error occurs (within 3 days?), you could try to disable this preference to verify if this helps.

------------------
Marco Kalter
Allround Automations

 

[gulhaugen]

Actually this didn't happen for a while.

But today it happened again.

Our database is now in a state where we cannot compile with debug info.

Any hints on how do determine what the source of the problem is?

We do not restart our database on a regular basis, so I have some time before I reboot manually.

 

[Marco Kalter]

Is there a user dump trace file on the server for this error? If so, can you send it to me?

 

[gulhaugen]

Not much in it.
Dump file c:\oradata\oraprod1\trace\udump\oraprod1_ora_2540.trc
Thu Jan 08 14:30:35 2004
ORACLE V9.2.0.3.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 , CPU type 586
Oracle9i Release 9.2.0.3.0 - Production
JServer Release 9.2.0.3.0 - Production
Windows 2000 Version 5.2 , CPU type 586
Instance name: oraprod1

Redo thread mounted by this instance: 1

Oracle process number: 66

Windows thread id: 2540, image: ORACLE.EXE

*** SESSION ID19.17719) 2004-01-08 14:30:35.000
Probe:read_pipe: receive failed, status 1

------------------------------------------

But the strange thing is that when I tried to compile with debug info on today, it worked again.

My guess is that on package in one of the systems make the debugger become in an invalid state until some cleanup occurs.

I did not restart the database this time.

 

[bwm75]

We are having the same problem with 9iR2 and developer 5.0.2.500.

Unchecking the "Add debug information when compiling" preference allows the code to compile successfully (Tools > Preferences > Debugger tab page).

 

[Marco Kalter]

The Oracle Server does indeed have problems compiling certain packages with debug information. Because of this we have addded an option to exclude specific program units from compilation with debug information.