Dynamic Object Link Connection for Cluster Database Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cluster database systems, accessing migrated objects is challenging due to the need for manual intervention by database administrators to reconfigure connections, leading to delays and unavailability of objects, especially when multiple objects require remote access with high transient rates, causing security and manageability issues.

Innovation Solution

The implementation of a service-to-instance mapping system that uses a global listener to dynamically establish connections to migrated objects through object links, which are instance-independent, allowing the listener to redirect connections to the new provider instance without administrator intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If instance-dependent database links are used to connect to specific database instances, then connection accuracy is improved, but system flexibility deteriorates when instances migrate or fail

Engineering Contradiction:
Improveconnection accuracyVSAvoidsystem flexibility
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent introduces a service name as an intermediary layer between the client and the database instance. Instead of directly connecting to a specific instance using instance-dependent links, clients connect to a service name which acts as a mediator. The service name resolves to the current provider instance dynamically, allowing connections to persist even when instances migrate or fail. This intermediary resolves the contradiction by maintaining connection accuracy through proper service resolution while enabling system flexibility through dynamic instance mapping.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements dynamic connection establishment by making the mapping between service names and provider instances changeable over time. The service-to-instance mapping is not fixed but can be updated when instances migrate or when load balancing is required. This dynamic resolution mechanism allows the system to adapt to changing conditions while maintaining accurate connections, resolving the contradiction between connection accuracy and system flexibility.

Inventive Principle:
Principle #15Dynamics

2Reliability

If manual reconfiguration by database administrators is performed after instance migration, then connection reliability is improved, but system availability deteriorates due to downtime

Engineering Contradiction:
Improveconnection reliabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables the database system to automatically handle connection routing after instance migration without requiring manual intervention from database administrators. The service name to provider instance mapping is automatically updated when instances migrate, and clients automatically reconnect to the new provider through the service name resolution mechanism. This self-service capability maintains connection reliability while eliminating the downtime associated with manual reconfiguration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary action by pre-establishing service names that map to provider instances before migration occurs. When migration happens, the service name continues to resolve to the new provider instance automatically, eliminating the need for post-migration reconfiguration. This preliminary service name setup ensures continuous availability and resolves the contradiction between reliability and time loss.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If multiple instance-specific database links are created for different objects, then access precision is improved, but device complexity deteriorates due to duplication of connection information

Engineering Contradiction:
Improveaccess precisionVSAvoidlink configuration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates a universal service name that can be used to access multiple different provider instances and objects through a single connection configuration. Instead of requiring separate instance-specific database links for each object, the service name serves as a universal entry point that dynamically resolves to the appropriate provider instance. This multi-functionality reduces the duplication of connection information while maintaining precise access to the correct objects, resolving the contradiction between access precision and device complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If database links are dynamically created and dropped for transient objects, then system adaptability is improved, but security and manageability deteriorate

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidsecurity risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent uses service names as intermediaries that provide stable, long-term identification for objects even when their provider instances change transiently. Instead of creating and dropping links for each transient object appearance, the service name acts as a persistent identifier that maintains security and manageability. The service name to provider instance mapping can be dynamically updated without affecting the security model, as the service name itself remains a stable, secure identifier throughout the object's lifecycle.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7502776B2Dynamic connection establishment using an object link
Publication Date: 2009.03.10 ORACLE INT CORP
  • US7502776B2 patent drawing
  • US7502776B2 patent drawing
  • US7502776B2 patent drawing

AI summary

Techniques are provided for creating dynamic connections to objects on remote database clusters. Service-to-instance mapping information is provided to a listener process for a cluster database. The service-to-instance mapping indicates the current provider instance(s) of each object within the cluster database. To establish a connection to a remote object, a sending process uses an object link. The object link identifies the desired destination object, but not the provider instance of the object. The object link also contains a authentication information and other connection information that exists in regular database links. The global listener for the cluster database uses the service-to-instance mapping to determine which instance is the current provider of the specified object, and dynamically distinguishes the appropriate database instance as the endpoint of the connection.