Can ASM “_DISABLE_REBALANCE_COMPACT=TRUE" Be Used With NetApp SAN Environment?
(Doc ID 1573768.1)
Last updated on JANUARY 01, 2020
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Oracle 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 Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
28TB sized ASM disk group had 4TB added. At a rebalance power of 10 (ASM compatibility is 188.8.131.52) 3 hours was spent in the second phase (extents rebalance) and an additional 3 hours in the third phase (compacting). Each LUN is 2TB in size and the new LUNs added together in one command. No databases were served by the particular ASM instance used to add the LUNs. The additional time spent in the compacting phase is not shown in the estimated rebalance time and impacted the batch process, so consider setting “_DISABLE_REBALANCE_COMPACT=TRUE” for the ASM instances connected to the NetApp FAS6080 SAN. Is there any reason not to put this setting in place?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!