|
Column |
Data type |
|
OPTIMAL_LOGFILE_SIZE |
NUMBER |
|
ESTD_CLUSTER_AVAILABLE_TIME |
NUMBER |
|
WRITES_MTTR |
NUMBER |
|
WRITES_LOGFILE_SIZE |
NUMBER |
|
WRITES_LOG_CHECKPOINT_SETTINGS |
NUMBER |
|
WRITES_OTHER_SETTINGS |
NUMBER |
|
WRITES_AUTOTUNE |
NUMBER |
|
WRITES_FULL_THREAD_CKPT |
NUMBER |
Table 5.5
–
v$instance_recovery view
The
next section provides some practical tips on ASM
implementation.
Guru Conversation for the
Senior DBA
In this chapter,
the topics of ASM,
ASM files, ASM instance,
etc. have been explored.
There will be some databases in any company using traditional
files as well as ASM managed files. When the author tested
the scenario of using
multiple types of files in a database on Redhat Linux, there
were some DBCA issues with Oracle recognizing these devices.
There is also documentation on Oracle Metalink (#266028.1) for
this problem. Here is a
review of how
a new disk that is
added and configured in a Linux server can be used by ASM.