Directory structure in ASM has a default of +<diskgroup>/<database>/<filetype>/<filename>.
The EXAMPLE tablespace was created with:
CREATE TABLESPACE EXAMPLE DATAFILE ‘+DATA/ORCL/oradata/example_01.dbf’
The asmcmd ls command shows:
ASMCMD>ls -l +DATA/ORCL/oradata/*
Type Redund Striped Type Sys Name
N example_01.dbf => +DATA/ORCL/DATAFILE/EXAMPLE.264.695918623
Which three statements can be verified by from the information provided?
A.
The ASM file +DATA/ORCL/oradata/example_01.dbf has an alias of
+DATA/ORCL/DATAFILE/EXAMPLE.264.695918623.
B.
The ASM system file +DATA/ORCL/DATAFILE/EXAMPLE.264.695918623 has an alias of
+DATA/ORCL/oradata/example_01.dbf.
C.
The default path indicates that the file is an oradata file belonging to the ORCL database.
D.
The default path indicates that the file is a data file belonging to the ORCL database.
E.
+DATA/ORCL/oradata/example_01.dbf is the name of the file in V$DBFILE in the database
instance.
F.
+DATA/ORCL/DATAFILE/EXAMPLE.264.695918623 is the name of the file in V$DBFILE in the
database instance.
Explanation:
Fully Qualified ASM File Names
Every file created in ASM gets a system-generated file name, known as the fully qualified file
name.
You cannot set the fully qualified file name.
ASM guarantees uniqueness within the ASM environment.
The fully qualified file name is used in database views that display Oracle Database file names.
D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 9 – 11
Answer: BDE
Because:
select name from v$dbfile;
NAME
———————————–
+DATA/test/oradata/example1_01.dbf
A is wrong. reversed
B is right.
C is not oradata
D is right
E is right. alias used in V$datafile
F is wrong
So B.D.E. are correct
I think so. LIKE