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

Thanks, Rick.

Alex

"Rick Wessman" <Rick.Wessman_at_oracle.com> wrote in message news:soc8zba17hz.fsf_at_rwessman-sun.us.oracle.com...
> This is a server bug. While this workaround will likely work, I strongly
> suggest contacting Oracle support. A patch for this likely already exists.
>
> Rick
>
> "Alex Ivascu" <alexdivascu_at_yahoo.com> writes:
>
> > Concatenation can only use characters, if you use/return numbers it
dies. I
> > would encourage you to use the to_char function...
> >
> > I had this problem when doing the following: insert into cube_doc
values('
> > <dtsstart>'||cast(nmopmgt_conv_date(v_p_dts_revised_start) as
> > varchar2)||'</dtsstart>');
> > And I fixed my problem doing this, instead: insert into cube_doc
values('
> > <dtsstart>'||cast(nmopmgt_conv_date(to_char(v_p_dts_revised_start)) as
> > varchar2)||'</dtsstart>');
> >
> > Hope this helps.
> >
> > Alex Ivascu
> > Oracle/SQL DBA
> >
> >
> >
> > "Roy" <something_at_something.here> wrote in message
> > news:a1c3mk$m4l$1_at_news1.xs4all.nl...
> > > 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
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
>
> --
> Rick Wessman
> Security Assurance Group
> Oracle Corporation
> Rick.Wessman_at_oracle.com
>
> The opinions expressed above are mine and do not necessarily reflect
> those of Oracle Corporation.
Received on Mon Jan 07 2002 - 11:19:58 CST