Question

  Asked: Nov 24 2004   5:11 AM GMT
  Asked by: boball


ORA-03113 error while compiling Oracle packages


Oracle, Oracle 8i, Oracle 9i, Standard Edition, SQL

Hi All

Recently we migrated our PLSQL code from Oracle 8.1.7.0 to 9.2.0.4.
While compiling our packages in 9i, we are getting the ORA-03113: end-of-file on communication channel error.
This happens only when we compile two particular packages.
And then when we connect again immediately, and recompile the same package, it gets compiled.

This is only happening for two packages, frequently. All other packages are not giving this error.

Why could this be happening? Any pointers to this would really help.

Thanks
Bob

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



I have seen this error when your session times out. Check your session/user settings.

Stefan
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Oracle, SQL Server and Development.

Looking for relevant Oracle Whitepapers? Visit the SearchOracle.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

dneaud  |   Nov 24 2004  9:13AM GMT

The problem could related to function prototypes not matching the final function definition. Do you have in your package a function/procedure for which the default parameter value is different in specifications and in body?
If yes, try to remove the default clause or synchronize both definitions.

regards

 

welcome  |   Nov 25 2004  1:19AM GMT

Once I received this error with the following:
- a table in an Oracle 8.1.6 database had a database
trigger used to replicate the table, by updating an
identical table in an Oracle 7.1.5 database.
- performing updates in Oracle 8.1.6 from SQL*PLUS worked
ok.
- performing updates in Oracle 8.1.6 from an Oracle Forms
application produced the ORA-03113 error.

My solution was changing the database trigger, so that instead of updating the remote table, it activated a
remote procedure passing it the record’s data and letting
the remote procedure update the table in its own database.

I received the error at run-time only, not at compilation.

No one could give a clear explanation why did it occur,
but it’s clear that it’s related to some incompatibility
between the two database versions.

Maybe this info could help you.

Best rgds,
Iudith

 

SID1411  |   Nov 26 2004  3:30AM GMT

There might be an database link involved.

 

carlosdl  |   Nov 26 2004  12:14PM GMT

Do these packets use a database link ?
The problem could be the DB Link configuration, and if so, of course this affect only the code that uses it.