Database mount state
Job details
| Name: | Database mount state |
| 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: | |
| Version: | 1.0 |
| Default schedule: | 15m |
| Requires engine install: | No |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’] |
Parameters
| Name | Default value | Description |
|---|---|---|
| correct_mount_state | READ WRITE | Correct mount status for OK signal |
Job Summary
- Purpose: The purpose of this job is to monitor and verify that an Oracle database instance is in the correct mount state as specified by the user.
- Why: This job is important to ensure that the database is operating in an expected mode (e.g., READ WRITE). Operating in an incorrect mode could lead to data accessibility issues, reduced performance, or system downtime, depending on the configuration and operational requirements. Ensuring the database is in the correct mount state is crucial for the availability and reliability of services that depend on the database.
- Manual Checking: You can manually check the current mount state of the Oracle database by executing the following SQL command in an SQL session:
select open_mode from v$database;Configuration Details
This monitoring job is configured specifically for Oracle database instances. It evaluates the current mode against a predefined ‘correct mount state’ and alerts if this state is not met.
Properties Overview
- Name: Oracle Database mount state noschema
- Version: 1.0
- Company: dbwatch.com
- Artifact ID: oracle_noschema_database_mount_state
- Category: Availability
- Express Install: false
- Default Schedule: Every 15 minutes
Compatibility
The job is designed to operate on entities that match the criteria `.[type=‘instance’ & databasetype=‘oracle’]`, ensuring it only runs on Oracle database instances.
Job Execution
The job uses SQL and JavaScript to determine the state of the database:
| Engine | Code |
|---|---|
| SQL | select open_mode from v$database |
| JavaScript | var open_mode = input.get(0).asString(); var status = 0; var msg; if (open_mode.equals(correct_mount_state)) { status = 0; msg = “Database open in correct mount state: “ + open_mode + “. Correct mount state configured: “ + correct_mount_state + “.”; } else { status = 2; msg = “Database NOT open in correct mount state: “ + open_mode + “. Correct mount state configured: “ + correct_mount_state + “.”; } result.setStatus(status, msg); |
Reporting
The results of this job are compiled into a report template named “Database mount status”. The report includes a detailed table illustrating the database mount status across monitored instances. The table is dynamically populated from the job’s execution results.
The table structure in the report is as follows:
Table Structure
| Details |
|---|
| The above entry reflects the specifics of database mount status extracted from job results |
Report Summary
The report provides a concise summary of database mount statuses across all selected instances, matching the job’s compatibility specification. Each entry in the report signifies the result for a particular instance and consists of critical details that help in quick assessment and decision-making.