Name: |
Max datafiles check |
Platform: |
Oracle |
Category: |
Availability |
Description: |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
Long description: |
From Oracle 9i, an attempt to add a file whose number is greater than MAXDATAFILES (‘hard limit’), but less than or equal to DB_FILES (‘soft limit’), causes the Oracle control file to expand automatically. Within the ora parameter ‘db_files’ applies to the ‘soft limit’. The MAXDATAFILES value stored in the Oracle control files applies to the ‘hard limit’. |
Version: |
2.7 |
Default schedule: |
15 5,17 * * |
Requires engine install: |
Yes |
Compatibility tag: |
[CDATA[.[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & _priv_read_v_controlfile_record_section = ‘1’ & _priv_read_v_parameter = ‘1’ |
Parameters |
|
|
Name |
Default value |
Description |
warning threshold “soft limit” |
5 |
Warning threshold – how many data files can be allocated to the Oracle instance before the init ora parameter “db_files” value is reached (“db_file” is a static parameter). |
warning threshold “hard limit” |
5 |
Warning threshed – how many data files can be allocated to the Oracle instance before the MAXDATAFILES limit, stored in the Oracle control files, is reached. Your will have to recreate control files to change this limit. |
alarm threshold “soft limit” |
2 |
Alarm threshed – how many data files can be allocated to the Oracle instance before the init ora parameter “db_files” value is reached (“db_file” is a static parameter). |
alarm threshold “hard limit” |
2 |
Alarm threshed – how many data files can be allocated to the Oracle instance before the MAXDATAFILES limit, stored in the Oracle control files, is reached. Your will have to recreate control files to change this limit. |
← Listener status check / Database mount state →
Post your comment on this topic.