|
|
metallink上的解法:
Problem statement:
ORA-600 [KCBRBR_2], [2],[25178366], [330], [],[],[],[]
--------------------------------------------------------------------------------
Hdr: 1125719 8.1.5 RDBMS 8.1.5 PRODID-5 PORTID-453 Abstract: ORA-600 [KCBRBR_2], [2],[25178366], [330], [],[],[],[] *** 12/23/99 01:27 pm *** . . . ========================= PROBLEM: . 1. Clear description of the problem encountered: ORA-600 [kcbrbr_2], [2],[25178366], [330], [],[],[],[] on database open. This happens when he comments out an event set in init.ora event="10061 trace name context forever, level 10" and tries to start the db. . 2. Pertinent configuration information (MTS/OPS/distributed/etc) Ct is running Oracle 8i on a two processor SUN (250) server, with 2 gigs RAM, Solaris 2.6. Includes MTS. No replication/distributed. The database is on both internal drives and an external RAID 0+1 (SUN) system. The database is configured to run Parallel queries,has many bitmaped local indexes (100's),has several large tables that are partioned into 60 partitions. . . 3. Indication of the frequency and predictability of the problem Whenever he tries to start the database without the event 10061. . 4. Sequence of events leading to the problem Ct had upgraded from an earlier version of Oracle.In this process he rebuilt all tablespaces and reimported all data. Once this process was completed, he issued a shutdown command from server manager.The database would not shutdown without a 'shutdown abort' being issued.At this point, he could not restart the database. A call to tech support advised placing this event 10061 in the init file. Once this was in the init file the database started. Subsequent to this he had trouble with temporary segments accumulating in permanent tablespace areas. . Ct has a segment of type TEMPORARY in one of his user data tablespaces. . 5. Technical impact on the customer. Include persistent after effects. This is having a major impact on ct. This is a production database. As temporary table segments build up in the tablespaces he is forced to recreate tablespace through a lengthy process of exporting data, rebuilding the tablespace and reimporting. The database contains over 500 million rows on 100 gigs of disk storage, so this is an invovled process. This database is also a critical part of his business. ========================= DIAGNOSTIC ANALYSIS: . ========================= WORKAROUND: . ========================= RELATED BUGS: 911109 . ========================= REPRODUCIBILITY: . 1. State if the problem is reproducible; indicate where and predictability Reproduced everytime the event 10061 is removed. 2. List the versions in which the problem has reproduced . 3. List any versions in which the problem has not reproduced . ========================= TESTCASE: . . ======================== STACK TRACE: ksedmp kgerinv kgeasnmierr kcbrbr ktssdro_segment ktssdt_segs ktmmon ksbrdp opirip opidrv sou2o main start . ========================= SUPPORTING INFORMATION: Alert log and trace files loaded onto WRVMS . ========================= 24 HOUR CONTACT INFORMATION FOR P1 BUGS: n/a ========================= DIAL-IN INFORMATION: n/a ========================= IMPACT DATE: *** 02/24/00 05:12 pm *** *** 02/25/00 04:04 pm *** (CHG: Asg->NEW OWNER) *** 02/25/00 04:04 pm *** *** 03/06/00 05:12 pm *** Logged into the ct's machine and fixed the problem here too. The database works fine without 10061. Due to lack of evidence on what caused the problem (redo records responsible for causing this inconsistency is not available), I am closing this as not a bug. Thanks *** 03/06/00 05:12 pm *** (CHG: Sta->32) *** 04/05/00 08:08 pm *** (CHG: Sta->92) *** 07/10/00 03:34 am *** (CHG: Sta->91) |
|
楼主: rebecca_xt
IP卡
狗仔卡
发表于 2004-12-27 10:40
显身卡
楼主