My lovely complicated SQL crashes with ORA-00600: internal[qerpfAllocateX2]

ORACLE 9201
Hi all
I wrote a nice query to look for combinations of transactions using a "connect by prior" to arrange a half-cartesian join, then look for all connected paths that were a certain depth and whose nodes added up to a certain value. It works great and has tested out fine in the debug runs I've given it, but it is falling over in live with the following weird error:
ORA-00600: internal error code, arguments: [qerpfAllocateX2], [4038], [4028], [], [], [], [], []
I was originally getting this and I solved it during debug, using a WITH statement rather than twice doing a nested select on my source table.. I double checked and I'm using the WITH verison (in PL/SQL)
What I dont get, is I can run it straight from e.g. Visual Studio just fine, but when my PL/SQL code calls into the function, it all falls apart with this error. Is there anything I can do to help investigate the cause or to fix?
The original thread, where you guys helped me write the SQL, is: Re: A little help writing an SQL please? May need some advanced functionality..
Regards
cj
Edited by: charred on Sep 15, 2008 8:05 AM

If you are running on 9i this could be as a result of a known database bug.
"A query may fail with ORA-600[qerpfAllocateX2] when the prefetch size exceeds the sort buffersize."
Bug: 2277191
Fixed in 10g or > v9202
With most ORA-600 errors, the only solution available is to contact Oracle Support or try and re-write the query to use different access methods (plans).
Christopher Soza
Oracle BI DBA
Orix Consultancy Services Ltd
http://sozaman.blogspot.com

Similar Messages

Export terminated with ORA-00600: internal error code, arguments: [kcfrbd_1

when i am taking an export of a particular table , i got following message. please help
ORA-00600: internal error code, arguments: [kcfrbd_1], [0], [400], [], [], [], [], []
Export terminated successfully with warnings.

with out a versioninfo it's not possible tomgive appropiate information. Anyway, an ORA-00600 is almost certainly a job for the oracle support.
And lastly, the right forum for this question would be a database forum, maybe the Database-General-forum.

ORA-00600: internal error code, arguments: [ktsircinfo_num1]

While taking export of a table received EXP error and while dropping/selecting the same gor ora-600 errors.
. . exporting table TEST4
EXP-00003: no storage definition found for segment(29, 371385)
SQL >Drop table test4 cascade;
ORA-00600: internal error code, arguments: [ktsircinfo_num1], [29], [29], [371385], [], [], [], []
sql> Desc test4;
ORA-00600: internal error code, arguments: [ktsircinfo_num1], [29], [29], [371385], [], [], [], []
I dont want to log TAR with oracle right now... I tried dropping and recreating Undo tablespace but still did not help much . Database version is 9204

hi
read metalink ID - 153788.1
CHeers

Database crashed with error ORA-00600: internal error code, arguments

Hi,
Yesterday night one of our database was crashed and when I see the altert log file I found below errors
Oracle 10g, AIX 5.3 platform
Killing background process QMNC
Tue Oct 14 20:22:07
Errors in file /oracle/SID/saptrace/usertrace/sid_ora_6492356.trc:
ORA-00600: internal error code, arguments: [ksb_shut_detached_process3], [QMNC], [], [], [], [], [], []
Tue Oct 14 21:02:27 2008
Adjusting the default value of parameter parallel_max_servers
from 320 to 65 due to the value of parameter processes (80).
trace file contains below errors
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [ksb_shut_detached_process3], [QMNC], [], [], [], [], [], []
      Call Stack Trace
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
ksedst+001c          bl       ksedst1              700000010008000 ?
                                                   700000069243690 ?
ksedmp+0290          bl       ksedst               104325D68 ?
ksfdmp+0018          bl       03F599D0
Anyone has any idea regarding this error?
Now the database is up, but would like to know why this has happened.
Thank you
KVR
Edited by: KVR on Oct 15, 2008 10:03 AM

Theres plenty of notes about ORA-00600... all depending on what is you Oracle version and what was running when the crash happen.
If it was during the night maybe the system was updating statistics then you can check SAP Note 365421 ORA-00600 [1113] when generating statistics
Regards
Juan

SQL*Loader error ORA-00600 and ORA-26095

Hi all,
We have a problem with the SQL*Loader Utility. We use an 8i-Database (8.1.7) and SQL*Loader 9.2.0.1.0. We have no Trims or other functions active in the control file and do a direct path load.
It used to work properly until this morning.
Now we have the following errors (it is in German - but I can translate it):
Satz 90153: Abgelehnt - Fehler in Tabelle SCHEMA1.T_IMPORT.
ORA-00600: Interner Fehlercode, Argumente: [klaprs_50], [7], [], [], [], [], [], []
... about 50 equal errors
Specify SKIP=90171 when continuing the load.
SQL*Loader-926: OCI-Fehler; uldlm:OCIDirPathFinish fÃ¼r Tabelle SCHEMA1.T_IMPORT
ORA-26095: Nicht verarbeitete Stream-Daten vorhanden
SQL*Loader-2026: Der Ladevorgang wurde abgebrochen, weil er nicht fortgesetzt werden kann.
Specify SKIP=90171 when continuing the load.
Trnaslation:
00600 - Internal error code, arguments: ...
OCI-Fehler = OCI error
fÃ¼r Tabelle = for table
ORA-26095: Nicht verarbeitete Stream-Daten vorhanden = Non processed stream data existing
SQL*Loader-2026: Der Ladevorgang wurde abgebrochen, weil er nicht fortgesetzt werden kann. = Load process has been cancelled as it cannot be continued.
Has anyone got a clue?!?!?!

Hi,
It's very clear that import 9i is for an import into 9i database.
Upgrade 8i to 9i indicates that we can make an export 8i from 8i database and import 9i into 9i database, but never use a tools like export from other version...
If you want import data from 9i database into 8i use exp tools 8i, and imp 8i.
I devise you to read Metalink note 132904.1 - compatibility matrix for export & import between different oracl version.
Nicolas.

XMLQuery SQL Error: ORA-00600: internal error code,

Hi guys,
I am trying to use XML feature of Oracle DB. What I am trying to implement is having XMLTYpe field in table and have some values in it and then query that table using XMLQuery(...). I started with example here : http://www.psoug.org/reference/xmlquery.html .
I am able to create table, Insert data into table, but when I tried to run SELECT query it does not work
"SELECT person_id, XMLQuery(
'for $i in /PDRecord
where $i /PDName = "Daniel Morgan"
order by $i/PDName
return $i/PDName'
passing by value person_data
RETURNING CONTENT) XMLData
FROM person_data; "
It throws error like
"Error report:
SQL Error: ORA-00600: internal error code, arguments: [qmxqrwRewExpr:1], [], [], [], [], [], [], []
00600. 00000 - "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
Am I missing any thing? or is my Oracle 10g DB is not compatible with XMLType ?
Please help.

