IMS Change Mapper for Database Maintenance Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current database maintenance processes are inefficient and costly, often requiring databases to be taken offline for reorganization and backup, and involve unnecessary log data management, leading to redundant processes and potential business disruptions due to lack of real-time monitoring of database changes.
Innovation Solution
The Change Mapper system monitors IMS logs in real-time or during archive to identify changed database records, analyzing log data to determine necessary maintenance activities based on user-defined thresholds, allowing for targeted and scheduled maintenance without scanning entire datasets, integrating with existing utilities for automation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database maintenance is performed periodically on all databases, then database reliability is improved, but productivity deteriorates due to unnecessary maintenance activities and business disruptions
Solution Approach 1:
The system changes the parameter of maintenance scheduling from fixed periodic intervals to dynamic thresholds based on actual database change activity. By monitoring log records and calculating change activity metrics, the system determines when maintenance is actually needed rather than following a rigid schedule, thus avoiding unnecessary maintenance that disrupts productivity while ensuring reliability when changes occur
Solution Approach 2:
The database maintenance system performs self-service by automatically monitoring its own change activity through log analysis and autonomously determining when maintenance is required. The system uses exit calls from IMS logger and log archive modules to capture change information, calculates change activity thresholds, and triggers maintenance only when necessary, eliminating the need for external periodic intervention
2Productivity
If real-time monitoring of database changes is implemented, then productivity is improved by reducing unnecessary maintenance, but device complexity increases due to additional monitoring infrastructure
Solution Approach 1:
The system uses exit calls as intermediaries between the IMS logging system and the maintenance decision-making process. These exit calls capture change information without requiring direct integration with database operations, providing a simplified interface that monitors database changes while maintaining independence from the core IMS system, thus reducing overall complexity
Solution Approach 2:
The system performs preliminary analysis of log records to build a change map that identifies which databases have changed and by how much. This preliminary action occurs during log archiving or in real-time before maintenance decisions are made, allowing the system to prepare maintenance recommendations in advance without adding complex real-time analysis infrastructure during critical maintenance windows
Data Source
AI summary
A method, system and device for monitoring internal database log events in a computer database environment are described. As database updates are detected they are analyzed and used to determine which of several kinds of database maintenance are required. The database administrator is therefore presented with information to allow for more accurate maintenance scheduling and able to prevent unnecessary database maintenance outages.