Re: ORA-3113 and 1041 with large PL/SQL scripts

Hi Michael,

Thanks for your input. After trying to compile the script a few more times I noticed that it was actually dumping a trace file and core, inserting an ORA 7445 error in the alert log. I opened a TAR with Oracle and sent in the trace and core files. Oracle tech support got back to me and told me that they were able to reproduce it and that it was an instance of Oracle bug #476541. The tech guy couldn't tell me what was causing the pacakge to dump core like this, but the two things he suggested were to either compile the procedures individually ( i.e. not as parts of a package ), or to upgrade to Oracle 7.3.3.2 or later. I'm taking the second option since I need to do that anyway.

Thanks to everyone who had suggestions!

Bart

bialik_at_wis.weizmann.ac.il wrote in message <6htbs7$mpk$1_at_nnrp1.dejanews.com>...
>Hi, Bart.
>
> I just got the same error myself. After a LONG time with Oracle tech
> support I learned :
> A. Never write packages over 64K size.
> B. ERR3113 is caused by Oracle bug, but it may by by-passed by changing
> an application a bit.
> In my case it was caused by definition of PL/SQL table of RECORDS and
> using assignment T_FIELD := TO_NUMBER (PLSQTAB(i).FIELD_NAME);
> Apparently PL/SQL functions don't deal to well with that case.
> To by-pass the problem we used :
> T_FIELD_CHAR := PLSQTAB(i).FIELD_NAME;
> T_FILED := TO_NUBER(T_FIELD_CHAR);
> It solved the problem here.
>
> Good luck. Michael.
Received on Wed Apr 29 1998 - 07:59:38 CDT