ora-00600 [12700] on SYS.EXU8REF

**Ron** · Jun 27 '08, 05:58 PM

Re: ora-00600 [12700] on SYS.EXU8REF

Shalom Doron,

Here you go:

Use dbms_utility.DA TA_BLOCK_ADDRES S_BLOCK and dbms_utility.
DATA_BLOCK_ADDR ESS_FILE to get file and block.

On metalink. please check below article:

Doc ID: Note:155933.1
Subject: Resolving an ORA-600 [12700] error in Oracle 8 and
above.
Type: HOWTO
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 24-AUG-2001
Last Revision Date: 24-NOV-2003

Regards,

Ron
DBA Infopower

Enteros, Inc | Production Database Performance Management for RDBMS /

http://www.dbainfopower.com

Enteros provides comprehensive software solutions and IT consulting services to help businesses achieve optimal results. Contact us today to learn more.

Standard disclaimer:

404 Not Found

http://www.dbainfopower.com/dbaip_advice_disclaimer.html

"Doron" <doron_almog@ms n.comwrote in message
news:995517bc.0 402131132.30c70 eed@posting.goo gle.com...

I'm getting a ORA-00600 [12700]error on SYS.EXU8REF (see trace file
below).
>
SYS.EXU8REF is a view so the problem should be with one of the
underlaying tables. i didnt run oerr12700 yet. can i find the
object/block that is giving the error via the RDBA? if so then how?
>
any suggestions appreciated!
>
>
>
*************** ****TRACE FILE STARTS
HERE*********** *************** ********
Dump file C:\oracle\admin \pdm\udump\ORA0 0660.TRC
Tue Feb 10 16:59:26 2004
ORACLE V8.1.7.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.0 Service Pack 3, CPU type 586
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
JServer Release 8.1.7.0.0 - Production
Windows 2000 Version 5.0 Service Pack 3, CPU type 586
Instance name: pdm
>
Redo thread mounted by this instance: 1
>
Oracle process number: 12
>
Windows thread id: 660, image: ORACLE.EXE
>
>
*** SESSION ID:(11.4313) 2004-02-10 16:59:26.289
*** 2004-02-10 16:59:26.289
ksedmp: internal or fatal error
ORA-00600: código de erro interno, argumentos: [12700], [18],
[4208467], [54], [], [], [], []
Current SQL statement for this session:
SELECT OWNER, TNAME, ROWNER, RTNAME, CNAME, CNO, RCNO, ACTION,
ENABLED, DEFER, OBJID, PROPERTY , REFTYPE FROM SYS.EXU8REF
WHERE OWNERID=:1
----- Call Stack Trace -----
calling call entry
argument values in hex
location type point
(? means dubious value)
-------------------- -------- --------------------
----------------------------
_ksedmp+a8 CALLrel _ksedst+0
>
043D428
_ksfdmp+e CALLrel _ksedmp+0
3
_kgeriv+95 CALLreg 00000000
>
BE190
>
3
_kgeasi+67 CALLrel _kgeriv+0
>
B3F00
>
204BC81C
>
319C
>
3
>
2043D5A0
_qertbFetchByRo wID+5ac CALLrel _kgeasi+0
>
BE190
>
204BC81C
>
319C
>
2 3 0
>
12 0
>
403753
>
0 36
_qerjoFetch+16a CALL??? 00000000
>
B6F41C
>
0 0 1
_qervwFetch+7b CALL??? 00000000
_qerjoFetch+301 CALL??? 00000000
>
B6F188
>
0 0 1
_qerjoFetch+301 CALL??? 00000000
>
B6EFD8
>
C533B0
>
2043D7C4
>
1
_qerjoFetch+301 CALL??? 00000000
>
B6EE18
>
0 0 1
_qerjoFetch+301 CALL??? 00000000
>
B6EC68
>
0 0 1
_qerjoFetch+301 CALL??? 00000000
>
99C384
>
0 0 1
_qerjoFetch+301 CALL??? 00000000
>
99C1D4
>
0 0 1
_qerjoFetch+301 CALL??? 00000000
>
99C024
>
0 0 1
_opifch+c0f CALL??? 00000000
>
99C000
>
AE4E20
>
2043DCAC
>
1
_opiall0+d11 CALLrel _opifch+0
5 2
>
2043DD60
_opial7+153 CALLrel _opiall0+0
_opiodr+506 CALLreg 00000000
47 F
>
2043EF80
_ttcpip+df8 CALLreg 00000000
47 F
>
2043EF80
>
3
_opitsk+608 CALLrel _ttcpip+0
_opiino+50c CALLrel _opitsk+0
0
_opiodr+506 CALLreg 00000000
3C 4
>
2043FBF8
_opidrv+384 CALLrel _opiodr+0
3C 4
>
2043FBF8
>
0
_sou2o+19 CALLrel _opidrv+0
_opimai+10c CALLrel _sou2o+0
_OracleThreadSt art@4+49f CALLrel _opimai+0
2
>
2043FE74
77E887DA CALLreg 00000000

ora-00600 [12700] on SYS.EXU8REF

ora-00600 [12700] on SYS.EXU8REF

Comment