Database Duration Identifier Mapping for Session Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During database session migration, the reuse of duration identifiers can lead to conflicts between source and destination database servers, as these identifiers are unique within a session and not easily re-mapped, causing issues in memory allocation and termination.
Innovation Solution
A mapping table is created to map conflicted duration identifiers from the source duration tree to new unique identifiers on the destination duration tree, allowing database components to recreate and manage memory durations without knowing the internal structure of the duration tree, thus resolving identifier conflicts and enabling seamless migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If duration identifiers are reused during session migration, then memory allocation efficiency is improved, but identifier conflicts occur between source and destination servers
Solution Approach 1:
A mapping table is introduced as an intermediary data structure that stores the correspondence between source duration identifiers and destination duration identifiers. This mapping table acts as a mediator that allows the system to reuse identifiers in the destination session while maintaining the ability to distinguish and manage memory allocations that originated from the source session, thereby resolving the conflict between identifier reuse and identifier uniqueness.
2Reliability
If duration identifiers are remapped during migration, then identifier conflicts are resolved, but the complexity of the migration process increases
Solution Approach 1:
The mapping table is created and populated with identifier correspondences before the actual session migration begins. By performing the identifier mapping setup in advance, the system avoids the complexity of dynamic remapping during migration execution. The pre-established mapping table allows for straightforward lookup and translation of identifiers throughout the migration process, reducing overall system complexity.
3Manufacturing precision
If database components must know the internal structure of the duration tree, then memory management precision is improved, but the ease of operation deteriorates
Solution Approach 1:
The complex internal structure of the duration tree is extracted and encapsulated within the mapping table, which presents a simplified interface to database components. Instead of requiring components to understand and navigate the hierarchical duration tree structure, they only need to interact with the flat, tabular mapping structure that provides the necessary identifier translations. This extraction isolates the complexity while maintaining precise memory management capabilities.
Data Source
AI summary
Techniques for migrating duration trees from a source database server (or instance) to a destination database server (or instance) are provided. A duration is a memory management construct that allows database components to group related areas of memory together. A source duration tree is captured at the source database server and combined with a destination duration tree at the destination database server. Any duration identifiers in the source duration tree that conflict with (i.e., are the same as) a duration identifier in the destination duration tree are mapped to new duration identifiers.