What are the advantages of variable extent size support for large ASM files? (Choose two.)
A.
It improves performance in the extended cluster configuration by reading from a local copy of an extent.
B.
It improves resync operations when the disk comes online after being taken offline for maintenance purposes.
C.
This feature enables faster file opens because of the reduction in the amount of memory that is required to store file extents.
D.
Fewer extent pointers are needed to describe the file and less memory is required to manage the extent maps in the shared pool.
The contents of Oracle ASM files are stored in a disk group as a set, or collection, of extents that are stored on individual disks within disk groups. Each extent resides on an individual disk. Extents consist of one or more allocation units (AU). To accommodate increasingly larger files, Oracle ASM uses variable size extents.
Variable size extents enable support for larger Oracle ASM data files, reduce SGA memory requirements for very large databases, and improve performance for file create and open operations. The initial extent size equals the disk group allocation unit size and it increases by a factor of 4 or 16 at predefined thresholds. This feature is automatic for newly created and resized data files when specific disk group compatibility attributes are set to 11.1 or higher.
The extent size of a file varies as follows:
Extent size always equals the disk group AU size for the first 20000 extent sets (0 – 19999).
Extent size equals 4*AU size for the next 20000 extent sets (20000 – 39999).
Extent size equals 16*AU size for the next 20000 and higher extent sets (40000+).