Home > IT Answers > Oracle > ORA-03113 error while compiling Oracle packages
Boball
0 pts.
 ORA-03113 error while compiling Oracle packages
Oracle, Oracle 8i, Oracle 9i, SQL, Standard Edition
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

Software/Hardware used:
ASKED: November 24, 2004  5:11 AM
UPDATED: November 26, 2004  12:14 PM
RELATED QUESTIONS
Answer Wiki:
I have seen this error when your session times out. Check your session/user settings. Stefan
Last Wiki Answer Submitted:  November 24, 2004  8:13 am  by  Spanayotov   0 pts.
All Answer Wiki Contributors:  Spanayotov   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

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

Dneaud
 0 pts.
 

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

Welcome
 0 pts.
 

There might be an database link involved.

SID1411
 0 pts.
 

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.

carlosdl
 63,580 pts.