系统环境：Oracle Linux 7.4
数据库环境：12.2.0.1.20200114
数据库告警日志近几日频繁提示：
ORA-17500: ODM err:ODM ERROR V-41-3-2-207-5 Mirror number too large for given offset
This note gives a brief overview of bug 30025955.
The content was last updated on: 15-APR-2020
Click
here for details of each of the sections below.
Product ( Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions BELOW 12.2 Versions confirmed as being affected
- (None Specified)
Platforms affected Generic (all / most platforms affected)
The fix for 30025955 is first included in
- 18.1.0
Interim patches may be available for earlier versions - click here to check.
Symptoms: |
Related To: |
|
|
This bug is only relevant when using Oracle Disk ManagerThis fixes 2 problems with diagnostic messages (it does not fix the root cause of any existing block corruption). The first problem is this msg in the alert log which shouldn't happen: ORA-17500: ODM err ... Mirror number too large for given offset The second problem is tracefiles msgs not showing the correct mirror name where a good version of the block was read, eg the message shows: Read datafile mirror 'Not able to find mirror name' ...found valid data Read datafile mirror '' found valid data Rediscovery NotesThe alert log has this error messsage which shouldn't happen: ---- Errors in file <tracefile_filespec> ORA-17500: ODM err:ODM ERROR V-41-3-2-207-5 Mirror number too large for given offset ---- And/or the tracefile has these kind of messages: - on ODM storage: Read datafile mirror 'Not able to find mirror name' (file <f>, block <b>) found valid data - on ASM storage: Read datafile mirror '' (file <f>, block <b>) found valid data WorkaroundNone.
免责声明：本站发布的内容（图片、视频和文字）以原创、转载和分享为主，文章观点不代表本网站立场，如果涉及侵权请联系站长邮箱：is@yisu.com进行举报，并提供相关证据，一经查实，将立刻删除涉嫌侵权内容。