Hi Marco,
Thanks for replying.
Oracle Database 10g Release 10.2.0.1.0 - Production. so as per you said it should work. I am sorry for being dumb, but I am not DBA guy. can you tell me how to check if XMLDB is installed properly? how can I look at DBA_REGISTRY and what kind of information I will find under DBA_REGISTRY?
BTW I found another way of querying XMLType columns from here http://download.oracle.com/docs/cd/B10501_01/appdev.920/a96620/xdb04cre.htm which uses extract(), existsNode(), etc.. function to accomplish some of the task. As of now I am still digging in it, so not sure which one will be better to use. I mean the link that I showed on my first thread or the above link.
I am still curious why wouldnt my first thread query work.
Thanks again.

Ora-12801 with ora - 00600 urgent

Hi dear
I just migrate my dataabse from oracle 8.1.7.4 to oracle 10g release 2
i m getting the error
ORA-12801: error signaled in parallel query server P000
ORA-00600: internal error code, arguments: [xtycsr3], [], [], [], [], [], [], []
when i save the new record it's work fine but when i save the record the modify mode it give the above error
i m using form 6i
O/s win 2000 server
Kindly suggest the solution urgently i m on production database
Regards
Tarun Mittal

Symptoms:
Internal Error may occur (ORA-600)
ORA-600 [xtycsr3]
Related To:
Parallel Query (PQO)
Description
Select with GROUP BY may result in ORA-600[xtycsr3]
on a parallel slave process, if select list contains
a PLSQL function call on aggregation operators.
Eg:
SELECT 1, b.x, xty_func( max(1),SUM(100))
FROM xty b
GROUP BY 1, b.x;
The full bug text (if published) can be seen at Bug 2459355
This link will not work for UNPUBLISHED bugs.

Instance crashing with ORA-00469: CKPT process terminated with error

Hi,
Instance crashing with ORA-00469: CKPT process terminated with error on 10.2.0.4. Any possibe causes?
Thanks,
Madhav

I did check alert log and trace files. I just find this in alert log:
ORA-00469: CKPT process terminated with error
Trace file:
*** 2009-07-29 02:22:06.840
*** SERVICE NAME:(SYS$BACKGROUND) 2009-07-29 02:22:06.839
*** SESSION ID:(275.1) 2009-07-29 02:22:06.839
error 469 detected in background process
ORA-00469: CKPT process terminated with error

Ora_m000 consuming 100% cpu with ORA-00600 [kcbz_check_objd_typ_3], [0]

