系统环境：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 30025955ORA-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
Clickherefor details of each of the sections below.

Affects:
Product (Component)Oracle Server (Rdbms)Range of versionsbelievedto be affectedVersions BELOW 12.2Versionsconfirmedas being affected(None Specified)Platforms affectedGeneric (all / most platforms affected)
Fixed:
The fix for 30025955 is first included in18.1.0
Interim patches may be available for earlier versions - clickhereto check.
Symptoms:Related To:Error May OccurStorage Space Usage Affected(None Specified)Description
This bug is only relevant when using Oracle Disk Manager

Thisfixes2problemswithdiagnosticmessages(itdoesnotfixtherootcauseofanyexistingblockcorruption).Thefirstproblemisthismsginthealertlogwhichshouldn'thappen:ORA-17500:ODMerr...MirrornumbertoolargeforgivenoffsetThesecondproblemistracefilesmsgsnotshowingthecorrectmirrornamewhereagoodversionoftheblockwasread,egthemessageshows:Readdatafilemirror'Notabletofindmirrorname'...foundvaliddataReaddatafilemirror''foundvaliddataRediscoveryNotesThealertloghasthiserrormesssagewhichshouldn'thappen:----Errorsinfile<tracefile_filespec>ORA-17500:ODMerr:ODMERRORV-41-3-2-207-5Mirrornumbertoolargeforgivenoffset----And/orthetracefilehasthesekindofmessages:-onODMstorage:Readdatafilemirror'Notabletofindmirrorname'(file<f>,block<b>)foundvaliddata-onASMstorage:Readdatafilemirror''(file<f>,block<b>)foundvaliddataWorkaroundNone.