Database Reference
In-Depth Information
ASMCMD> ls
DATA/
VOCR/
ASMCMD> cd DATA
ASMCMD> cd KHDB
On the ASM file system, each file is given a fully qualified file name during its creation.
+diskgroup/dbname/filetype/filetypetag.file.incarnation.
For example, the system tablespace is stored in:
file:'+VOCR/KHDB/DATAFILE/SYSTEM.256.789808227'
ASMCMD> ls -l +VOCR/KHDB/DATAFILE/SYSTEM.256.789808227
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE NOV 01 07:00:00 Y SYSTEM.256.789808227
The control file: '+DATA/KHDB/CONTROLFILE/ Current.256.789808289':
ASMCMD> ls -l +DATA/KHDB/CONTROLFILE/Current.256.789808289
Type Redund Striped Time Sys Name
CONTROLFILE UNPROT FINE NOV 01 07:00:00 Y Current.256.789808289
This fully qualified file name also indicates the file directory structure where the file is located. You can use the cd
command to navigate the directory structure to reach the leaf directory where this file is located.
ASMCMD> cd +VOCR/KHDB/DATAFILE
ASMCMD> ls
SYSAUX.257.789808227
SYSTEM.256.789808227
UNDOTBS1.258.789808227
UNDOTBS2.264.789808307
USERS.259.789808227
The ASM file that stores OCR and voting disks looks like this:
ASMCMD> ls -l +VOCR/kr720n-scan/OCRFILE/REGISTRY.255.789801895
Type Redund Striped Time Sys Name
OCRFILE UNPROT COARSE NOV 01 07:00:00 Y REGISTRY.255.789801895
This is the ASM instance spfile:
ASMCMD> ls -l +VOCR/kr720n-scan/ASMPARAMETERFILE/REGISTRY.253.789801893
Type Redund Striped Time Sys Name
ASMPARAMETERFILE UNPROT COARSE JUL 28 05:00:00 Y REGISTRY.253.789801893
■
Since these two files are not the database file, they use the Clusterware name 'kr720n-scan' instead of
a database name on the file path.
Note
