| Bug 8341623 RMAN block media recovery fails ORA-600 [kcrrge.cannotread_inc.1] This note gives a brief overview bug 8341623.
The content was last updated on: 18-NOV-2010
Click here for details of each of the sections below. Affects:
| Product (Component) |
Oracle Server (Rdbms) |
| Range of versions believed to be affected |
Versions >= 10.2.0.2 but BELOW 11.2 |
| Versions confirmed as being affected |
- 11.1.0.7
- 11.1.0.6
- 10.2.0.4
- 10.2.0.2
|
| Platforms affected |
Generic (all / most platforms affected) |
It is believed to be a regression in default behaviour thus:
Regression introduced in 10.2.0.4
Regression introduced in 11.1.0.6
Regression introduced in 11.1.0.7
Fixed:
| This issue is fixed in |
- 11.2.0.1 (Base Release)
- 11.1.0.7.1 (Patch Set Update)
- 10.2.0.5 (Server Patch Set)
- 10.2.0.4.2 (Patch Set Update)
- 11.1.0.7 Patch 18 on Windows Platforms
- 10.2.0.4 Patch 26 on Windows Platforms
|
| Symptoms: |
Related To: |
- Internal Error May Occur (ORA-600)
- ORA-600 [kcrrge.cannotread_inc.1]
|
|
Description This problem is introduced in 10.2.0.4, 11.1.0.6 and 11.1.0.7 by the fix for bug 5079641 . It can also affect any release where a one off fix for bug 5079641 has been installed. ORA-600 [kcrrge.cannotread_inc.1] can be produced by RMAN blockrecover (Block Media Recovery - BMR) In 11g look for the next top call stack in the trace file: krdbmr -> krddbmr -> kcrrge Workaround
Recover the whole datafile rather than an individual block i.e. do media recovery rather than block media recovery
| Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice. |
References Bug:8341623 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article 实际解决方案； 先从NBU中（备份片中）恢复出所有归档日志到本地归档目录； （Rac 环境）若归档日志分放在不同目录，需要全拷贝到恢复节点；（然后再关掉另外的节点） |