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)<1span style="font-size:12.0pt;font-family:" color:#333333;"=""> |
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 |
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
转到底部
