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
Interim patches may be available for earlier versions - click to check.
Symptoms: |
Related To: |
|
Description
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.
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/30327022/viewspace-2696056/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- ORA-17500 ODM err的問題排查
- AIX ODM操作AI
- ODM enable on Veritas
- nodejs Error: request entity too large解決方案NodeJSError
- ora 15181 symbol odm_mkdir not foundSymbol
- [Err] 1709 - Index column size too large. The maximum column size is 767 bytes.Index
- MongoDB ODM: 用於電子商務的MongoDBMongoDB
- insert:key too large to index…Index
- IHS Markit：2018年國產ODM手機公司排名
- 寵物食品行業：從ODM大學畢業後，本土品牌企望破冰向前行業
- Counterpoint：2019年智慧手機ODM市場增長18%
- TrendForce：2021年台灣ODM佔全球伺服器產量的90%伺服器
- ORA-00064: object is too large to allocate on this O/SObject
- Mysql 報Row size too large 65535解決方法MySql
- Row size too large (> 8126)解決辦法
- 【AWR】Suggestions if Your SYSAUX Tablespace Grows Rapidly or Too LargeUXAPI
- gunzip時，提示file too large（問題已解決）
- system image file too large for device hardware configurationdev
- ORA-01555: snapshot too old: rollback segment number with name "" too small
- node接收圖片報錯 PayloadTooLargeError: request entity too largeError
- Index column size too large. The maximum column size is 767 bytesIndex
- ES報錯Result window is too large問題處理薦
- mysql specified key was too long與Index column size too large. The maximum column size is 767 bytes.MySqlIndex
- 上傳報錯 Status Code: 413 Payload Too Large 請教！
- Index column size too large. The maximum column size is 767 bytes.Index
- Java程式碼解決ElasticSearch的Result window is too large問題JavaElasticsearch
- Nginx出現413 Request Entity Too Large錯誤解決方法Nginx
- Nginx 報錯413 Request Entity Too Large 上傳檔案過大Nginx
- MySQL ERROR 1040: Too many connectionsMySqlError
- 【自動化】全球最大手機ODM電子工廠探祕！解密自動化“智造”祕訣解密
- mysql Index column size too large 超過767錯誤解決方案(轉)MySqlIndex
- 1709 - Index column size too large. The maximum column size is 767 bytes.Index
- SQLServer mirror當機後error 9004異常處理SQLServerError
- err Invalid input of type: 'dict'. Convert to a byte, string or number first
- 【es】FATAL [circuit_breaking_exception] [parent] Data too large, data for [＜http_request＞] would beUIExceptionHTTP
- [Mark]解決ElasticSearch深度分頁機制中Result window is too large問題Elasticsearch
- 2020上半年全球主要智慧手機ODM / IDH供應商排名（附原資料表）
- error RS102 too stale to catch upError