Examine this command:
SQl> CREATE DISKGROUP RECO HIGH REDUNDANCY:
FAILGROUP fgrpl1 DISK
‘/dev/disk1’ NAME disk1,
‘/dev/disk2’ NAME disk2,
‘/dev/disk3’ NAME disk3,
FAILGROUP fgrpl2 DISK
‘/dev/disk4’ NAME disk4,
‘/dev/disk5’ NAME disk5,
‘/dev/disk6’ NAME disk6,
FAILGROUP fgrpl3 DISK
‘/dev/disk7’ NAME disk7,
‘/dev/disk8’ NAME disk8,
‘/dev/disk9’ NAME disk9,
ATTRIBUTE ‘au_size’=’4M’,
‘compatible.asm’ = ’12.1’,
‘compatible.rdbms’ = ’12.1’,
‘compatible.advm’ = ’12.1’,
‘content_type’ = ‘recovery’;
Which two statements are true about this disk group?
A.
File created in it have three copies for each allocation unit.
B.
Any database instance with the COMPATIBLE parameter 10.1 and higher can use it.
C.
The Compatible attribute values of the disk group can be changed to lower values.
D.
Files created using a template with the redundancy attributes set to MIRROR will have three-way Mirroring.
E.
The RECO diskgroup may only be used for the FRA.
F.
Files created using a template with the redundancy attribute set to HIGH will have three-way mirroring.
Explanation:
For Oracle ASM to mirror files, specify the redundancy level as NORMAL REDUNDANCY (2-way mirroring by
default for most file types) or HIGH REDUNDANCY (3-way mirroring for all files).
Note:
When a file is created, redundancy and striping attributes are set for that file based on an explicitly named
template or the system template that is the default template for the file type.
Incorrect Answers:
B: Compatible.rdbms is set to 12.1, not to 10.1.
C: The compatible attributes cannot be reversed.
D: With the MIRROR redundancy attribute, the file is written to a disk in one failure group, a mirrored copy of
the file is written to a disk in another failure group.
E: FRA (Flash Recovery Area) is not referenced in the creation of the diskgroup.
https://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_5008.htm
A,F