Database Diagnostic Engine Automated Symptom-Based Error Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database malfunctions due to errors like data inconsistencies and misconfigurations require extensive resources for troubleshooting, leading to downtime and productivity losses.

Innovation Solution

A database diagnostic engine generates a user interface for clients to input symptoms, performs checks based on user inputs, and identifies remedial actions to correct errors, minimizing the time and resources needed for database repair.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual troubleshooting is performed for database errors, then comprehensive error detection is possible, but time consumption and resource requirements increase significantly

Engineering Contradiction:
Improveerror detection capabilityVSAvoidtroubleshooting time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system enables self-service troubleshooting by automatically generating diagnostic checks based on user-provided symptoms and executing them without requiring expert intervention. The database system itself performs the diagnosis through automated check generation and execution, reducing dependency on manual troubleshooting resources while maintaining comprehensive error detection.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-generating multiple diagnostic checks that can be executed based on symptom selection. Instead of manually crafting diagnostic procedures during troubleshooting, the system prepares diagnostic checks in advance that can be systematically applied to detected symptoms, reducing the time required for error detection.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If extensive troubleshooting resources are allocated to database errors, then error detection accuracy improves, but resource consumption and downtime increase

Engineering Contradiction:
Improveerror detection accuracyVSAvoiddatabase availability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The diagnostic process is segmented into discrete, selectable checks that can be executed independently based on specific symptoms. Rather than running a comprehensive suite of all possible checks regardless of the situation, the system divides diagnostics into targeted segments that address only the relevant symptoms, improving accuracy while reducing unnecessary resource consumption and downtime.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies partial action by executing only the subset of diagnostic checks relevant to the reported symptoms rather than performing exhaustive troubleshooting on all possible error types. This selective approach maintains high detection accuracy for the specific problem at hand while minimizing resource consumption and database downtime.

Inventive Principle:
Principle #16Partial or excessive action

3Speed

If automated diagnostic checks are implemented, then troubleshooting speed increases, but system complexity increases

Engineering Contradiction:
Improvediagnosis speedVSAvoiddiagnostic system complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The diagnostic system is designed with multi-functionality to handle various database error types through a unified interface. The same check generation and execution mechanism works across different symptom types and error categories, reducing the need for multiple specialized troubleshooting systems while maintaining high diagnostic speed through standardized automated processes.

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

Data Source

PatentUS10545813B2Database diagnostic engine
Publication Date: 2020.01.28 SAP SE
  • US10545813B2 patent drawing
  • US10545813B2 patent drawing
  • US10545813B2 patent drawing

AI summary

A method for performing database diagnostics may include generating, by a database diagnostic engine, a user interface for displaying, at a client, a first selection of symptoms. The database diagnostic engine may receive, from the client and via the user interface, a first input indicating that a first symptom from the first selection of symptoms is present at a database coupled with the client. The database diagnostic engine may respond to the first input by updating the user interface to enable an entry of a second input with respect to the first symptom. The second input may be received from the client via the updated user interface. The database diagnostic engine may perform, based on the first input and/or the second input, checks to detect at least one error at the database. Related systems and articles of manufacture are also provided.