Hello,
I have been trying to troubleshoot high cpu usage in our Ebiz R12 environment where cpu is running 100% by ora_m000 process and I see ORA-00600 in alert log.
I have tried work around from metalink note 466049.1 and even applied fixed for patch 4430244, 5752105 but it hasn't fixed the issue.
Before going through opening a ticket with support, I thought try my luck here. I'd really appreciate any suggestions to fix this problem.
content of trace file.
*** KEWROCISTMTEXEC - encountered error: (ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_3], [0], [0], [1], [], [], [], [])
*** SQLSTR: total-len=176, dump-len=176,
STR={insert into wrh$_sysstat (snap_id, dbid, instance_number, stat_id, value) select :snap_id, :dbid, :instance_number, stat_id, value from v$sysstat order by stat_id}
*** KEWRAFM1: Error=13509 encountered by kewrfteh

What's your database version in four decimal places?
ORA-600 is Oracle internal error you need to work with Oracle support to fix the problem.
Also use "Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool"
The lookup tool will show you the known bug related to the error message.

This query worked, then it didn't with ORA-00600

select decode (level, -1, -1, -1) initial_level,
level node_depth,
decode (level, 0, parent_id, child_id)||' '||rule_desc node_label,
'expand' node_icon,
child_id node_data,
parent_id node_parent
from rule_tree, rule_master
where rm_id = child_id
start with nvl(parent_id,' ') = 'MASTER'
connect by parent_id = prior child_id
select decode (level, -1, -1, -1) initial_level,
ERROR at line 1:
ORA-00600: internal error code, arguments: [12406], [], [], [], [], [], [], []
Anyone know why this code once worked but now doesn't and what does the error mean?

http://download.oracle.com/docs/cd/B19306_01/server.102/b14219/e0.htm#sthref371
http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-00600%3A+internal+error+code&objID=c84&dateRange=all&userID=&numResults=15&rankBy=10001

ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [],

