ORA-17500: ODM err:ODM ERROR V-41-3-2-207-5 Mirror Number too large

系統環境：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

Bug 30025955  ORA-17500 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.

Affects:

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)

Fixed:

The fix for 30025955 is first included in

18.1.0

Interim patches may be available for earlier versions - click   to check.

Symptoms:	Related To:
Error May Occur Storage Space Usage Affected	(None Specified)

Description

This bug is only relevant when using Oracle Disk Manager

This 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.