oracle ora22922,Oracle ORA-600 [25027]

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

ERROR:

Format: ORA-600 [25027] [a] [b]

VERSIONS:

versions 9.2 and above

ARGUMENTS:

Arg [a] Tablespace Number (TSN)

Arg [b] Decimal Relative Data Block Address (RDBA)

In 12c it includes Multitenant information:

Arg [a] 0 if Multitenant is not enabled or 0 if there is not Root CDB session, 1 ROOT PDBID, otherwise PDBID top session

Arg [b] PDBID

Arg [c] Tablespace Number (TSN)

Arg [d] Decimal Relative Data Block Address (RDBA)

SUGGESTIONS:

1. If the Arg [b] onr [d] in 12c (the RDBA) is 0 (zero), then this could be caused by fake indexes.

The following query will list fake indexes:

select do.owner,do.object_name, do.object_type,sysind.flags

from dba_objects do, sys.ind$ sysind

where do.object_id = sysind.obj#

and bitand(sysind.flags,4096)=4096;

If the above query returns any rows, check the objects involved and consider dropping them as they can cause this error.

2. Run analyze table validate structure on the table referenced in the Current SQL statement in

the related trace file.

If the Known Issues section below does not help in terms of identifying

a solution, please submit the trace files and alert.log to Oracle

Support Services for further analysis.

Known Issues:You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:

NB

Prob

Bug

Fixed

Description

II

ORA-600 [25027] can occur with large datafiles using ASSM

I

12.1.0.2, 12.2.0.0

ORA-600 [25027][0][0] from ALTER TABLE .. MOVE with nosegment index

I

12.1.0.1.4, 12.1.0.2, 12.2.0.0

Corruption type ORA-600 errors from heavy concurrent DML on index cluster table

II

11.2.0.3.BP22, 11.2.0.4.2, 11.2.0.4.BP03, 12.1.0.1.4, 12.1.0.2, 12.2.0.0

ORA-600 [ktspfundo:objdchk_kcbgcur_3] in SMON after failed temp segment merge load

III

11.2.0.4, 12.2.0.0

Various ORA-600 errors crashing the apply process in a downstreams environment

II

11.2.0.4, 12.1.0.1

Intermittent ORA-600 [25027] during upgrade from 10.2 to 11.2

I

11.2.0.1.BP09

Assorted Dumps by SQL*LOADER using DIRECT and PARALLEL after exadata bp8 is applied

II

12.2.0.0

ORA-600 [25027] when local index has unusable index partitions

II

12.1.0.2, 12.2.0.0

ORA-600 [25027] ORA-7445 [kauxs_do_dml_cooperation] ORA-8102 during CREATE INDEX ONLINE

III

11.2.0.3.BP04, 11.2.0.4

ORA-600 [kkedsgettabblkcnt: null segment] / ORA-600 [25027] against PARTITION table with Delayed Segment Creation or Interval Partitioned Table

II

11.2.0.3.5, 11.2.0.3.BP13, 11.2.0.4, 12.1.0.1

SGA memory corruption / ORA-7445 when modifying uncompressed blocks of an HCC-compressed segment

II

11.2.0.3.4, 11.2.0.3.BP10, 11.2.0.4, 12.1.0.1

ORA-600 [kcbgtcr_1] / ORA-600 [kkpo_rcinfo_defstg:objnotfound] / ORA-600 [25027] against a Partitioned Table during Dynamic Sampling

II

11.2.0.4, 12.1.0.1

ora-600 [ktspfmb_add1], [4294959240] occurred, then cannot recover with ora-600[25027]

III

11.2.0.2.BP15, 11.2.0.3.3, 11.2.0.3.BP03, 11.2.0.4, 12.1.0.1