Question by Oracler:
10.2.0.4 Linux RAC
ORA-00600: internal error code, arguments: [12269], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [733], [1936597240], [pga heap], [], [], [], [], []
ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [], []
该数据库在NAT后，当前现象，用PL/SQL Developer 连接进行某个SQL 查询时，会直接报ORA-3113，但是在SQLPLUS 下是正常的。如何诊断？
Wed Aug 1 23:09:25 2012
Thread 1 advanced to log sequence 352 (LGWR switch)
Current log# 2 seq# 352 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Thu Aug 2 23:10:20 2012
Thread 1 advanced to log sequence 353 (LGWR switch)
Current log# 1 seq# 353 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Fri Aug 3 23:11:22 2012
Thread 1 advanced to log sequence 354 (LGWR switch)
Current log# 2 seq# 354 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Sat Aug 4 14:00:02 2012
Thread 1 advanced to log sequence 355 (LGWR switch)
Current log# 1 seq# 355 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Sun Aug 5 04:00:20 2012
Thread 1 advanced to log sequence 356 (LGWR switch)
Current log# 2 seq# 356 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Sun Aug 5 23:13:35 2012
Thread 1 advanced to log sequence 357 (LGWR switch)
Current log# 1 seq# 357 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Mon Aug 6 23:14:33 2012
Thread 1 advanced to log sequence 358 (LGWR switch)
Current log# 2 seq# 358 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Tue Aug 7 11:08:23 2012
Thread 1 advanced to log sequence 359 (LGWR switch)
Current log# 1 seq# 359 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Tue Aug 7 23:15:26 2012
Thread 1 advanced to log sequence 360 (LGWR switch)
Current log# 2 seq# 360 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Wed Aug 8 23:16:20 2012
Thread 1 advanced to log sequence 361 (LGWR switch)
Current log# 1 seq# 361 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Thu Aug 9 23:17:15 2012
Thread 1 advanced to log sequence 362 (LGWR switch)
Current log# 2 seq# 362 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Fri Aug 10 19:59:57 2012
Thread 1 advanced to log sequence 363 (LGWR switch)
Current log# 1 seq# 363 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Sat Aug 11 08:00:21 2012
Thread 1 advanced to log sequence 364 (LGWR switch)
Current log# 2 seq# 364 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Sat Aug 11 23:19:09 2012
Thread 1 advanced to log sequence 365 (LGWR switch)
Current log# 1 seq# 365 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Sun Aug 12 23:20:00 2012
Thread 1 advanced to log sequence 366 (LGWR switch)
Current log# 2 seq# 366 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Mon Aug 13 23:20:56 2012
Thread 1 advanced to log sequence 367 (LGWR switch)
Current log# 1 seq# 367 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Tue Aug 14 16:59:57 2012
Thread 1 advanced to log sequence 368 (LGWR switch)
Current log# 2 seq# 368 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Wed Aug 15 07:00:23 2012
Thread 1 advanced to log sequence 369 (LGWR switch)
Current log# 1 seq# 369 mem# 0: +DATA/orcl/onlinelog/group_1.257.766685683
Wed Aug 15 10:46:42 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orcl1_ora_26736.trc:
ORA-00600: internal error code, arguments: [12269], [], [], [], [], [], [], []
Wed Aug 15 10:46:43 2012
Trace dumping is performing id=[cdmp_20120815104643]
Wed Aug 15 10:47:57 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orcl1_ora_26736.trc:
ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [], []
Wed Aug 15 10:47:58 2012
Trace dumping is performing id=[cdmp_20120815104758]
Wed Aug 15 10:54:03 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orcl1_ora_26736.trc:
ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [], []
Wed Aug 15 10:54:04 2012
Trace dumping is performing id=[cdmp_20120815105404]
Wed Aug 15 10:55:10 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orcl1_ora_26736.trc:
ORA-00600: internal error code, arguments: [733], [1936597240], [pga heap], [], [], [], [], []
Wed Aug 15 10:55:11 2012
Trace dumping is performing id=[cdmp_20120815105511]
Wed Aug 15 10:56:11 2012
WARNING: inbound connection timed out (ORA-3136)
Wed Aug 15 14:19:17 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orcl1_ora_6528.trc:
ORA-00600: internal error code, arguments: [12316], [], [], [], [], [], [], []
Wed Aug 15 14:19:18 2012
Trace dumping is performing id=[cdmp_20120815141918]
Wed Aug 15 15:24:14 2012
WARNING: inbound connection timed out (ORA-3136)
Wed Aug 15 22:00:07 2012
Thread 1 advanced to log sequence 370 (LGWR switch)
Current log# 2 seq# 370 mem# 0: +DATA/orcl/onlinelog/group_2.258.766685683
Thu Aug 16 09:38:40 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 09:45:08 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 10:18:16 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 10:18:22 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 10:38:57 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 13:46:42 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 13:51:09 2012
WARNING: inbound connection timed out (ORA-3136)
Thu Aug 16 14:12:58 2012
WARNING: inbound connection timed out (ORA-3136)
节点2
Wed Aug 15 03:00:42 2012
Thread 2 advanced to log sequence 571 (LGWR switch)
Current log# 3 seq# 571 mem# 0: +DATA/orcl/onlinelog/group_3.265.766686179
Wed Aug 15 10:47:03 2012
Trace dumping is performing id=[cdmp_20120815104643]
Wed Aug 15 10:48:18 2012
Trace dumping is performing id=[cdmp_20120815104758]
Wed Aug 15 10:54:24 2012
Trace dumping is performing id=[cdmp_20120815105404]
Wed Aug 15 10:55:31 2012
Trace dumping is performing id=[cdmp_20120815105511]
Wed Aug 15 13:12:29 2012
Thread 2 advanced to log sequence 572 (LGWR switch)
Current log# 4 seq# 572 mem# 0: +DATA/orcl/onlinelog/group_4.266.766686179
Wed Aug 15 14:19:38 2012
Trace dumping is performing id=[cdmp_20120815141918]
Wed Aug 15 22:00:10 2012
Thread 2 advanced to log sequence 573 (LGWR switch)
Current log# 3 seq# 573 mem# 0: +DATA/orcl/onlinelog/group_3.265.766686179
Thu Aug 16 13:13:48 2012
Thread 2 advanced to log sequence 574 (LGWR switch)
Current log# 4 seq# 574 mem# 0: +DATA/orcl/onlinelog/group_4.266.766686179
后续的验证，发现 sqldeveloper 3.0.04和 pl/sql developer 8.0.0.1483 在查询大表的时候都会报3113，唯有SQLPLUS 没问题。
目前定位于，PL/SQL DEV NAT后的数据库，31493 行的 ORA-3113，25463 行的正常返回。
最新进展，在服务器端设置
To enable tracing at the server, find the sqlnet.ora file for the server and create the following lines in it:
TRACE_TIMESTAMP_SERVER = ON
TRACE_LEVEL_SERVER = 16
TRACE_UNIQUE_SERVER = ON
后，本来3113 的查询可以正常出来了，但是关闭trace后，又不正常了。
Solution
问题最终定位在 CISCO ASA 防火墙的 SQLNet inspect，关闭就OK了。

ORA-00600 12333 usually means there was a communications error between the client and server. If you kill a session or perform a shutdown while a users connected you could potentially get this error. There's other reasons too. I think you're probably right that Oracle support will tell you to upgrade if you file a TAR with them.
Did this error crash your database or does it happen frequently? If the answer is no then I wouldn't worry about it unless the end user has said something about it. If this is a problem then I'd contact Oracle support.
I'm also running 8.1.7.2 and get maybe 1-2 of these errors a month from the same PC. In our case this error didn't correspond with a database shutdown or a killed session. We also tried reinstalling the client software and this didn't fix it either. I think our error may be because of this one PC being on a very old part of our network that probably needs upgrading.

ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [],

