Framework

Job details

Parameters

Job Summary

• Purpose: The purpose of this job is to manage and maintain the internal framework of the dbWatch engine, specifically for patching or upgrading the dbWatch engine framework.
• Why: This job is crucial to ensure that the dbWatch engine operates efficiently and is up-to-date with the latest patches and enhancements. Regular updates to the framework prevent potential conflicts and issues that could arise from outdated components, and allow for new features and optimizations to be integrated seamlessly.
• Manual checking: To verify the installation and version of the framework manually, the following SQL command can be used:

select 'dbWatch Framework installed.' as "Framework";

Job Implementation Details

• The main procedure involved in this job is ‘dbw_framework_proc’, which is created as part of the job’s implementation. This procedure logs details about the engine framework installation progress.
• The job has cleaning procedures in place to handle failures effectively; specifically, it will drop the ‘dbw_framework_proc’ if the job fails during its execution.

Upgrade Process and Logic

• The job includes two defined upgrades from previous versions:
  • From version 1.0: A new procedure is created or replaced to ensure the task is properly registered within the dbWatch system.
  • From version 1.1: A housekeeping procedure ‘dbw_fix_framework’ is called to check and clean up unnecessary dependencies, followed by its removal.

Automatic Installation Characteristics

• Express Installation: This job supports express installation, meaning it can automate the process without manual prompts, streamlining the patching or upgrading process.
• Force Installation: The job supports force installation, allowing updates to be forcibly applied, ensuring that the engine remains consistent with the latest framework requirements.

Applicability and Execution

• This job is designed specifically for MariaDB platforms, ensuring that only appropriate database instances are targeted for the framework updates.
• The job is scheduled to execute monthly at 05:50, with additional settings to ensure it can run more frequently if necessary, based on the configurations defined in dbWatch Control Center.

Additional Metadata and Descriptions

• The job is categorized under ‘Maintenance’, reflecting its role in maintaining the operational integrity and up-to-dateness of the dbWatch framework within the hosting database environment.

Following these guidelines helps maintain the stability, efficiency, and reliability of the dbWatch engine, particularly in environments utilizing MariaDB. Thus, deploying the updates through this job is key for continuous and smooth operation of the dbWatch infrastructure.