ORA-00600: internal error code, arguments: [4000], [13824] , [], [], [], []

Hi
I am getting following error while issuing below query on production DB server.
Please help me out.
select * from ss_ntl_other_inc_det where ntl_seq_no=4071205129
ERROR at line 1:
ORA-00600: internal error code, arguments: [4000], [13824], [], [], [], [], [],
Thanks and Regards

....theres an ora600 lookup tool which helios posted. Always hit this first. maybe someone made a change that needs to be reversed? could find it in seconds with the 600 lookup tool. Always, always, always lookup that tool first. If it doesnt help only THEN log an SR.
If the error is found in 600 lookup tool, the support engineer would only point you at that anyway which means you wasted minutes or even hours logging the call and waiting for the engineer to come back.
I was on support anyway so had a look and that error is in the 600 lookup tool. OP, look it up.

Similar Messages

Err#-600 msg ORA-00600: internal error code, arguments: [4000], [7089]

Hi All,
I am getting the error "Err#-600 msg ORA-00600: internal error code, arguments: [4000], [7089]" while running a package. Could not able to get detailed info on this. Please someone help in resolving the above error.
Thanks,
Karthi

http://orafaq.com/wiki/ORA-00600
You can follow Nikolay's advice or try to find a workaround yourself by rewriting your query using a somehow different approach
Regards
Etbin

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 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

ORA-00600: internal error code, arguments: [unable to load XDB library]

hi everybody ;
i have 9.2.0.7 db runs on SLES9 on host A. and i take full rman database backup to make a new database on different host ( host B ) with different file structure. ( sid is the same ) i had already 1 database on host B. after this duplicate now there are 2 database on host B.
i take daily full database rman backup on the new host for my new database and there is no problem. when i try to take extra full export backup i get an error ;
Dynamic link error: libxdb.so: cannot open shared object file: No such file or directory
*** 2010-08-05 09:46:12.868
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [unable to load XDB library], [], [], [], [], [], [], []
as i search ; i have to stop the database and listener and set the LD_LIBRARY_PATH variable. how can i make this without make any mistake for the first database runs on Host B.
because 2 database must be up and running on host B. can you explaın these operation step by step ?
thank you ....

craft wrote:
any idea ?
>any idea ?
your database is out off support you should consider to upgrade. ORA-00600 indicate for bug

ORA-00600: internal error code, arguments: [25012], [19], [21], [], [], [],

when i execute dbcheck in db13, i receive this message:
ORA-00600: internal error code, arguments: [25012], [19], [21], [], [], [], [], []
i have Oracle 9.2.0 and i don't find any note in the OSS notes.

This may point you in the right direction?
Look at Note 758563 - Oracle Metalink access for SAP customers.
Oracle Metalink WebSite is:
https://metalink.oracle.com/metalink/plsql/f?p=200:101:5428529246127535152
Metalink Username and Password deleted by Moderator.
Please do not post this kind of information in the forum.
Thanks.
Then do a search on ORA-00600: internal error code, arguments: [25012]
This should get you started.
Message was edited by: Christian Graf

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

Can anyone please try check out this ORA-600 error, ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59DA4],
[2], [], [], [], [], [].
My db went down abruptly due to power source ....now the database mounts successfully but when u try opening the db i.e. alter database open; it comes up with the error. Plz kindly treat urgently.Thanks

For all kind of internal errors, you should open SR (Service Request) in metalink. You need to contact Oracle Support
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com
[Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

ORA-00600: internal error code, arguments: [kksscl-inf-inl-loop], [2500]

Hi people,
Do you have any idea about this error: ORA-00600: internal error code, arguments: [kksscl-inf-inl-loop], [2500], [6], [40], [85], [85], [], [].
Thanks in advance.
Marcos Freitas

Duplicate Thread:
ORA-00600: internal error code, arguments: [kksscl-inf-inl-loop], [2500]
C.

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

Could you tell me to to handle the following error?
ORA-00600: internal error code, arguments: [12333], [0], [0], [3], [], [], [], []
Thanks a lot

Could you please give me more detail information?
Thanks

ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [],.....

Hi,
While connecting with database, I got the following error,
ORA-00600: internal error code, arguments: [ttcgcshnd-1], [0], [], [], [], [], [], []
I am using oracle 9i. Can anyone tell me the solution of that error ?
Thanks and Regards,
Hiren

many people are here because they lack that optionIt's not false, indeed, but if nobody had the same error, there is no chance to solve it.
At least a complete system/operation description is necessary to indicates some valid ways to investigate.
Nicolas.

ORA-00600: internal error code, arguments: [ktbdchk1: bad dscn], [], [], []

Hi,
Can anyone tell me how to resolve this error
ORA-00600: internal error code, arguments: [ktbdchk1: bad dscn], [], [], [], [], [], [], []
ORA-06512: at "ProcName", line 7
ORA-06512: at line 17
thx

Most of this type of errors (ORA-600) you need report to Oracle Support or check the metalink for released fix or possible workaround.
Anyway this error is fixed in:
10.1.0.4 patchset
9.2.0.7 patchset (released for Windows only, for other platforms expecting soon)
10gR2 (not released yet)

ORA-00600: internal error code, arguments: [kglpin-bad-lock], [0x70000062E067FC8], [], [], [], [], [], [], [], [], [], []

Hi,
Using owb 11.2.0.3 and encountering
ORA-00600: internal error code, arguments: [kglpin-bad-lock], [0x70000062E067FC8], [], [], [], [], [], [], [], [], [], []
this error when a proces sflow runs a mapping.
It fails and data remains unchanged.
When proces sflow next runs it succeeds.
Any ideas?
Thanks

Don't multipost, please. Stay in your original thread ORA-00600: internal error code, arguments: [kglpin-bad-lock], [0x70000062E067FC8], [], [], [], [], [], [], [], [], [], […
Mod: locking.

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: [kqlidp0:no user], [258], [], []

Hi,
Does anyone has solution to the below problem
ORA-00600: internal error code, arguments: [kqlidp0:no user], [258], [], []
Thanks and Regards

That we have already researched earlier but we are trying to find out exact solution as per second argument ...is taken. Because for first argument a bug already exists and it is resolved if we apply the interim patch .What is the bug/patch number you are referring to?
Tell me one thing ...
if an ORA -600 error has ORA-00600: internal error code, arguments: [kqlidp0:no user], [258], [], []
and the patch is available for ORA-00600: internal error code, arguments: [kqlidp0:no user], [1292], [], []
Can we apply that RDBMS server patch for 11.1.0.7 database...Yes.
Thanks,
Hussein

ORA-00600: internal error code, arguments: [4000], [13824] , [], [], [], []

Similar Messages

Maybe you are looking for