ORA-00600 [KCBNEW_3] 分析
系统:AIX数据库版本:10.2.0.3 报错如下:Tue Jan 15 04:08:18 2013Errors in file /Oracle/admin/RASDB/udump/rasdb_ora_76620
系统:AIX
数据库版本:10.2.0.3
报错如下:
Tue Jan 15 04:08:18 2013
Errors in file /Oracle/admin/RASDB/udump/rasdb_ora_766202.trc:
ORA-00600: internal error code, arguments: [kcbnew_3], [0], [8], [1639086], [], [], [], []
查看官方说明:
Summary of Bugs Containing ORA - 00600 [KCBNEW_3] [ID 428568.1]
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1.0.6
Information in this document applies to any platform.
This article is intended to
1. Help the reader to understand ORA-00600 [KCBNEW_3] error and how is this caused.
2. List the most common bugs of the aforesaid error and their fixes.
This is a consolidated article based upon various bugs logged for the error ORA-00600 [KCBNEW_3] and gives the reader an overview about the most frequent bugs which the customers are affected with.
The error ORA-00600 [KCBNEW_3] is raised due to the following reason.
A cache buffer holding a database block is in the process of
being reused.
The buffer is in state "current" and may be reused only if the object
is of type temp or undo.
The consistency check comparing the block class in the buffer header
with the block class passed to the cache by the caller is failing.
Bug 4430244 ( Unpublished )
Abstract : ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KCBNEW_3]
Versions affected : 10.2
Fixed releases : 10.2.0.4, 11.0.0.0
Details : Segment advisor code (eg: DBMS_SPACE.OBJECT_GROWTH_TREND)
can load blocks into the cache for DROPped objects as CURRENT leading
to subsequent operations seeing an incorrect (old) version of a block.
This can lead to various internal buffer cache related errors such as
ORA-600 [kcbnew_3] / ORA-600 [kcbz_check_objd_typ_3].
The exact error depends on which code sees the block.
Backportable : yes to 10.2
Symptoms :
1. ORA-600 [kcbnew_3] internal error reported in the alert.log
2. May occur if segment advisor and DROP operation are being run
concurrently on the same object.
Workaround :
sql>alter system flush buffer cache' to flush the buufer in the cache.
Patch Details:
Check Metalink for Patch 4430244 availability.
解决方法:
1.临时解决方法可以清空缓存区。
2.可以打Patch 4430244小补丁

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

Data Integration Simplification: AmazonRDSMySQL and Redshift's zero ETL integration Efficient data integration is at the heart of a data-driven organization. Traditional ETL (extract, convert, load) processes are complex and time-consuming, especially when integrating databases (such as AmazonRDSMySQL) with data warehouses (such as Redshift). However, AWS provides zero ETL integration solutions that have completely changed this situation, providing a simplified, near-real-time solution for data migration from RDSMySQL to Redshift. This article will dive into RDSMySQL zero ETL integration with Redshift, explaining how it works and the advantages it brings to data engineers and developers.