ORA-00600: Occurred in production database. I did not contact oracle support yet, because I know they will ask to upgrade or apply a patch. I want do that as a last resort. Do you see any other reason for this ORA-600 error or solution?
Thanks.
part of trace file:
Dump file /tmp/rmsdv84_ora_11548.trc
Oracle8i Enterprise Edition Release 8.1.7.2.0 - Production
With the Partitioning option
JServer Release 8.1.7.2.0 - Production
ORACLE_HOME = /usr/oracle/product/8.1.7
System name:     SunOS
Node name:     fcdb239
Release:     5.8
Version:     Generic_108528-12
Machine:     sun4u
Instance name: RMSDV84
Redo thread mounted by this instance: 1
Oracle process number: 32
Unix process pid: 11548, image: oracle@fcdb239 (TNS V1-V3)
*** SESSION ID:(34.1296) 2003-01-23 16:46:43.524
*** 2003-01-23 16:46:43.524
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [], [], []
Current SQL statement for this session:
SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp()+168 CALL ksedst()+0 230 ? 1 ? FFBED080 ?
FFBECB24 ? FFBECB08 ? 0 ?
kgeriv()+196 PTR_CALL 00000000 3 ? 0 ? 0 ? 258 ? 1 ? 302D ?

ORA-00600 12333 usually means there was a communications error between the client and server. If you kill a session or perform a shutdown while a users connected you could potentially get this error. There's other reasons too. I think you're probably right that Oracle support will tell you to upgrade if you file a TAR with them.
Did this error crash your database or does it happen frequently? If the answer is no then I wouldn't worry about it unless the end user has said something about it. If this is a problem then I'd contact Oracle support.
I'm also running 8.1.7.2 and get maybe 1-2 of these errors a month from the same PC. In our case this error didn't correspond with a database shutdown or a killed session. We also tried reinstalling the client software and this didn't fix it either. I think our error may be because of this one PC being on a very old part of our network that probably needs upgrading.

ORA-00600: internal error code, arguments: [kdddgb1], [0], [], [], [], [],

