ASM alert.log shows messages "used AU total mismatch: DD={29273, 0} AT={29250, 0}"
(Doc ID 1528617.1)
Last updated on JANUARY 24, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
ASM alert log reports below mismatch info
From ASM alert.log
NOTE: disk DATA_01_0000, used AU total mismatch: DD={29273, 0} AT={29250, 0}
GMON checking disk 1 for group 3 at 56 for pid 22, osid 16465
GMON checking disk 2 for group 3 at 57 for pid 22, osid 16465
NOTE: disk DATA_01_0002, used AU total mismatch: DD={29266, 0} AT={29250, 0}
GMON checking disk 3 for group 3 at 58 for pid 22, osid 16465
NOTE: disk DATA_01_0003, used AU total mismatch: DD={29263, 0} AT={29250, 0}
GMON checking disk 4 for group 3 at 59 for pid 22, osid 16465
NOTE: disk DATA_01_0004, used AU total mismatch: DD={29016, 0} AT={29249, 0}
NOTE: disk DATA_01_0000, used AU total mismatch: DD={29273, 0} AT={29250, 0}
GMON checking disk 1 for group 3 at 56 for pid 22, osid 16465
GMON checking disk 2 for group 3 at 57 for pid 22, osid 16465
NOTE: disk DATA_01_0002, used AU total mismatch: DD={29266, 0} AT={29250, 0}
GMON checking disk 3 for group 3 at 58 for pid 22, osid 16465
NOTE: disk DATA_01_0003, used AU total mismatch: DD={29263, 0} AT={29250, 0}
GMON checking disk 4 for group 3 at 59 for pid 22, osid 16465
NOTE: disk DATA_01_0004, used AU total mismatch: DD={29016, 0} AT={29249, 0}
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |