Mapping Files to Physical Devices -- 将数据文件与物理设备一一对应,很有用
Overview of Oracle Database File Mapping Interface
To build these views, storage vendors must provide mapping libraries that are
responsible for mapping their particular I/O stack elements. The database
communicates with these libraries through an external non-Oracle Database process
that is spawned by a background process called FMON. FMON is responsible for
managing the mapping information. Oracle provides a PL/SQL package, DBMS_
STORAGE_MAP, that you use to invoke mapping operations that populate the mapping
views.
FMON进程,负责FILE MAPPING的工作。
Components of File Mapping -- FILE MAPPING的组件
FMON FMON is a background process started by the database whenever the FILE_
MAPPING initialization parameter is set to TRUE. FMON is responsible for: -- FMON进程的主要作用
--- Building mapping information, which is stored in the SGA. This information is
composed of the following structures:
– Files
– File system extents
– Elements
– Subelements
These structures are explained in "Mapping Structures" on page 15-18.
---- Refreshing mapping information when a change occurs because of:
– Changes to datafiles (size)
– Addition or deletion of datafiles
– Changes to the storage configuration (not frequent)
---- Saving mapping information in the data dictionary to maintain a view of the
information that is persistent across startup and shutdown operations
---- Restoring mapping information into the SGA at instance startup. This avoids the
need for a potentially expensive complete rebuild of the mapping information on
every instance startup.
Using the DBMS_STORAGE_MAP Package
Obtaining Information from the File Mapping Views -- 与FILE MAPPING相关的视图
具体的MAPPING的相关方法参见PAGE 468 - 470
Undo Space Data Dictionary Views -- 与UNDO相关的数据字典视图