Dear all,
we are getting the following errors in our alert file.
Errors in file /oracle8i/oracle/app/admin/sbidpc8/udump/sbidpc8_ora_650.trc:
ORA-00600: internal error code, arguments: [kdddgb1], [0], [], [], [], [], [], []
The portion of trace file is also pasted here.
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kdddgb1], [0], [], [], [], [], [], []
Current SQL statement for this session:
UPDATE CORG SET UCD_CORG_BORRTYPECODE=:b1,UCD_CORG_RELATIONSHIPCODE=:b2,UCD_CORG_RELATIONTYPECODE=:b3,CORG_BUSINESSENTITYNAME=:b4,CORG_BORROWERTITLE=:b5,CORG_FIRSTNAME=:b6,CORG_MIDDLENAME1=:b7,CORG_MIDDLENAME2=:b8,CORG_MIDDLENAME3=:b9,CORG_LASTNAME=:b10,CORG_PAN=:b11,CORG_PERCENTAGECONTROL=:b12,CORG_ADDRESS1=:b13,CORG_ADDRESS2=:b14,CORG_ADDRESS3=:b15,CORG_TOWNCITYNAME=:b16,STDS_CORG_DISTCODE=:b17,STDS_CORG_STATECODE=:b18,CORG_PIN=:b19,SWFT_CORG_COUNTRYCODE=:b20,CORG_TELEPHONEAREACODE=:b21,CORG_TELEPHONE=:b22,CORG_EMAIL=:b23,CORG_WORTHAMT=:b24,CORG_RELINQUISHINGDATE=:b25 WHERE CUST_CORG_BRCD = :b26 AND CUST_CORG_CUSTID = :b27 AND PRDT_CORG_REPORTDATE = :b28 AND CORG_NAMEID = :b29
----- PL/SQL Call Stack -----
object line object
handle number name
f01520d0 1489 package body CIS.PKGUPLOAD
efa17d80 13 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp()+168 CALL ksedst()+0 540 ? 0 ? FFBF6570 ?
FFBF6014 ? FFBF5FF8 ? 0 ?
kgerinv()+184 PTR_CALL 00000000 3 ? 0 ? 0 ? 175DCEC ? 1 ?
FFBF6D7C ?
kgesinv()+20 CALL kgerinv()+0 186509C ? 18B7D4C ? 14B03BC ?
1 ? FFBF6D7C ? 1855270 ?
ksesin()+60 CALL kgesinv()+0 186509C ? 18B7D4C ? 175DCEC ?
1 ? FFBF6D7C ? F3329628 ?
kdddgb()+1496 CALL ksesin()+0 175DCEC ? 1 ? 0 ? 0 ? 0 ?
18AFDA1 ?
kdusru()+604 CALL kdddgb()+0 18AFCF4 ? 0 ? 2 ? 18AFCF4 ?
EF9EE640 ? 18AFD24 ?
kauupd()+148 CALL kdusru()+0 18AF25C ? 0 ? 18AFCF4 ? 0 ?
0 ? 18B0060 ?
updrow()+3744 CALL kauupd()+0 18AF258 ? 0 ? 18AFCF4 ? 0 ?
FFFF ? 1E ?
qerupFetch()+272 CALL updrow()+0 0 ? EF9F5DD4 ? 18AFCF4 ?
18AF258 ? 18AECC4 ? 18AFCF4 ?
updaul()+392 PTR_CALL 00000000 EF9F4138 ? 1867C84 ?
EF9F5DD4 ? 7FFF ? 186A604 ?
EF9EE640 ?
updexe()+232 CALL updaul()+0 EF9F7108 ? FFBF7B44 ?
1867C00 ? 1868000 ? 18AEA98 ?
18AEA94 ?
opiexe()+9440 CALL updexe()+0 EF9F7108 ? 0 ? 18AEA94 ?
18AECC4 ? 18AEA98 ? 18AECC4 ?
opipls()+9740 CALL opiexe()+0 18AEA94 ? EF9F7108 ? 4 ?
EF9F7108 ? 18BE3F0 ?
1911F98 ?
opiodr()+5688 PTR_CALL 00000000 1868000 ? 1A ? 18AEA90 ?
192F9F0 ? 2758920 ? 460 ?
rpidrus()+128 CALL opiodr()+0 1562F40 ? FFBF9664 ?
1869000 ? 44 ? 1597C1A ?
18BCBB8 ?
skgmstack()+156 PTR_CALL 00000000 FFBF974C ? FFBF9888 ? 1 ? 0 ?
0 ? 0 ?
rpidru()+140 CALL skgmstack()+0 FFBF986C ? 1864EF0 ? F618 ?
81121C ? FFBF9888 ?
EFA184B0 ?
rpiswu2()+608 PTR_CALL 00000000 FFBF9C7C ? 811384 ? 0 ?
FFBFDBEC ? 2E ? FE743EF4 ?
rpidrv()+2240 CALL rpiswu2()+0 FFBF9918 ? 1865000 ?
FFBF9BEC ? 2 ? FFBF9BE4 ?
2E ?
psddr0()+136 CALL rpidrv()+0 1911F98 ? 32 ? 4000 ?
1864C00 ? FFBF9C3C ?
1865000 ?
psdnal()+216 CALL psddr0()+0 FFBF9DC8 ? FFBF9D28 ?
FFBF9DC8 ? 30 ? 1660478 ?
1CC5D20 ?
pfrrun()+58188 PTR_CALL 00000000 FFBFBBFC ? FFBFBCC0 ? 0 ?
2E ? 2E ? 1 ?
peicnt()+324 CALL pfrrun()+0 74 ? 192F578 ? F01466E4 ?
11A ? FFBFBBFC ? 18BCBB8 ?
kkxexe()+468 CALL peicnt()+0 FFBFBBFC ? 18BCBB8 ?
18BCBB8 ? FFBFBBFC ?
FFBFBB2C ? 0 ?
opiexe()+11608 CALL kkxexe()+0 186A400 ? 18BCBB8 ?
7FFFFC00 ? 14B5800 ?
1864C00 ? EFA17D80 ?
opiall0()+4944 CALL opiexe()+0 0 ? EFA18A54 ? 4 ? EFA18A54 ?
1867C9C ? 18BCD1C ?
opial7()+324 CALL opiall0()+0 18BA5A4 ? FFBFD4F8 ?
1562920 ? 18BCD1C ? 3E ? 0 ?
opiodr()+5688 PTR_CALL 00000000 1 ? F ? FFBFF048 ? 18BCD1C ?
F1BCDAF4 ? F1B773D8 ?
ttcpip()+956 PTR_CALL 00000000 1562D50 ? FFBFD7EC ?
1869000 ? 1 ? 1597B9E ? 0 ?
opitsk()+664 CALL ttcpip()+0 1867C98 ? 1867D74 ? 1597B9E ?
FFBFE6AC ? FFBFE848 ? 0 ?
opiino()+1792 CALL opitsk()+0 0 ? 18669F0 ? 186946C ? 0 ?
1 ? 0 ?
opiodr()+5688 PTR_CALL 00000000 FFBFFA28 ? 80005000 ?
1867C00 ? 189AC58 ? 0 ?
1855270 ?
opidrv()+1316 CALL opiodr()+0 1562CA0 ? FFBFF62C ?
1869000 ? 0 ? 1597B72 ?
1872F7C ?
sou2o()+20 CALL opidrv()+0 3C ? FFBFF73C ? 1864C00 ?
FFBFF790 ? 0 ? 0 ?
main()+160 CALL sou2o()+0 FFBFFA38 ? 3C ? 4 ?
FFBFFA28 ? 165B614 ?
1872F7C ?
_start()+220 CALL main()+0 0 ? FFBFFBE4 ? 188A05C ?
1864C00 ? 0 ? 0 ?
----- Argument/Register Address Dump -----
Argument/Register addr=ffbf6570.
We request you to please look into this and help us out as early as possible.
One query we are having is that whether database will crash, because of these errors?
With regards
Rajesh Jain

