ORA-00600: internal error code, arguments: [2662]
数据库版本:Oracle 11.2.0.1.0
数据库服务器操作系统:Windows server 2008
事故原因:数据库服务器异常断电
影响:导致磁盘损坏,两个控制文件全部损坏,通过DBV工具检查发现,多个数据文件,产生多个坏块;
数据库备份情况:数据库非归档,之前没有任何物理或逻辑备份;
解决方案:手动创建控制文件,启动数据库到mount状态,通过隐含参数_allow_resetlogs_corruption=TRUE跳过一致性检查,强制open数据库,expdp导出全部数据,重建数据库;
问题:在设置隐含参数_allow_resetlogs_corruption=TRUE,尝试resetlogs Open数据库时,报错ORA-00600: internal error code, arguments: [2662],[0],[82522462],[0],[82530638],[12583040],[],[],[],[],[],[]
报错原因:
A data block SCN is ahead of the current SCN.(SCN不一致)
Bug 14351566 ORA-600 [kclchkblk_4] ORA-600 [2662] when doing flash back;
解决方案:
调整(提升)SCN;
方法一:
数据库在open状态下执行
alter session set events 'IMMEDIATE trace name adjust_scn level n';(不适用本次案例)
方法二:
数据库在mount状态下执行
alter session set events '10015 trace name adjust_scn level n';(只适用11.2.0.2g之前的版本,不适用11g版本数据库)
方法三:
设置隐含参数_minimum_giga_scn=n,提升SCN(【11.2.0.2之前】适用此案例)
方法四:
oradebug工具,提升SCN(【支持11.2.0.2以后版本】)
其中MOS中查询有关ORA-00600[2662]问题相关信息;
ORA-600/ORA-7445/ORA-700 Error Look-up Tool (文档 ID 153788.1)
|
|
ORA-600 [2662] "Block SCN is ahead of Current SCN" (文档 ID 28929.1) |
Note: For additional ORA-600 related information please read Note:146580.1
PURPOSE:
This article discusses the internal error "ORA-600 [2662]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.
ERROR:
Format: ORA-600 [2662] [a] [b] [c] [d] [e]
VERSIONS:
versions 6.0 to 12.1
DESCRIPTION:
A data block SCN is ahead of the current SCN.
The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN
stored in a UGA variable.
If the SCN is less than the dependent SCN then we signal the ORA-600 [2662]
internal error.
ARGUMENTS:
Arg [a] Current SCN WRAP
Arg [b] Current SCN BASE
Arg [c] dependent SCN WRAP
Arg [d] dependent SCN BASE
Arg [e] Where present this is the DBA where the dependent SCN came from.
FUNCTIONALITY:
File and IO buffer management for redo logs
IMPACT:
INSTANCE FAILURE
POSSIBLE PHYSICAL CORRUPTION
SUGGESTIONS:
There are different situations where ORA-600 [2662] can be raised.
It can be raised on startup or during database operation.
If not using Parallel Server, check that 2 instances have not mounted
the same database.
Check for SMON traces and have the alert.log and trace files ready
to send to support.
Check the SCN difference [argument d]-[argument b].
If the SCNs in the error are very close, then try to shutdown and startup
the instance several times.
In some situations, the SCN increment during startup may permit the
database to open. Keep track of the number of times you attempted a
startup.
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:
The list below is restricted to show only bugs believed to affect version 11.2.0.1.
Other bugs may affect this version but have not been confirmed as being relevant yet.
There is 1 bug listed.
NB |
Prob |
Bug |
Fixed |
Description |
III |
14351566 |
11.2.0.3.8, 11.2.0.3.BP21, 11.2.0.4, 12.1.0.1 |
ORA-600 [kclchkblk_4] ORA-600 [2662] when doing flash back |
· '*' indicates that an alert exists for that issue.
· '+' indicates a particularly notable issue / bug.
· See Note:1944526.1 for details of other symbols used
Bug 14351566 - ORA-600 [kclchkblk_4] ORA-600 [2662] when doing flash back (文档 ID 14351566.8) | 转到底部 |
|
|
Bug 14351566 ORA-600 [kclchkblk_4] ORA-600 [2662] when doing flash backThis note gives a brief overview of bug 14351566.The content was last updated on: 21-SEP-2015 Click here for details of each of the sections below. Affects:
Fixed:
DescriptionThis fix prevents various ORA-600 internal errors relating to the database having the wrong versions of some blocks following a "flashback database" operation. Rediscovery Notes Look for all the following: - the DB Admin performs a "flashback database" on a database containing writable plugged-in datafiles (from transportable tablespaces), then some time after that, there are various ORA-600 errors, for example: ORA-600 [kclchkblk_4] and/or ORA-600 [2662] involving block types "KTFB Bitmapped File Space Header" or "PAGETABLE MANAGED LOB BLOCK" - "select file#,foreign_dbid from v$datafile" shows some non-zero foreign_dbid's (and BEFORE the "flashback database", these datafiles also had a non-zero value for v$datafile.unrecoverable_change#). - alter session set events 'immediate trace name controlf level 9' MAY show some non-zero Plugin scns (depends on compatibility history)
ReferencesBug:14351566 (This link will only work for PUBLISHED bugs) |
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/29785807/viewspace-2104794/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/29785807/viewspace-2104794/