| << Back to previous view |
|
[QA-34] ORA-00600 [kddummy_blkchk] while dropping UNDO segment. Created: 08/Nov/07 Updated: 08/Nov/07 |
|
| Status: | Closed |
| Project: | Questions & Answers |
| Fix Version/s: | None |
| Type: | Oracle - Internals | Priority: | Blocker |
| Reporter: | ubTools Support | Assignee: | ubTools Support |
| Resolution: | Answered | Votes: | 0 |
| Product Version: | Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production |
| Operating System: | IBM-AIX |
| Description |
While dropping an offlined UNDO segment (by _offline_rollback_segments), the following error appeared:
SQL> drop rollback segment "_SYSSMU85$"; > > drop rollback segment "_SYSSMU85$" > * > ERROR at line 1: > ORA-00607: Internal error occurred while making a change to a data block > ORA-00600: internal error code, arguments: [kddummy_blkchk], [2], [846985], > [38508], [], [], [], [] Then, the instance crashed. After re-starting the instance, it crashed again. Stack trace: ORA-00600: internal error code, arguments: [kddummy_blkchk], [2], [846985], [38508], [], [], [], []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst+001c bl ksedst1 FFFFFFFFFFF9D10 ? 000000000 ?
ksedmp+0290 bl ksedst 1047C9C10 ?
ksfdmp+0018 bl 03F53584
kgerinv+00dc bl _ptrgl
kseinpre+0040 bl kgerinv 110040AA0 ? 000000000 ?
1048470A0 ? 07FFFFFFF ?
000000000 ?
ksesin+0048 bl kseinpre 1048470A0 ? 07FFFFFFF ?
000000000 ?
kco_blkchk+0778 bl ksesin 10484752C ? 300000003 ?
000000000 ? 000000002 ?
000000000 ? 0000CEC89 ?
000000000 ? 00000966C ?
kcoapl+0d24 bl kco_blkchk FFF00FFFFFFA310 ?
284422800B4E4358 ?
102FD4FDC ? 7000001F5151F50 ?
000000080 ?
kcbapl+0178 bl kcoapl FFFFFFFFFFFC218 ?
7000001E815A000 ? 100000001 ?
7FFFFFFF000000F7 ?
200000000000 ? 20BD260C8 ?
000000000 ?
kcrfw_redo_gen+2964 bl kcbapl 000000000 ? 000000000 ?
000000000 ? 000000000 ?
000000000 ?
kcbchg1_main+25e0 bl kcrfw_redo_gen 102DA5AC7 ?
2D30491F0A2889F8 ?
FFFFFFFFFFFAB20 ?
700000010008000 ? 1000024A4 ?
000000001 ? 400000000000001 ?
000000000 ?
kcbchg1+038c bl kcbchg1_main 000000000 ? 0000001F4 ?
000000000 ? 110366678 ?
0000023A0 ? 70000020B29AFD8 ?
ktbchgro+0380 bl kcbchg1 00A288AD0 ? 30A2889FA ?
FFFFFFFFFFFB620 ?
FFFFFFFFFFFB658 ? 000000000 ?
000000000 ?
ktfbapp+0044 bl ktbchgro 000000000 ? 300000003 ?
FFFFFFFFFFFCB48 ?
FFFFFFFFFFFC218 ?
FFFFFFFFFFFBFD8 ?
FFFFFFFFFFFC0B0 ?
FFFFFFFFFFFC4D8 ?
FFFFFFFFFFFC5B0 ?
kteopgen+00ec bl ktfbapp 000000000 ? FFFFFFFFFFFC218 ?
044244040 ? 0FFFFFFFF ?
FFFFFFFFFFFBFD8 ?
kteopdelete+1468 bl kteopgen FFFFFFFFFFFCB48 ? 000000000 ?
FFFFFFFFFFFBFD8 ?
FFFFFFFFFFFC140 ?
FFFFFFFFFFFC218 ?
FFFFFFFFFFFC0B0 ? 000000000 ?
1101EBDCC ?
ktsxfastdele+0118 bl kteopdelete 700000209E9B238 ? 100000001 ?
100B5A770 ? 000000000 ?
FFFFFFFFFFFC270 ? 000000000 ?
000000000 ?
kteopshrink+0308 bl 01FC21A0
ktssdrbm_segment+0a bl kteopshrink 100000001 ? FFFFFFFFFFFCAD8 ?
f8 000000001 ? 000000001 ?
0000001A0 ? 700000200C016A0 ?
000000000 ?
ktssdro_segment+06c bl ktssdrbm_segment FFFFFFFFFFFD498 ?
8 FFFFFFFFFFFD560 ? 100008043 ?
1FFFFFFFF ?
ktssdt_segs+0350 bl ktssdro_segment 70000020A3C52F0 ? 600007530 ?
0001DCE78 ?
ktmmon+1048 bl ktssdt_segs 000000000 ?
7FFFFFFF7FFFFFFF ?
7FFFFFFF7FFFFFFF ?
000000000 ? 000000000 ?
000000000 ?
7FFFFFFC7FFFFFFC ?
0472CD5BE ?
ktmSmonMain+0030 bl ktmmon 000000000 ?
ksbrdp+03e0 bl _ptrgl
opirip+03fc bl 01FC66A0
opidrv+0448 bl opirip 1103BD070 ? 4103BE990 ?
FFFFFFFFFFFF860 ?
sou2o+0090 bl opidrv 32023373FC ? 400000020 ?
FFFFFFFFFFFF860 ?
opimai_real+0150 bl 01FC0DF4
main+0098 bl opimai_real 000000000 ? 000000000 ?
__start+0090 bl main 000000000 ? 000000000 ?
UNDO segment status: SQL> select status$ from undo$ where us#=85;
STATUS$
----------
1
UNDO$ structure from $ORACLE_HOME/rdbms/admin/sql.bsq: create table undo$ /* undo segment table */
( us# number not null, /* undo segment number */
name varchar2("M_IDEN") not null, /* name of this undo segment */
user# number not null, /* owner: 0 = SYS(PRIVATE), 1 = PUBLIC */
file# number not null, /* segment header file number */
block# number not null, /* segment header block number */
scnbas number, /* highest commit time in rollback segment */
scnwrp number, /* scnbas - scn base, scnwrp - scn wrap */
xactsqn number, /* highest transaction sequence number */
undosqn number, /* highest undo block sequence number */
inst# number, /* parallel server instance that owns the segment */
status$ number not null, /* segment status (see KTS.H): */
/* 1 = INVALID, 2 = AVAILABLE, 3 = IN USE, 4 = OFFLINE, 5 = NEED RECOVERY,
* 6 = PARTLY AVAILABLE (contains in-doubt txs)
*/
ts# number, /* tablespace number */
ugrp# number, /* The undo group it belongs to */
keep number,
optimal number,
flags number,
spare1 number,
spare2 number,
spare3 number,
spare4 varchar2(1000),
spare5 varchar2(1000),
spare6 date
)
status$=1 means INVALID or DOES NOT EXIST. That means the UNDO segment doesn't exist. |
| Comments |
| Comment by ubTools Support [ 08/Nov/07 08:03 AM ] |
Since the UNDO segment doesn't exist, the most probably its type is converted to TEMP. After setting the following event in the SPFILE/PFILE, the problem disappeared.
event="10061 trace name context forever, level 10" This event disables SMON from cleaning temp segment. |
| Comment by ubTools Support [ 08/Nov/07 12:39 PM ] |
| The current UNDO TABLESPACE was dropped, and a new one has been created. Then, Event 10061 has been removed. |