If you cannot recover data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.

Parnassusdata Software Database Recovery Team

Service Hotline:  +86 13764045638 E-mail: service@parnassusdata.com

  ORA-600 [ksmals] Possible bugs: Fixed in: Bug:2662683 ORA-7445 & HEAP CORRUPTION WHEN RUNNING APPS PROGRAM THAT DOES HEAVY INSERTS 9.2.0.4 References: Note:247822.1 ORA-600 [ksmals] ORA-600 [4000] Possible bugs: Fixed in: Bug:2959556 STARTUP after an ORA-701 fails with OERI[4000] 9.2.0.5,10G Bug:1371820 OERI:4506 / OERI:4000 possible against transported tablespace 8.1.7.4, 9.0.1.4, 9.2.0.1 References: Note:47456.1 ORA-600 [4000] "trying to get dba of undo segment header block from usn" ORA-600 [4454] Possible bugs: Fixed in: Bug:1402161 OERI:4411/OERI:4454 on long running job 8.1.7.3, 9.0.1.3, 9.2.0.1 References: Note:138836.1 ORA-600 [4454] ORA-600 [kcbgcur_9] Possible bugs: Fixed in: Bug:1804676 OERI:KCBGCUR_9 possible from ONLINE REBUILD INDEX with concurrent DML 8.1.7.3, 9.0.1.3, 9.2.0.1 References: Note:114058.1 ORA-600 [kcbgcur_9] "Block class pinning violation" ORA-600 [729] Possible bugs: Fixed in: Bug:931820 Direct load fails in kghxhdr when SESSION_CACHED_CURSORS is larger than zero 9.0.1 Bug:2177050 OERI:729 space leak possible (with tags "define var info" / "oactoid info") 8.1.7.4, 9.0.1   References: Note:31056.1 ORA-600 [729] "UGA Space Leak" ORA-600 [1113] Possible bugs: Fixed in: Bug:1307247 OERI:1113 can occur if ANALYZE fails or is interupted 8.0.6.3, 8.1.7.1, 9.0.1 References: Note:145367.1 Interrupted or failed ANALYZE might cause instance to hang Note:41767.1 ORA-600 [1113] "Parent SO is free when adding a child" ORA-600 [1114] / ORA-600 [ksmguard2] Possible bugs: Fixed in: Bug:1779978 OERI:1114 / OERI:KSMGUARD2 with more than about 536 sessions 8.1.7.2, 9.0.1 References: Note:153041.1 ORA-600 [1114] / ORA-600 [KSMGUARD2] on 8.1.7.1.x with Large Number of Sessions ORA-600 [4820] Possible bugs: Fixed in: Bug:1951929 ORA-7445 in KQRGCU/kqrpfr/kqrpre possible 8.1.7.3, 9.0.1.2, 9.2 References: ORA-600 [12261] Possible bugs: Fixed in: Bug:912223 OERI:12261 / dump in OPIPLS using EXECUTE IMMEDIATE with SQL derived strings 8.1.7.2, 9.0.1 @Bug:1661786 OERI:12261 / single byte memory corruption possible for CALL type triggers 8.1.7.3, 9.0.1 References: ORA-600 [12333] Possible bugs: Fixed in: References: Note:35928.1 ORA-600 [12333] "Fatal Two-Task Protocol Violation" ORA-600 [16224] Possible bugs: Fixed in: Bug:1651530 ORA-600 [16224] [], THEN SMON DIES AND KILLS INSTANCE 8.1.7.4, 9.0.1.3 Bug:1310142 SMON CRASHES INSTANCE WITH ERROR ORA-600 [16224] 8.1.6.3 References: Note:136754.1 Instance crashes with ORA-600 [16224] ORA-600 [17069] Possible bugs: Fixed in:   References: Note:39616.1 ORA-600 [17069] "Failed to pin a library cache object after 50 attempts" ORA-600 [17112] Possible bugs: Fixed in: References: Note:47411.1 ORA-600 [17112] "Internal Heap Error" ORA-600 [17182] Possible bugs: Fixed in: References: Note:34779.1 ORA-600 [17182] "Heap chunk header BAD MAGIC" ORA-600 [kcbgcur_2] Possible bugs: Fixed in: Bug:1502537 OERI:KCBGCUR_2 possible on DML (stack includes ktsf_rsp1) 8.1.7.1, 9.0.1 References: Note:145610.1 ORA-600 [kcbgcur_2] after upgrade from Oracle7 to 8.1.x ORA-600 [kccsbck_first] or ORA-600 [3716] or ORA-600 [4185] (HP Tru64 Only) Possible bugs: Fixed in: Bug:1379200 NODE PANIC OR SHUTDOWN CAN CAUSE PARITIONED CLUSTER AND DATABASE CORRUPTION 8.1.7.1, 9.0.1.0 References: Note:137322.1 ALERT: Node panic or shutdown can cause partitioned cluster and database corruption ORA-600 [kwqitnmptme:read] Possible bugs: Fixed in: Bug:1663503 ORA-600 [kwqitnmptme:read] w/MAX_RETRIES and EXPIRATION (AQ_TM_PROCESSES) 9.0.1 References: