9.2.0.5 Alert -- LMT+ASSM Possible Corruption
- From: Hemant K Chitale <hkchital@xxxxxxxxxxxxxx>
- To: ORACLE-L@xxxxxxxxxxxxx
- Date: Tue, 31 Aug 2004 23:42:00 +0800
Note "281047.1" "ALERT: Possible Corruption when Using Locally Managed
Tablespaces and ASSM "
Bug 3785200 "ORA-600 [6002] INDEX CORRUPION IN ASSM TABLESPACE "
Rediscovery Information:
There are various internals errors:
Eg ORA-600:[ktspmlhwm-1] ORA-600:[kcb*] ORA-600:[6002]
Always involves a bitmapped segment (tablespace
is created with "segment space management auto").
Most reports of this bug were from customers who
were running on HP-UX and who were updating
bitmapped index partitions in parallel mode.
For the ORA-00600:[ktspmlhwm-1], the tracefile
should have a segment header dumped somewhere in
the process state and:
- for one or both highwatermarks, blk# >ext size
- in the extent map the last extent is probably
smaller than the previous extent (ie the last
extent has been trimmed)
.
Workaround:
To prevent the error from happening:
- do not use ASSM tablespaces
.
Release Notes:
]] Various internal errors when using bitmapped tablespaces
]] Eg ORA-600:[ktspmlhwm-1] ORA-600:[kcb*] ORA-600:[6002]
Hemant K Chitale
Oracle 9i Database Administrator Certified Professional
http://web.singnet.com.sg/~hkchital
[1]
----------------------------------------------------------------------------
----------------------------------------------------------------------------
--- Links ---
1 http://web.singnet.com.sg/~hkchital
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
- » 9.2.0.5 Alert -- LMT+ASSM Possible Corruption
