V$SYSMETRIC_HISTORY Maintains a historical view of the metrics previously in V$SYSMETRIC. This view is time limited.
DBA_HIST_SYSMETRIC_HISTORY Provides a longer-term view of historical system metrics.
DBA_OUTSTANDING_ALERTS Contains current database alerts (this view was introduced earlier in this section).
DBA_ALERT_HISTORY Provides a history of threshold alerts that have been resolved, and provides a history of nonthreshold alerts.
DBA_THRESHOLDS Defines the threshold settings for the given instance.
V$ALERT_TYPES Provides information on various alert types.
If you have ever asked yourself, ''How much memory should I allocate to the database buffer cache?" then Automatic Shared Memory Management (ASMM) might just be the thing for you. Of course, if you are a control freak, then you might just not like it at all. Oracle 10g allows you to define the size of a new parameter, sga_target, and it will allocate that memory as it thinks best to the default buffer cache, the shared pool, the large pool, and the java pool. Setting sga_target to 0 disables ASMM, which is the default setting.
Regardless of the setting of sga_target, you still need to manually set the following parameters:
The log buffer
The keep buffer pool
The recycle buffer pool
The new streams pool
Nondefault block-sized buffer cache pools
Also, you must set statistics_level to TYPICAL or ALL to use ASMM. Also, if one of the ASMM parameters (e.g., shared_pool_size) is set to a non-zero value, then the value that the parameter is set to will be considered a minimum size for that memory area.
The sga_target parameter is a dynamic parameter, so if you find that you need additional memory allocated to your database while it's up and running, all you need to do is issue an alter system command and allocate more memory to the database (assuming the memory is available).