【Oracle数据库恢复】ORA-00600[25027]错误解析
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了【Oracle数据库恢复】ORA-00600[25027]错误解析,小编现在分享给大家,供广大互联网技能从业者学习和参考。文章包含5659字,纯文字阅读大概需要9分钟。
内容图文
ORA-00600[25027]错误的触发原因是ORACLE检测到一个无效的表空间号TSN Tablespace Number或者相对文件号Relative File Number。 该ORA-00600[25027]的2个变量各代表: arg[a] Tablespace Number表空间号 arg[b] 十进制的相对数据块号Relative Data Block Add
ORA-00600[25027]错误的触发原因是ORACLE检测到一个无效的表空间号TSN Tablespace Number或者相对文件号Relative File Number。
该ORA-00600[25027]的2个变量各代表:
arg[a] Tablespace Number表空间号
arg[b] 十进制的相对数据块号Relative Data Block Address (RDBA)
该ORA-00600[25027]错误相关的模块为Kernel File management Tablespace component,其影响为可能的物理块损坏。
当该错误触发后 如果 arg[b] 即RDBA为0,则该错误可能由于索引问题引起。
可以使用如下查询来获得有问题的索引:
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;
如果上面的查询返回了数据行,则建议用户进一步检查查询所获得的对象,并考虑drop这些对象来绕过错误。
进一步可以对trace文件中指向的表做一个analyze table validate structure cascade,来进一步确认该问题。
与ORA-00600[25027]相关的一些BUG列表如下:
?如果自己搞不定可以找ASKMACLEAN专业ORACLE数据库修复团队成员帮您恢复!
NB | Bug | Fixed | Description |
14010183 | 11.2.0.3.BP22, 11.2.0.4.BP03, 12.1.0.2, 12.2.0.0 | ORA-600 [ktspfundo:objdchk_kcbgcur_3] in SMON after failed temp segment merge load | |
13503554 | 11.2.0.4, 12.2.0.0 | Various ORA-600 errors crashing the apply process in a downstreams environment | |
13785716 | 11.2.0.4, 12.1.0.1 | Intermittent ORA-600 [25027] during upgrade from 10.2 to 11.2 | |
11661824 | 11.2.0.1.BP09 | Assorted Dumps by SQL*LOADER using DIRECT and PARALLEL after exadata bp8 is applied | |
10067246 | 12.2.0.0 | ORA-600 [25027] ORA-7445 [kauxs_do_dml_cooperation] by CREATE INDEX ONLINE | |
14138130 | 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 | |
13330018 | 11.2.0.4, 12.1.0.1 | ora-600 [ktspfmb_add1], [4294959240] occurred, then cannot recover with ora-600[25027] | |
13103913 | 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 | |
10394825 | 11.2.0.3, 12.1.0.1 | ORA-600[25027] [..] [0] inserting to ASSM segment | |
10329146 | 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 | |
+ | 10209232 | 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 |
+ | 9399991 | 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 |
* | 9145541 | 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 |
8837919 | 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 | |
8803762 | 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 | |
8716064 | 11.2.0.2, 12.1.0.1 | Analyze Table Validate Structure fails on ADG standby with several errors | |
+ | 8597106 | 11.2.0.1.BP06, 11.2.0.2, 12.1.0.1 | Lost Write in ASM when normal redundancy is used |
7251049 | 11.2.0.1.BP08, 11.2.0.2, 12.1.0.1 | Corruption in bitmap index introduced when using transportable tablespaces | |
8437213 | 10.2.0.4.3, 10.2.0.5, 11.1.0.7.7, 11.2.0.1 | ASSM first level bitmap block corruption | |
8356966 | 11.2.0.1 | ORA-7445 [kdr9ir2rst] by DBMS_ADVISOR or false ORA-1498 by ANALYZE on COMPRESS table | |
* | 8198906 | 10.2.0.5, 11.2.0.1 | OERI [kddummy_blkchk] / OERI [5467] for an aborted transaction of allocating extents |
* | 7263842 | 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 |
6666915 | 10.2.0.5, 11.1.0.7, 11.2.0.1 | OERI[25027] / dictionary corruption from concurrent partition DDL | |
6025993 | 10.2.0.5, 11.1.0.6 | ORA-600 [25027] in flashback archiving queries | |
4925342 | 9.2.0.8, 10.2.0.3, 11.1.0.6 | OERI [25027] / OERI [25012] on IOT analyze estimate statistics | |
* | 7190270 | 10.2.0.4.1, 10.2.0.5 | Various ORA-600 errors / dictionary inconsistency from CTAS / DROP |
4310371 | 9.2.0.8, 10.2.0.2 | OERI [25027] from concurrent startup / shutdown in RAC | |
4177651 | 10.2.0.1 | Row migration within a MERGE may OERI[25027] | |
4020195 | 10.1.0.5, 10.2.0.1 | OERI 25027 can occur in RAC accessing transported tablespace | |
4000840 | 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 | |
3963135 | 10.1.0.5, 10.2.0.1 | OERI[kcbgcur_3] / OERI:25027 during bitmap index updates | |
3829900 | 10.1.0.4, 10.2.0.1 | OERI[25027] possible accessing index in 10g | |
2942185 | 9.2.0.6, 10.1.0.4, 10.2.0.1 | Corruption occurs on direct path load into IOT with ADDED columns | |
3085057 | 10.1.0.2 | ORA-600: [25027] from ALTER TABLE .. SHRINK SPACE CASCADE | |
2926182 | 9.2.0.5, 10.1.0.2 | OERI[25027] / ORA-22922 accessing LOB columns in IOT in AFTER UPDATE trigger |
Related posts:
- 【ORACLE数据库恢复】ORA-00600[KCLCHKBLK]
- 【Oracle数据恢复】ORA-00600[4000]错误解析
- 【Oracle数据恢复】ORA-00600[3020]错误解析
- 【Oracle数据恢复】ORA-00600[kdBlkCheckError]错误解析
- 【Oracle数据恢复】ORA-600 [kcbgcur_9]错误解析
- 【Oracle数据恢复】ORA-00600[2662]错误解析
- 【Oracle数据恢复】ORA-600[4511]错误解析
- Oracle内部错误:ORA-00600[25012]一例
- How to trigger ORA-00600,ORA-7445 by manual
- Oracle内部错误:ORA-00600:[6033]一例
原文地址:【Oracle数据库恢复】ORA-00600[25027]错误解析, 感谢原作者分享。
内容总结
以上是互联网集市为您收集整理的【Oracle数据库恢复】ORA-00600[25027]错误解析全部内容,希望文章能够帮你解决【Oracle数据库恢复】ORA-00600[25027]错误解析所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错,欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 gblab@vip.qq.com 举报,一经查实,本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。