Active Inactive Table Space Containers Database Redistribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for redistributing data across partitions in a relational database, such as DB2, are inefficient and require downtime, with limited monitoring capabilities, making it difficult for database administrators to manage capacity additions and data balancing effectively.

Innovation Solution

A method that creates active and inactive logical nodes and corresponding table space containers, allowing for on-line data redistribution without the need for the REDISTRIBUTE command, by predefining inactive nodes and activating them as needed to balance data across active and newly added containers, thereby avoiding system downtime.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional data redistribution methods are used in relational databases, then data can be redistributed across partitions, but system downtime is required and the process is inefficient

Engineering Contradiction:
Improvedata redistribution efficiencyVSAvoidsystem downtime
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent pre-creates inactive table space containers before they are needed. When data redistribution is required, these pre-created inactive containers are activated without interrupting database operations. This preliminary preparation eliminates the need for downtime during redistribution, as the infrastructure is already in place and ready for immediate use.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamic activation of table space containers. Containers can transition between inactive and active states based on real-time needs. This dynamic state change allows the system to add storage capacity and redistribute data without shutting down, transforming a static storage structure into a flexible, runtime-adjustable system.

Inventive Principle:
Principle #15Dynamics

2Extent of automation

If traditional data redistribution methods are used, then data can be balanced across partitions, but monitoring capabilities are limited and administrative effort is high

Engineering Contradiction:
Improveautomatic data balancingVSAvoidadministrative effort
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The patent implements self-service through automatic detection and activation of inactive table space containers. The system monitors storage conditions and autonomously activates appropriate containers for data redistribution without requiring manual intervention. This automated self-service reduces administrative burden while maintaining effective data balancing across partitions.

Inventive Principle:
Principle #25Self-service

3Quantity of substance

If table space containers are created for all nodes, then data storage capacity is maximized, but system complexity increases due to managing active and inactive nodes

Engineering Contradiction:
Improvedata storage capacityVSAvoidnode management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent segments table space containers into distinct active and inactive sets. This segmentation allows the system to maintain a large total capacity while managing complexity through clear categorization. Inactive containers are pre-prepared but not actively managed, while only active containers require real-time attention. This division simplifies operational complexity despite maximizing storage capacity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9361351B2Data management via active and inactive table space containers
Publication Date: 2016.06.07 KYNDRYL INC
  • US9361351B2 patent drawing
  • US9361351B2 patent drawing
  • US9361351B2 patent drawing

AI summary

Aspects distribute database data to table space containers as a function of active and inactive node designations. Different groups of active and inactive logical nodes are created in response to integrating a relational database on one or more physical servers. Database node groups are created by marking the active nodes as available for use in data storage and distribution, and the inactive nodes as unavailable. Table space is created for the relational database by defining containers for each of the active and inactive nodes.