Audit Trail Data Capture via Segmented Storage

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in reliably capturing audit trail data without impacting regular request processing, particularly in ensuring critical data is not lost during high-demand scenarios.

Innovation Solution

Classifying requests into critical and non-critical categories, where critical requests are immediately stored in non-volatile storage, and non-critical requests are stored in volatile memory for later transfer, optimizing resource usage and ensuring data reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all audit trail data is stored immediately in non-volatile storage, then reliability of data capture is improved, but processing overhead and system performance deteriorate

Engineering Contradiction:

Improvereliability of critical audit data captureVSAvoidrequest processing throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent segments audit trail data into two categories: critical audit data and non-critical audit data. Critical audit data is immediately stored in non-volatile storage to ensure reliability, while non-critical audit data is stored in volatile memory first and then transferred to non-volatile storage later. This segmentation resolves the contradiction by applying different storage strategies to different data types, ensuring critical data reliability while maintaining system throughput.

Inventive Principle:

Principle #1Segmentation

2Productivity

If audit trail data is stored in volatile memory only, then processing overhead is reduced, but data reliability deteriorates due to potential loss

Engineering Contradiction:

Improveprocessing efficiencyVSAvoiddata retention reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary action by first storing non-critical audit data in volatile memory for quick processing, then subsequently transferring it to non-volatile storage. This two-stage approach allows the system to maintain high processing efficiency initially while still ensuring data reliability through the follow-up transfer operation, resolving the contradiction between processing efficiency and data retention reliability.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If critical requests are immediately stored in non-volatile storage, then data loss probability is reduced, but system resources are consumed faster

Engineering Contradiction:

Improvecritical data capture reliabilityVSAvoidsystem resource consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by tailoring the storage approach to the specific characteristics of different request types. Critical requests (which require high reliability) are immediately stored in non-volatile storage, while non-critical requests use a two-stage storage approach through volatile memory. This localized differentiation ensures that system resources are consumed only when necessary for critical data, resolving the contradiction between data capture reliability and resource consumption.

Inventive Principle:

Principle #3Local quality

Data Source

PatentUS9659041B2Model for capturing audit trail data with reduced probability of loss of critical data

Publication Date: 2017.05.23 ORACLE INT CORP

AI summary

An aspect of the present invention provides for capturing of audit trail data related to processing of requests. In an embodiment, the received requests are classified into a first category and a second category. For each request in the first category, the corresponding audit trail data is stored directly into non-volatile storage upon processing of the request. On the other hand, for each request in the second category, the audit trail data is first stored into a volatile memory upon processing of the request, and then later copied from the volatile memory to non-volatile storage. Thus, the audit trail data corresponding to both categories of requests is eventually available stored on non-volatile storage.