ASRU (Asm Storage Reclamation Utility) failed to resize the disk
(Doc ID 1383359.1)
Last updated on AUGUST 03, 2021
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
At ASRU compaction phase, disk was resized to smaller size. After resize, if the disk size can not be divided exactly by Allocation Unit(AU), ASM will resize the disk to smaller size which can be divided exactly by AU size.
At the expansion phase, ASRU resize failed because disk size was not expected by ASRU.
For example, if ASRU try to resize the disk to 920M and AU size was 32M. 32 can not be divided exactly by 920. So ASM resize the disk to 896.
Actually this problem may occur when ASM AU size was not 1MB.
Although we can resize the disk to original size manually, it is not convenient.
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 |