Statistics migration
Job details
| Name: | Statistics migration |
| Platform: | Oracle |
| Category: | License and compliance |
| Premium package: | Migration EM12 to CC |
| Description: | Migrates statistics from a number of tasks from dbWatch version 12 to dbWatch CC. |
| Long description: | Migrates statistics from a number of tasks from dbWatch version 12 to dbWatch CC. |
| Version: | 1.41 |
| Default schedule: | 1 1 1 1 |
| Requires engine install: | Yes |
| Compatibility tag: | .[type=‘instance’ & databasetype=‘oracle’]/.[hasengine=‘YES’ & _priv_read_v_datafile = ‘1′ & _priv_read_v_tempfile = ‘1′] |
Parameters
| Name | Default value | Description |
|---|---|---|
| copy statistics | NO | If set to YES the procedure will copy history data from dbWatch 12 engine to dbWatch CC engine. |
| dbWatch12 engine | AUTO | Name of dbWatch 12 engine to copy statistics from. If set to AUTO (default value) the procedure will find automatically the last in use dbWatch engine. |
Job Summary
- Purpose: To migrate statistics data from dbWatch version 12 to dbWatch Control Center (dbWatch CC).
- Why: This job is essential for organizations upgrading from dbWatch version 12 to dbWatch CC, ensuring that all historical and operational statistics are transferred seamlessly. This allows for continued monitoring and analysis without data loss.
- Manual checking: Can be done by running queries on the database to verify the migration tables and procedures are in place and functioning as expected.
Job Features
- Statistics Handled: The job includes migration of statistics related to various database aspects such as blocking detectors, buffer cache, CPU load, database uptime, session load, and more.
- Procedural Implementation: The migration is achieved through a set of SQL operations executed in a defined sequence, including data insertion, updates, and deletion as necessary to sync dbWatch CC with historical data of dbWatch version 12.
- Dependency Cleaning: The job includes mechanisms to handle dependencies and cleanup on failures, ensuring that partial migrations do not leave the system in an inconsistent state.
Operations Details
- Migration Scope: Historical data related to various statistics such as session loads, redo statistics, blocking detectors, etc., are migrated.
- SQL Operations: Includes table creation for migration tracking, data deletion, and batch data insertion operations aimed at specific statistic categories.
- Error Handling: Procedures are in place to manage errors during migration, with catch blocks designed to log and handle exceptions smoothly.
Dependencies and Pre-requisites
- Database Checks: Ensures relevant dbWatch 12 database objects are present before attempting migration.
- Schema Preparation: Involves schema name retrieval and validation, creating a seamless connection between datasets from different versions.
- Data Integrity: Checkpoints and validations are performed to ensure data correctness post-migration, with specific tasks aimed at preserving database performance and integrity.
Scheduled Tasks and Automations
- Scheduling: Migration tasks are programmatically scheduled to ensure minimal downtime.
- Automations: Includes automated scripts for pre-migration checks, actual data migration, and post-migration cleanup.
- Monitoring: Continuous monitoring is proposed to observe the status of migration and system health post migration.
Security and Compliance
- Data Handling: All data handling operations are performed adhering to standard security protocols ensuring data privacy and integrity.
- Compliance Checks: Post-migration scripts ensure that the system remains compliant with existing standards and configurations necessary for dbWatch operations.
Optimization and Performance
- Execution Plans: The job is optimized for fast execution with minimal resource consumption, ensuring that the database performance is not significantly impacted.
- Resource Allocation: Adequate resources are allocated dynamically based on the data size and system capabilities to enhance performance.
Reporting and Alerts
- Migration Report: Detailed reports are generated post-migration outlining the activities undertaken, success rate, issues encountered, and corrective actions applied.
- Alert Mechanisms: Configured to trigger alerts in case of migration failure or partial successes requiring manual intervention.
This comprehensive job assures a smooth transition from dbWatch version 12 to dbWatch CC, maintaining the continuity of database monitoring and statistics analysis without any hindrance.