ORA-00600 Kcfrbd_3 出现在查询 DBA_EXTENTS解决办法-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

ORA-00600 Kcfrbd_3 出现在查询 DBA_EXTENTS解决办法

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 05:46 PM

filenbsp

本文章总结了关于ORA-00600 Kcfrbd_3 出现在查询 DBA_EXTENTS解决办法,碰到这类问题的朋友可看看。

在某些异常情况下，查询数据库的dba_extents字典表时，可能遇到ORA-600 kcfrbd_3错误，这个错误是由于文件大小和控制文件不符合导致的，触发原因可能是数据库写异常，通常可以通过重建控制文件来消除错误。
但是，如果是数据文件头部的信息记录错误，和数据文件本身不符合，则需要修改数据文件头部的文件大小信息，才能够解决该问题。

这一问题极其少见，在MOS Note 601798.1 记录如下参考信息：

代码如下	复制代码
Oracle reports the ORA-00600: [kcfrbd_3] on a particular query. The same exception is encountered if you try to select DBA_EXTENTS using a FILE#/BLOCK#.

以下是这个600错误的几个主要参数说明：

代码如下

复制代码

ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kcfrbd_3], [13], [64011], [1], [64000], [64000], [], []

Arg [a] File number
Arg [b] Block number
Arg [c] Nro of blocks
Arg [d] Logical File Size
Arg [e] File Size

第一个参数是文件号，如下 13 为文件号：

代码如下

复制代码

SELECT segment_name , segment_type , owner , tablespace_name
FROM sys.dba_extents
WHERE file_id = 13
AND 64011 BETWEEN block_id and block_id + blocks -1;

ERROR at line 2:
ORA-00600: internal error code, arguments: [kcfrbd_3], [13], [66499], [1], [64000], [64000], [], []
Cause

There is a corruption on the extent allocation table to tablespace that

the file# 13 belongs to.
For example, in this case,

Datafile # 13 is +DATA/ORCL/datafile/mgmt_tablespace.340.655388135
(FOB) flags=512 fib=0x1629c8f68 incno=0 pending i/o cnt=0

fname=+DATA/ORCL/datafile/mgmt_tablespace.340.655388135

fno=13 lblksz=8192 fsiz=64000
We are trying to access the block 64011 that is beyond the number of blocks 6400.

最简单的情况，可以通过 resize 文件来消除。

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

How does MySQL index cardinality affect query performance?Apr 14, 2025 am 12:18 AM

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

MySQL: Resources and Tutorials for New UsersApr 14, 2025 am 12:16 AM

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

Real-World MySQL: Examples and Use CasesApr 14, 2025 am 12:15 AM

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.

SQL Commands in MySQL: Practical ExamplesApr 14, 2025 am 12:09 AM

SQL commands in MySQL can be divided into categories such as DDL, DML, DQL, DCL, etc., and are used to create, modify, delete databases and tables, insert, update, delete data, and perform complex query operations. 1. Basic usage includes CREATETABLE creation table, INSERTINTO insert data, and SELECT query data. 2. Advanced usage involves JOIN for table joins, subqueries and GROUPBY for data aggregation. 3. Common errors such as syntax errors, data type mismatch and permission problems can be debugged through syntax checking, data type conversion and permission management. 4. Performance optimization suggestions include using indexes, avoiding full table scanning, optimizing JOIN operations and using transactions to ensure data consistency.

How does InnoDB handle ACID compliance?Apr 14, 2025 am 12:03 AM

InnoDB achieves atomicity through undolog, consistency and isolation through locking mechanism and MVCC, and persistence through redolog. 1) Atomicity: Use undolog to record the original data to ensure that the transaction can be rolled back. 2) Consistency: Ensure the data consistency through row-level locking and MVCC. 3) Isolation: Supports multiple isolation levels, and REPEATABLEREAD is used by default. 4) Persistence: Use redolog to record modifications to ensure that data is saved for a long time.

MySQL's Place: Databases and ProgrammingApr 13, 2025 am 12:18 AM

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL: From Small Businesses to Large EnterprisesApr 13, 2025 am 12:17 AM

MySQL is suitable for small and large enterprises. 1) Small businesses can use MySQL for basic data management, such as storing customer information. 2) Large enterprises can use MySQL to process massive data and complex business logic to optimize query performance and transaction processing.

What are phantom reads and how does InnoDB prevent them (Next-Key Locking)?Apr 13, 2025 am 12:16 AM

InnoDB effectively prevents phantom reading through Next-KeyLocking mechanism. 1) Next-KeyLocking combines row lock and gap lock to lock records and their gaps to prevent new records from being inserted. 2) In practical applications, by optimizing query and adjusting isolation levels, lock competition can be reduced and concurrency performance can be improved.

See all articles