Examine this command:
SQL> CREATE DISKROUP data NORMAL REDANDUNCY:
FAILGROUP fgrpl 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’ = ’11.12’,
‘compatible.rdbms’ = ’11.12’,
‘compatible.advm’ = ’11.12’,
‘content_type’ = ‘recovery’;
Which two statements a true about this disk group, created using Grid Infrastructure 12.1?
A.
Each disk in each of the three fail groups is a mirror of the corresponding disk of the other two failure groups.
B.
File created in this disk group always has two copies for each allocation unit: one primary and one secondary.
C.
It can contain ASM Dynamic Volume Manager (ADVM) volumes.
D.
Any database instance with the COMPATIBLE parameter set to 11.2 or higher can access it.
E.
The ASM compatible attributes can be changed to 11.1 for this disk group.
Explanation:
B: NORMAL REDUNDANCY requires the existence of at least two failure groups (see the FAILGROUP clause that follows). Automatic Storage Management
provides redundancy for all files in the disk group according to the attributes specified in the disk group templates. NORMAL REDUNDANCY disk groups can
tolerate the loss of one group.
C: The COMPATIBLE.ADVM attribute determines whether the disk group can contain Oracle ADVM volumes.
Incorrect Answers:
E: The COMPATIBLE.ADVM attribute value must be set to 11.2 or higher. https://docs.oracle.com/database/121/SQLRF/statements_5009.htm#SQLRF01114
Hello
Correct answers are B and D.
C is incorrect because compatible.advm should be >= 11.2
B is not correct. Mirror is applied for extent not AU.
C.D
Hi Jk
Or perhaps there is mistake in the question. May be 11.2 instead of 11.12
regards
If the attribute values is 11.2
then the correct answers B,C & D
C: to create the ADVM volume the compatibility attribute for COMPATIBLE.RDBMS &
COMPATIBLE.ASM must be >= 11.2
I don’t think B is correct: first of all, you can create a template with redundancy MIRROR, HIGH or UNPROTECTED in a disk group with NORMAL REDUNDANCY. On the other hand, ASM stores redundant copies of the file extents, not the allocation unit
I’d choose C & D, providing 11.12 is a mistake, and it is 11.2 instead
In the Exam, they appear like 11.2! “C” and “D” is the correct answer!