Re: ORA-00600: internal error code, arguments: [711], [1], [32386120], [frame segment], [], [], [], []

This is a known bug within Oracle. It occurs occasionally when doing an insert with a returning clause. It is non-corruptive and has to do with the de-allocation of resources after the insert. I believe it was fixed in the 8.1.7.2 patchset, definitely in the 8.1.7.3 patchset, but you may want to check MetaLink. Also, if you have Oracle support, send them the tracefile to be sure this is truly the problem. It may just be similar to what I have seen happen.

HTH,
Patrick

In article <a1c3mk$m4l$1_at_news1.xs4all.nl>, Roy says...
>
>Hi,
>
>I am working with the following configuration
>- Oracle 8i (8.1.7) on VMS
>- Windows2000 sp2 application server with the "Oracle components for MTS"
>installed
>
>I have written a few Com+ components using OCI but now I seem to have a
>strange problem.
>
>Sometimes when I call a function to do an insert/update in a table I get the
>following error-message
>ORA-00600: internal error code, arguments: [711], [1], [32386120], [frame
>segment], [], [], [], []
>
>Strange thing is that when I activate the same function again all goes
>fine....there seems to be no way to predict when it goes wrong.
>It does however only goes wrong when I use the 'returning into' clause.
>
>eg statement is
>insert into table values ('aaa', 'bbb')
>returning field1, field2
>into :out1, :out1
>
>OCIStmtPrepare(m_hOCIStm, m_hOCIErr, statement, strnlen(statement),
>OCI_NVT_SYNTAX, OCI_DEFAULT);
>
>if (OCIBindByName(m_hOCIStm, &hOCIBind[0], m_hOCIErr,(text *) ":out1",
> -1, &record.field1, sizeof(record.field1),
> SQLT_STR,NULL, NULL, NULL, NULL, NULL, OCI_DEFAULT)
> || OCIBindByName(m_hOCIStm, &hOCIBind[1], m_hOCIErr,(text *) ":out2",
> -1, &record.field2, sizeof(record.field1),
> SQLT_STR,NULL, NULL, NULL, NULL, NULL, OCI_DEFAULT)
>} throw error;
>
> if(OCIStmtExecute(m_hOCISvc, m_hOCIStm, m_hOCIErr,
> (ub4) 1, 0, NULL,NULL,OCI_DEFAULT))
> throw E_OCI_EXECUTE;
>
>this seems fairly simple......does somebody recognize this problem?
>is there some serverpatch for this? or is it my own mistake?
>
>Thanks for any information,
>Roy
>
>
>
>
>
>
>
>
>
>
Received on Mon Jan 07 2002 - 11:35:35 CST