Re: ORA-6550 PLS-707 parameter 2603 - internal error or unsupported structure.

"Wanda Zoe" <clarioneer_at_hotmail.com> wrote in message news:<cbe4dc$2ct6$1_at_newsreader02.ops.uunet.co.za>...
> Hi there..
>
> I've been doing "bulk insert" into an oracle db for a few years, and today I
> hit an error that's got me stumped...
>
> My test environment is unix/solaris/oracle 9i, running app from Windows 2000
> and XP
> All work fine on it of course!!
>
> New database was created with 8.1.7 on Solaris, and when my
> app do bulk insert on it, I get error :
> ORA-6550 PLS-707 internal error or unsupported structure [2603]
> My insert buffer is 32K. I load it with a begin clause, lots of inserts, and
> an end at the back, before I submit it.
> ie:
> begin
> insert into datatable values(1,2,3,4);
> insert into datatable values(2,3,4,5);
> ....
> end
>
>
>
> Currently the app work if the buffer has about 10 inserts in, but if I let
> it
> grow bigger, this pesky error pops up.
> I would like to get back to using the full 32K buffer.
>
> A search on metalink and google did not really help.
> oerr ora 6550 is not of much help either - except saying :
> "$ oerr ora 6550
> 06550, 00000, "line %s, column %s:\n%s"
> // *Cause: Usually a PL/SQL compilation error.
> // *Action:"
> (ps - the oracle message complain about line zero, column zero which is not
> of much help :-)
>
> I have a feelling the buffer get chopped of? But where do I see what the max
> buffer size is, and how do I change it?
>
> Any help would be appreciated.
> Thanks, Wanda

Hi Wanda,

Are the SQLs really just "insert into datatable values (..." or bulk insert in Oracle's sense? Is datatable just a local regular table? What is "insert buffer is 32K"? You get the error at runtime not compile time, correct? You're running an anonymous block, not compiling a stored program unit?

You can find error description for PLS-707 in documentation, which says

• quote ------- Cause: At run time, this is an internal error. At compile time, it indicates one of the following problems:

A call was made to a remote subprogram that has a parameter type or default expression not supported at the calling site.

An incomplete upgrade or downgrade was done to a database that has stored procedures. Perhaps incorrect versions of system packages such as STANDARD.SQL were installed.

A compiler bug was encountered. In such cases, legal PL/SQL syntax will fail to compile.
...
------- quote -------

Yong Huang Received on Thu Jun 24 2004 - 17:55:47 CDT