JDBC Transaction Log Persistence for Database Failover

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems for processing transactions, such as WebLogic application servers, face complexity and cost issues in administering transaction logs due to the need for costly and complex dual-ported SCSI disks or distributed file systems for failover support.

Innovation Solution

Configuring Java Database Connectivity (JDBC) TLOG stores with a data source or database instead of a file system to store primary transaction logs, allowing for database persistence and leveraging high availability features for disaster recovery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If dual-ported SCSI disks or distributed file systems are used for transaction log storage to support failover, then system reliability is improved, but device complexity and administration cost increase

Engineering Contradiction:

Improvefailover supportVSAvoidadministration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a database management system as an intermediary layer between the transaction manager and the storage system. The TLOG store uses standard JDBC connectivity to access the database, which handles all storage operations, replication, and failover logic. This mediator eliminates the need for complex distributed file systems while maintaining reliability through the database's native high-availability features.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent leverages database replication capabilities to create copies of transaction log data across multiple database instances. Instead of implementing complex distributed file system replication, the system uses the database's built-in replication mechanisms to maintain redundant copies of TLOG data, ensuring failover support while simplifying the storage architecture.

Inventive Principle:

Principle #26Copying

2Reliability

If dual-ported SCSI disks or distributed file systems are used for transaction log storage, then system reliability is improved, but cost increases

Engineering Contradiction:

Improvefailover supportVSAvoidcost

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent makes the database management system perform multiple functions: it stores application data, manages transaction logs, handles replication, and provides failover support. By using the existing database infrastructure for TLOG storage, the system eliminates the need for separate expensive distributed file system hardware and software, reducing overall cost while maintaining reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent replaces expensive, specialized distributed file system components with standard, widely-available database management systems that use conventional storage hardware. The JDBC-based TLOG store uses ordinary database tables and storage resources that are already present in most enterprise environments, significantly reducing hardware and software costs while maintaining failover capabilities through database replication.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

3Ease of operation

If JDBC TLOG stores are used instead of file systems, then administration is simplified and cost is reduced, but compatibility with existing transaction log systems must be maintained

Engineering Contradiction:

Improveadministration easeVSAvoidsystem compatibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent changes the storage parameter from file system-based to database-based while maintaining the same transaction log interface and format. The TLOG store continues to use the same logging format and structure, but the underlying storage medium changes from files to database tables accessed via JDBC. This parameter change simplifies administration by using standard database tools while maintaining compatibility with the transaction manager through the unchanged log interface.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS10127259B2System and method for database persistence of transaction logs

Publication Date: 2018.11.13 ORACLE INT CORP

AI summary

A system and method for database persistence of transaction logs (TLOGs). Embodiments of the invention allow an administrator to configure their system to associate one or more Java Database Connectivity (JDBC) TLOG stores with a data source or database instead of a file system, for use in storing the primary TLOG. This provides an opportunity to exploit the high availability features of a database system; improve handling of disaster recovery scenarios, such as cross-site recovery using database replication; and alleviate the need for third-party distributed file system components, together with their cost and complexity.