Operation analytic repository central monitoring system

• US 10,282,441 B2
• Filed: 01/01/2015
• Issued: 05/07/2019
• Est. Priority Date: 01/01/2015
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Tilekar, Ulhas Shashikant
• Primary Examiner(s): Thomas, Ashish
• Assistant Examiner(s): Eyers, Dustin D
• Application Number:
  US14/588,426
• Publication Number:
  US 20160196294A1
• Time in Patent Office: 1,587 Days
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management

Abstract

Embodiments of the invention are directed to systems, methods and computer program products for use in financial systems, where messages are automatically generated based on message templates. An exemplary apparatus is configured to access one or more databases within an operation analytic repository having data stored therein; store in the at least one database, for a predetermined time period, for analysis; process, for at least one of the databases, a proactive action whereby the proactive action implements an ongoing health assessment of the data stored within the at least one database; and in response to receiving indication of an issue within at least one of databases, provide a reactive action whereby the reactive action determines one or more steps necessary to correct the issue.

Claims

1. An apparatus for use in operation analytic repository database monitoring, whereby the apparatus automatically and continuously monitors and provides corrective actions for detected issues, the apparatus comprising:

an electronic storage device;

a computing processor; and

a module stored in the electronic storage device, said module comprising instruction code executable by one or more computing processors, and configured to cause the one or more computing processors to;

continuously access one or more operational databases;

continuously copy data from the one or more operational databases and store the copied data in a separate database, for a predetermined time period;

receive a threshold value for determining whether or not a potential issue exists, wherein a value above the threshold value indicates that the potential issue exists, and wherein a value below the threshold value indicates that the potential issue does not exist, and wherein the threshold value comprises a metric for determining a database or server environment usage percentage;

process, for the data, a proactive action, wherein processing the proactive action comprises running one or more monitoring scripts on the data;

in response to running the one or more monitoring scripts, determine that the potential issue exists in the data, wherein the potential issue is determined to exist based on the threshold value;

determine a severity of the potential issue;

in response to determining that the severity of the potential issue is below a severity threshold, automatically correct, without manual intervention, the potential issue, and implement an ongoing health assessment of the data to determine if the potential issue persists, and wherein the potential issue is not automatically corrected, without manual intervention, if the severity of the potential issue is above the severity threshold;

in response to determining that the severity of the potential issue is above the severity threshold, apply a second severity threshold to determine whether the potential issue must be escalated to a third party, wherein the potential issue is escalated to a third party if the severity of the potential issue is above the second severity threshold;

provide a central monitoring tool to a user, and wherein the central monitoring tool comprises an interface such that information related to the data is displayed within the central monitoring tool;

fetch data from the separate database for presentation within the central monitoring tool, wherein the fetched data comprises a user roles table and a user grants table related to the one or more operational databases; and

present the fetched data from the separate database via the interface.

2. The apparatus of claim 1, wherein the module is configured to cause one or more computing processors to notify at least one party of the potential issue.

3. The apparatus of claim 1, wherein the module is configured to cause one or more computing processors to:

receive one or more authentication credentials from the user via the interface; and

prior to presenting the fetched data via the interface, authenticate the user'"'"'s identity based at least in part on validating the one or more authentication credentials.

4. The apparatus of claim 3, wherein the module is configured to cause one or more computing processors to:

receive a user-specified script via the interface;

receive one or more additional authentication credentials from the user via the interface;

validate the one or more additional authentication credentials;

in response to validating the one or more additional authentication credentials, launch the user-specified script.

5. The apparatus of claim 1, wherein the module is configured to cause one or more computing processors to analyze the data on periodic, semi-periodic, or continuous basis.

6. The apparatus of claim 5, wherein analyzing the data comprises:

monitoring the data;

identifying one or more parameters for improvement within the data;

determining whether or not the one or more parameters for improvement within the data are necessary; and

in response to determining the one or more parameters for improvement within the data are necessary, implementing at least one action to improve the data.

7. The apparatus of claim 1, wherein the module is configured to cause one or more computing processors to maintain a record log of indications of an issue within the one or more operational databases.

8. The apparatus of claim 1, wherein the module is configured to cause one or more computing processors to:

identify and analyze a second potential issue in the data; and

determine, based on results of the analysis, whether or not the second potential issue can be resolved by the apparatus.

9. The apparatus of claim 8, wherein the module is configured to cause one or more computing processors to in response to determining the second potential issue can be resolved by the apparatus, implementing one or more steps for resolving the second potential issue.

