Database Migration via Image Copy and Metadata Translation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for migrating database data between platforms are inefficient and prone to errors, particularly when using image copies, due to the need for manual input and compatibility issues between source and target databases.

Innovation Solution

A computer-implemented method that creates an image copy of the source database, collects metadata to ensure compatibility, and uses this metadata to refresh the target database, automatically translating object identifiers and verifying version information to facilitate seamless data migration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the unload/reload process is used to migrate data, then version compatibility is improved, but processing time and processor usage increase significantly

Engineering Contradiction:
Improveversion compatibilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating an image copy of the source database and collecting metadata describing the source database structure before actual data migration. This preparation enables the subsequent fast image copy transfer while maintaining version compatibility through pre-collected metadata, avoiding the time-consuming unload/reload process during the actual migration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary metadata structure that describes the source database and serves as a bridge between the source and target databases. This metadata enables automatic compatibility verification and object identifier translation, allowing the system to use the fast image copy approach while maintaining version compatibility without manual intervention.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the image copy approach is used for data migration, then processing time is reduced, but compatibility issues and manual input requirements increase

Engineering Contradiction:
Improvemigration speedVSAvoidmanual input requirement
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system implements self-service by automatically collecting metadata from the source database, verifying compatibility between source and target databases, and translating object identifiers without manual intervention. The metadata-driven approach enables the system to self-configure the migration process, eliminating the manual input requirements that normally accompany image copy migrations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent employs feedback mechanisms by using collected metadata to verify compatibility between source and target databases before migration. The system continuously references the metadata during the migration process to ensure compatibility and automatically adjust for any discrepancies, providing real-time feedback that eliminates manual verification needs.

Inventive Principle:
Principle #23Feedback

3Productivity

If the image copy approach is used for data migration, then processing time is reduced, but error rates increase due to manual translation of object identifiers

Engineering Contradiction:
Improvemigration speedVSAvoiderror rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent replaces the manual mechanical process of translating object identifiers with an automated computer-based system. The metadata collected from the source database enables automatic translation of object identifiers to the target database schema, eliminating typographical errors and other mistakes inherent in manual translation while maintaining fast migration speeds.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The metadata structure serves as an intermediary that bridges the source and target database schemas. This metadata contains the mapping information needed to automatically translate object identifiers, serving as a reliable reference that eliminates errors associated with manual translation while enabling fast automated migration.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If the unload/reload process is used to migrate data, then version compatibility is improved, but processor usage and cost increase

Engineering Contradiction:
Improveversion compatibilityVSAvoidprocessor usage
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary actions by creating an image copy and collecting metadata before migration, which enables the subsequent data transfer to proceed rapidly using the image copy mechanism. This preliminary preparation maintains version compatibility through metadata verification while avoiding the intensive processor usage of unload/reload during the actual migration execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The metadata acts as an intermediary that enables version compatibility verification without requiring the intensive processor operations of unload/reload. The pre-collected metadata allows the system to verify compatibility and automatically adjust for version differences during the fast image copy transfer, dramatically reducing processor usage compared to traditional methods.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10366074B2Systems and methods for migrating database data
Publication Date: 2019.07.30 BMC SOFTWARE INC
  • US10366074B2 patent drawing
  • US10366074B2 patent drawing
  • US10366074B2 patent drawing

AI summary

In one aspect, a computer-implemented method for ensuring a source database (e.g., target space or index space) has correct version information before a migration includes executing, using at least one processor, instructions recorded on a computer-readable storage medium. The instructions include determining whether a table has been changed since a most recent alter of the table, performing an update on the table when it is determined that the table has not been changed since the most recent alter, and performing a rollback on the table after the update. The method may also include creating an image copy of the data in the source database and refreshing data in a target database with the image copy of the data in the source database. The method may also include automatically repairing the target database when the version information of the target does not correspond with the version information for the source.