Amit,
The doc id mentioned by Satish already,*138325.1* is the correct note for the error code of yours.As its not right to post the content of metalink material, I shall just say that you have hit a bug which is removed in the release of 10g. So you should upgrade to 10g and/or , post the trace files which are created by this error to Oracle Support. I am not sure that would work either as support for 8i is not there any more.
HTH
Aman....

ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [],

Dear all,
we are getting the following errors in our alert file.
Errors in file /oracle8i/oracle/app/admin/sbidpc8/udump/sbidpc8_ora_650.trc:
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], []
Current SQL statement for this session:
UPDATE CORG SET UCD_CORG_BORRTYPECODE=:b1,UCD_CORG_RELATIONSHIPCODE=:b2,UCD_CORG_RELATIONTYPECODE=:b3,CORG_BUSINESSENTITYNAME=:b4,CORG_BORROWERTITLE=:b5,CORG_FIRSTNAME=:b6,CORG_MIDDLENAME1=:b7,CORG_MIDDLENAME2=:b8,CORG_MIDDLENAME3=:b9,CORG_LASTNAME=:b10,CORG_PAN=:b11,CORG_PERCENTAGECONTROL=:b12,CORG_ADDRESS1=:b13,CORG_ADDRESS2=:b14,CORG_ADDRESS3=:b15,CORG_TOWNCITYNAME=:b16,STDS_CORG_DISTCODE=:b17,STDS_CORG_STATECODE=:b18,CORG_PIN=:b19,SWFT_CORG_COUNTRYCODE=:b20,CORG_TELEPHONEAREACODE=:b21,CORG_TELEPHONE=:b22,CORG_EMAIL=:b23,CORG_WORTHAMT=:b24,CORG_RELINQUISHINGDATE=:b25 WHERE CUST_CORG_BRCD = :b26 AND CUST_CORG_CUSTID = :b27 AND PRDT_CORG_REPORTDATE = :b28 AND CORG_NAMEID = :b29
----- PL/SQL Call Stack -----
object line object
handle number name
f01520d0 1489 package body CIS.PKGUPLOAD
efa17d80 13 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp()+168 CALL ksedst()+0 540 ? 0 ? FFBF6FA8 ?
FFBF6A4C ? FFBF6A30 ? 0 ?
kgeriv()+196 PTR_CALL 00000000 3 ? 0 ? 0 ? 258 ? 1 ? 42C2 ?
kgesiv()+96 CALL kgeriv()+0 186509C ? 18B7D4C ? 14B03BC ?
0 ? FFBF77C8 ? 1855270 ?
kgesic0()+32 CALL kgesiv()+0 186509C ? 18B7D4C ? 42C2 ?
0 ? FFBF77C8 ? 1855270 ?
updrow()+2280 CALL kgerse()+0 186509C ? 18B7D4C ? 42C2 ?
833CE4 ? FFBF6D7C ? 0 ?
qerupFetch()+272 CALL updrow()+0 18AFCF4 ? EF9F5DD4 ?
18AFCF4 ? 18AF258 ? 18AECC4 ?
18AFCF4 ?
updaul()+392 PTR_CALL 00000000 EF9F4138 ? 1867C84 ?
EF9F5DD4 ? 7FFF ? 186A604 ?
EF9EE640 ?
updexe()+232 CALL updaul()+0 EF9F7108 ? FFBF7B44 ?
1867C00 ? 1868000 ? 18AEA98 ?
18AEA94 ?
opiexe()+9440 CALL updexe()+0 EF9F7108 ? 0 ? 18AEA94 ?
18AECC4 ? 18AEA98 ? 18AECC4 ?
opipls()+9740 CALL opiexe()+0 18AEA94 ? EF9F7108 ? 4 ?
EF9F7108 ? 18BE3F0 ?
1911F98 ?
opiodr()+5688 PTR_CALL 00000000 1868000 ? 1A ? 18AEA90 ?
192F9F0 ? 2758920 ? 460 ?
rpidrus()+128 CALL opiodr()+0 1562F40 ? FFBF9664 ?
1869000 ? 44 ? 1597C1A ?
18BCBB8 ?
skgmstack()+156 PTR_CALL 00000000 FFBF974C ? FFBF9888 ? 1 ? 0 ?
0 ? 0 ?
rpidru()+140 CALL skgmstack()+0 FFBF986C ? 1864EF0 ? F618 ?
81121C ? FFBF9888 ?
EFA184B0 ?
rpiswu2()+608 PTR_CALL 00000000 FFBF9C7C ? 811384 ? 0 ?
FFBFDBEC ? 2E ? FE743EF4 ?
rpidrv()+2240 CALL rpiswu2()+0 FFBF9918 ? 1865000 ?
FFBF9BEC ? 2 ? FFBF9BE4 ?
2E ?
psddr0()+136 CALL rpidrv()+0 1911F98 ? 32 ? 4000 ?
1864C00 ? FFBF9C3C ?
1865000 ?
psdnal()+216 CALL psddr0()+0 FFBF9DC8 ? FFBF9D28 ?
FFBF9DC8 ? 30 ? 1660478 ?
1CC5D20 ?
pfrrun()+58188 PTR_CALL 00000000 FFBFBBFC ? FFBFBCC0 ? 0 ?
2E ? 2E ? 1 ?
peicnt()+324 CALL pfrrun()+0 74 ? 192F578 ? F01466E4 ?
11A ? FFBFBBFC ? 18BCBB8 ?
kkxexe()+468 CALL peicnt()+0 FFBFBBFC ? 18BCBB8 ?
18BCBB8 ? FFBFBBFC ?
FFBFBB2C ? 0 ?
opiexe()+11608 CALL kkxexe()+0 186A400 ? 18BCBB8 ?
7FFFFC00 ? 14B5800 ?
1864C00 ? EFA17D80 ?
opiall0()+4944 CALL opiexe()+0 0 ? EFA18A54 ? 4 ? EFA18A54 ?
1867C9C ? 18BCD1C ?
opial7()+324 CALL opiall0()+0 18BA5A4 ? FFBFD4F8 ?
1562920 ? 18BCD1C ? 3E ? 0 ?
opiodr()+5688 PTR_CALL 00000000 1 ? F ? FFBFF048 ? 18BCD1C ?
F1BCDAF4 ? F1B773D8 ?
ttcpip()+956 PTR_CALL 00000000 1562D50 ? FFBFD7EC ?
1869000 ? 1 ? 1597B9E ? 0 ?
opitsk()+664 CALL ttcpip()+0 1867C98 ? 1867D74 ? 1597B9E ?
FFBFE6AC ? FFBFE848 ? 0 ?
opiino()+1792 CALL opitsk()+0 0 ? 18669F0 ? 186946C ? 0 ?
1 ? 0 ?
opiodr()+5688 PTR_CALL 00000000 FFBFFA28 ? 80005000 ?
1867C00 ? 189AC58 ? 0 ?
1855270 ?
opidrv()+1316 CALL opiodr()+0 1562CA0 ? FFBFF62C ?
1869000 ? 0 ? 1597B72 ?
1872F7C ?
sou2o()+20 CALL opidrv()+0 3C ? FFBFF73C ? 1864C00 ?
FFBFF790 ? 0 ? 0 ?
main()+160 CALL sou2o()+0 FFBFFA38 ? 3C ? 4 ?
FFBFFA28 ? 165B614 ?
1872F7C ?
_start()+220 CALL main()+0 0 ? FFBFFBE4 ? 188A05C ?
1864C00 ? 0 ? 0 ?
----- Argument/Register Address Dump -----
Argument/Register addr=ffbf6fa8.
We request you to please look into this and help us out as early as possible.
One query we are having is that whether database will crash, because of these errors?
With regards
Rajesh Jain

ORA-600 = go to http://metalink.oracle.com
Would it be possible to pick a thread to tell that at the top of this forum ?
Fred

ORA-00600: internal error while running procedure in oracle 7.3.4

I am using Oracle 7.3.4 running on HP-Unix. While running a procedure, I am getting the following error.
ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL execution], [], [], [], [], [], []
ORA-06544: PL/SQL: internal error, arguments: [77102], [], [], [], [], [], [], []
ORA-06553: PLS-801: internal error [77102]
Please suggest what could be the problem. Incidentally, the same procedure is running on another installation of Oracle 7.3.4. I am unable to find out what could be the difference between the 2 Oracle instances that is causing this problem.
Please help.
Thanks in advance.

Are there any trace files created on the server?
Did you see if they have any more information?
Generally, these types of errors suggest contacting Oracle support to resolve the issue, but with the Oracle version you are using being already desupported, it would be an issue.
Alternatively, you could search metalink to see if there is any support note on this type of error.

My lovely complicated SQL crashes with ORA-00600: internal[qerpfAllocateX2]

Similar Messages

Maybe you are looking for