10. The apparatus of claim 8, wherein the module is configured to cause one or more computing processors to in response to determining the second potential issue cannot be resolved by the apparatus, determining to automatically escalate the second potential issue to a third party system or entity for resolution.

11. The apparatus of claim 1, wherein the potential issue comprises a first database of the one or more operational databases utilizing a maximum memory capacity.

12. The apparatus of claim 11, wherein automatically correcting the potential issue comprises allocating storage from a second database to the first database based on determining that the second database is less active than the first database.

13. The apparatus of claim 1, wherein the interface of the central monitoring tool is configured to receive the threshold value from the user.

14. A computer implemented method for use in operation analytic repository database monitoring, whereby the method comprises automatically monitoring and providing corrective actions for detected issues, the method comprising:

accessing one or more operational databases;

copying data from the one or more operational databases and storing the copied data in a separate database, for a predetermined time period;

receiving a threshold value for determining whether or not a potential issue exists, wherein a value above the threshold value indicates that the potential issue exists, and wherein a value below the threshold value indicates that the potential issue does not exist, and wherein the threshold value comprises a metric for determining a database or server environment usage percentage;

processing, for the data, a proactive action, wherein processing the proactive action comprises running one or more monitoring scripts on the data;

in response to running the one or more monitoring scripts, determining that the potential issue exists in the data, wherein the potential issue is determined to exist based on the threshold value;

determining a severity of the potential issue;

in response to determining that the severity of the potential issue is below a severity threshold, automatically correcting, without manual intervention, the potential issue, and implement an ongoing health assessment of the data to determine if the potential issue persists, and wherein the potential issue is not automatically corrected, without manual intervention, if the severity of the potential issue is above the severity threshold;

in response to determining that the severity of the potential issue is above the severity threshold, apply a second severity threshold to determine whether the potential issue must be escalated to a third party, wherein the potential issue is escalated to a third party if the severity of the potential issue is above the second severity threshold;

providing a central monitoring tool to a user, and wherein the central monitoring tool comprises an interface such that information related to the is displayed within the central monitoring tool;

fetching data from the separate database for presentation within the central monitoring tool, wherein the fetched data comprises a user roles table and a user grants table related to the one or more operational databases; and

presenting the fetched data from the separate database via the interface.

15. The method of claim 14 further comprising:

identify and analyze a second potential issue in the data; and

determining, based on results of the analysis, whether or not the second potential issue can be resolved.

16. A computer program product for use in operation analytic repository database monitoring, whereby the computer program product automatically monitors and provides corrective actions for detected issues, the computer program product comprising:

a non-transitory computer-readable medium comprising a set of codes for causing a computer to;

access one or more operational databases;

copy data from the one or more operational databases and store the copied data in a separate database, for a predetermined time period;

receive a threshold value for determining whether or not a potential issue exists, wherein a value above the threshold value indicates that the potential issue exists, and wherein a value below the threshold value indicates that the potential issue does not exist, and wherein the threshold value comprises a metric for determining a database or server environment usage percentage;

process, for the data, a proactive action, wherein processing the proactive action comprises running one or more monitoring scripts on the data;

in response to running the one or more monitoring scripts, determine that the potential issue exists in the data, wherein the potential issue is determined to exist based on the threshold value;

determine a severity of the potential issue;

in response to determining that the severity of the potential issue is below a severity threshold, automatically correct, without manual intervention, the potential issue, and implement an ongoing health assessment of the data to determine if the potential issue persists, and wherein the potential issue is not automatically corrected, without manual intervention, if the severity of the potential issue is above the severity threshold;

in response to determining that the severity of the potential issue is above the severity threshold, apply a second severity threshold to determine whether the potential issue must be escalated to a third party, wherein the potential issue is escalated to a third party if the severity of the potential issue is above the second severity threshold;

provide a central monitoring tool to a user, and wherein the central monitoring tool comprises an interface such that information related to the is displayed within the central monitoring tool;

fetch data from the separate database for presentation within the central monitoring tool, wherein the fetched data comprises a user roles table and a user grants table related to the one or more operational databases; and

present the fetched data from the separate database via the interface.

17. The computer program product of claim 16, the computer program product further comprising a set of codes for causing a computer to:

identify and analyze a second potential issue in the data; and

determine, based on results of the analysis, whether or not the second potential issue can be resolved.