ORA-600 [25027] [ts#] [1] or false ORA-1 during dml while index is being rebuilt online

II

11.2.0.3.8, 11.2.0.3.BP18, 11.2.0.4, 12.1.0.1

Direct NFS appears to be sending zero length windows to storage device. It may also cause Lost Writes

II

11.2.0.3.BP18, 11.2.0.4, 12.1.0.1

ORA-600[kdsgrp1] from SELECT on plugged in tablespace with FLASHBACK

II

11.2.0.4, 12.1.0.1

ORA-600 / ORA-8103 UNUSABLE state of partitioned index is not carried across by TABLESPACE transport using DataPump

III

11.2.0.3, 12.1.0.1

ORA-600[25027] [..] [0] inserting to ASSM segment

-

11.2.0.1.BP10, 11.2.0.2.2, 11.2.0.2.BP03, 11.2.0.2.GIBUNDLE02, 11.2.0.2.GIPSU02, 11.2.0.3, 12.1.0.1

Lost write in ASM with multiple DBWs and a disk is offlined and then onlined

+

II

11.1.0.7.7, 11.2.0.1.BP08, 11.2.0.2.1, 11.2.0.2.BP02, 11.2.0.2.GIBUNDLE01, 11.2.0.3, 12.1.0.1

ORA-1578 / ORA-600 [3020] Corruption. Misplaced Blocks and Lost Write in ASM

+

IIII

11.1.0.7.5, 11.2.0.1.3, 11.2.0.1.BP04, 11.2.0.2, 12.1.0.1

Assorted Internal Errors and Dumps (mostly under kkpa*/kcb*) from SQL against partitioned tables

*

III

11.1.0.7.4, 11.2.0.1.2, 11.2.0.2, 12.1.0.1

OERI[25027]/OERI[4097]/OERI[4000]/ORA-1555 in plugged datafile after CREATE CONTROLFILE in 11g

E

II

11.2.0.2, 12.1.0.1

DBV / RMAN enhanced to detect ASSM blocks with ktbfbseg but not ktbfexthd flag set as in Bug 8803762

III

11.1.0.7.6, 11.2.0.1.2, 11.2.0.1.BP06, 11.2.0.2, 12.1.0.1

ORA-600[kdsgrp1], ORA-600[25027] or wrong results on 11g database upgrade from 9i

II

11.2.0.2, 12.1.0.1

Analyze Table Validate Structure fails on ADG standby with several errors

+

II

11.2.0.1.BP06, 11.2.0.2, 12.1.0.1

Lost Write in ASM when normal redundancy is used

II

11.2.0.1.BP08, 11.2.0.2, 12.1.0.1

Corruption in bitmap index introduced when using transportable tablespaces

-

10.2.0.4.3, 10.2.0.5, 11.1.0.7.7, 11.2.0.1

ASSM first level bitmap block corruption

III

11.2.0.1

ORA-7445 [kdr9ir2rst] by DBMS_ADVISOR or false ORA-1498 by ANALYZE on COMPRESS table

*

III

10.2.0.5, 11.2.0.1

OERI [kddummy_blkchk] / OERI [5467] for an aborted transaction of allocating extents

*

III

10.2.0.4.2, 10.2.0.5, 11.1.0.7.1, 11.2.0.1

ORA-955 during CTAS / OERI [ktsircinfo_num1] / dictionary inconsistency for PARTITIONED Tables

-

10.2.0.5, 11.1.0.7, 11.2.0.1

OERI[25027] / dictionary corruption from concurrent partition DDL

-

10.2.0.5, 11.1.0.6

ORA-600 [25027] in flashback archiving queries

-

9.2.0.8, 10.2.0.3, 11.1.0.6

OERI [25027] / OERI [25012] on IOT analyze estimate statistics

*

IIII

10.2.0.4.1, 10.2.0.5

Various ORA-600 errors / dictionary inconsistency from CTAS / DROP

-

9.2.0.8, 10.2.0.2

OERI [25027] from concurrent startup / shutdown in RAC

-

10.2.0.1

Row migration within a MERGE may OERI[25027]

-

10.1.0.5, 10.2.0.1

OERI 25027 can occur in RAC accessing transported tablespace

-

9.2.0.7, 10.1.0.4, 10.2.0.1

Update of a row with more than 255 columns can cause block corruption

II

10.1.0.5, 10.2.0.1

OERI[kcbgcur_3] / OERI:25027 during bitmap index updates

-

10.1.0.4, 10.2.0.1

OERI[25027] possible accessing index in 10g

-

9.2.0.6, 10.1.0.4, 10.2.0.1

Corruption occurs on direct path load into IOT with ADDED columns

II

10.1.0.2

ORA-600: [25027] from ALTER TABLE .. SHRINK SPACE CASCADE

-

9.2.0.5, 10.1.0.2

OERI[25027] / ORA-22922 accessing LOB columns in IOT in AFTER UPDATE trigger