ORA-03113 end of file on communication channel

[cpc1]

We are running:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - 64bit Production
PL/SQL Release 9.2.0.1.0 - Production
on two servers. One server has our live database. The other has 2 instances - one for development and one for training.
Last week a problem developed with compiling procedures, creating tables, user etc on the development instance. We get ORA-03113 end of file communications channel. It doesn't happen on with other instance. In addition if we paste the same SQL into a command window there is no problem. Any ideas? We have been advised to upgrade to 9.2.0.5 but I think that if it was a version problem it should occur on all instances.
Any advice?

 

[cpc1]

Found the answer in an earlier forum topic. Have turned Add debug information when compiling off and it worked.

 

[Wojtek]

I think that this option should be turned off as a default. Had the same problem and don't know what is going on.

 

[Bill Pry]

Turning off the debug option prevents variable tracking in debug.

While this workaround keeps you from having to bounce the database, it's not an acceptable situation.

Need a fix for the problem.

 

[Marco Kalter]

Unfortunately there are several Oracle bugs concerning debug information. Therefore we have added an option in 6.0 to selectively exclude debug information from specific objects. The real solution, instead of a workaround, has to come from Oracle though.

 

[Dennis]

Marco,

I'm experiencing the ORA-03113 error ONLY with PL/SQL. After about 5 minutes, I receive this error when connected through a VPN from home to our 10g app server.

At the same time that I see this problem with PL/SQL, I have NO problems when using either an ODBC connection or a connection to our application.

This doesn't seem to be a problem that you can throw at Oracle.

Any suggestions?

Thanks,

Dennis
IT Director

 

[Marco Kalter]

Do you get this error during compilation?

Note that ORA-03113 indicates that the session on the client has lost connection to the server. Usually this implies that the server process has died, but I can imagine that network problems can also cause this symptom. Regardless, it does not necessarily affect other sessions.

 

[betapower]

Hi,
I am using ORACLE 9.2.0.5 and PLSQL-Developer Version 6.0.4.906. I get the same error when starting the debugger (ORA-03113 end of file communications channel). Obviously the ICD-Vector is missing:

Here 's the trace file message:

*** 2005-01-21 15:46:19.922
ksedmp: internal or fatal error
ORA-00600: Interner Fehlercode, Argumente: [17285], [0x4DC2E88], [4294967295], [0x2DFE108C], [], [], [], []
ORA-00604: Fehler auf rekursiver SQL-Ebene 1
ORA-06509: PL/SQL: ICD-Vektor fehlt in diesem Paket
ORA-06512: in "ET3000.PBREAK", Zeile 560
ORA-06512: in "ET3000.PBSDE", Zeile 108
ORA-06512: in Zeile 1
ORA-00604: Fehler auf rekursiver SQL-Ebene 1
ORA-06509: PL/SQL: ICD-Vektor fehlt in diesem Paket
ORA-06512: in "ET3000.PBREAK", Zeile 560
ORA-06512: in "ET3000.PBSDE", Zeile 108
ORA-06512: in Zeile 1

I loaded pbload.sql as sysdab again and there was an error that the several packages would be invalid:

DBMS_DEBUG - missing or invalid package spec.
DBMS_DEBUG - missing or invalid package body.
PBUTL - missing or invalid package spec.
PBRPH - missing or invalid synonym.
PBRPH - missing or invalid package spec.
PBRPH - missing or invalid package body.
PBSDE - missing or invalid package spec.
PBSDE - missing or invalid package body.
PBREAK - missing or invalid package spec.
PBREAK - missing or invalid package body.

Thanks.

Holger, Software Developer

 

[mike]

We recently upgraded and now I get this error if I compile with debug info. Bummer. I really like the debugger.

What I noticed is that I can compile without debug info. After it is compiled, I can then add the debug info without a problem (You know, right click the package in the object browser and select "Add debug info"). At least I can so far - it's only been a few days.

I thought I would share that if others are having this issue and need the debugger for something.

Mike