Framework
Job details
| Name: | Framework |
| Platform: | Oracle |
| Category: | Maintenance Maintenance |
| Description: | Engine framework is used when upgrading earlier versions of dbWatch. Ensures the dbWatch Engine and dbWatch Server run compatible codes. |
| Long description: | Engine framework is used when upgrading earlier versions of dbWatch Engine Framework. This task makes sure that the dbWatch Engine and the dbWatch Server run compatible codes. It also auto-tunes the dbWatch schema. |
| Version: | 3.3 |
| Default schedule: | 50 5 1 * |
| Requires engine install: | Yes |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & maj_version=‘8′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| Remove unescalated status check history | 30 | Days to keep the check history for checks that have alerted but not escalated status |
| Remove check history | 365 | Days to keep the check history |
Job Summary
- Purpose: This job is designed to maintain and ensure compatibility between dbWatch Engine and dbWatch Server, especially during upgrades from previous versions. It includes tasks to auto-tune dbWatch schema by manipulating database statistics and cleaning up historical check data.
- Why: This job is crucial for maintaining the integrity and performance of the dbWatch system. It helps in preventing issues related to compatibility between different versions of the dbWatch Engine and Server, and ensures the removal of obsolete data which could potentially lead to performance degradation.
- Manual checking: You can check the key aspects manually in the database by issuing these SQL commands:
SELECT * FROM dbw_framework_tab_info;SELECT * FROM dbw_framework_tab_del_histr;Details and Operations
The main operations performed by this job include:
- Updating database statistics using gathered table statistics.
- Deletion of outdated records from dbW_checks_history based on specified thresholds or when records involve unescalated checks.
- Inspection and cleanup of data in tables containing date columns, specifically targeting records that reference incorrect future dates (e.g., due to server clock misconfigurations).
- Reporting on the cleanup process by recording which tables had records deleted because of future date issues.
The job uses the following SQL structures:
| SQL Operation | Description |
|---|---|
| “Gather table statistics” | Ensures that statistics for user tables are up-to-date. |
| Conditional data removal | Deletes records from dbW_checks_history older than specified number of days or involves specific check statuses. |
| Data integrity checks | Inserts and updates dbw_framework_tab_info to maintain a log of tables with date issues. |
| Cleanup reporting | Updates dbw_framework_tab_del_histr to keep a track of table cleanup actions. |
Schedule and Frequency
The job is scheduled to run based on a default pattern described in the configuration as:
- “50 5 1 *” – This implies the job runs monthly at 05:50.
Dependencies
- The job depends on various ‘dbw_framework’ related tables and procedures which must be present and correct for successful execution. These dependencies are critical as they support the job’s ability to gather and update the necessary database statistics and perform data integrity checks.
Error Handling
- The job configuration includes detailed procedures for handling exceptions during the execution phase. It uses custom procedures to log errors when encountered and even attempts to conditionally clean up historical data based on specific scenarios.
- Post-execution procedures are also included to handle the purging of error logs exceeding thousand entries, further illustrating the robust error management practices in place.
Reporting
After each execution, reports are generated which detail:
- The version and general framework details.
- Specific tables containing date columns and any discrepancies found regarding future dates.
- Tables from which historical data were deleted indicating the extent of cleanup performed.
This structured and automated monitoring and maintenance facilitated by the dbWatch job are essential for ensuring the operational efficiency and reliability of the dbWatch system on the Oracle platform.