Maintaining consistent state information among multiple active database systems

• US 20070174349A1
• Filed: 03/16/2007
• Published: 07/26/2007
• Est. Priority Date: 12/30/2004
• Status: Abandoned Application

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: NCR Corporation (NCR Voyix Corporation)
• Inventors: Mitchell, Mark, Fastner, Thomas
• Application Number:
  US11/638,643
• Publication Number:
  US 20070174349A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A system-management tool is used in managing at least two copies of a relational database that are stored in at least two database systems. The tool includes (a) a monitoring component configured to monitor for the occurrence of an event within one of the database systems that creates a change in an operational status of that database system, and (b) a synchronization component configured to update state information stored in another of the database systems to reflect the change in operational status of the one database system.

Claims

1. A system-management tool for use in managing at least two copies of at least a portion of a relational database that are stored in at least two database systems, the tool comprising:

a monitoring component configured to monitor for the occurrence of an event within one of the database systems that creates a change in an operational status of that database system; and

a synchronization component configured to update state information stored in another of the database systems to reflect the change in operational status of the one database system.

2. The system-management tool of claim 1, where the synchronization component, to update the state information, is configured to update one or more relational tables in each of the database systems.

3. The system-management tool of claim 2, where the synchronization component, to update the information stored in one or more tables, is configured to update one or more event tables configured to store information about one or more events occurring within at least one of the database systems.

4. The system-management tool of claim 2, where the synchronization component, to update the information stored in one or more tables, is configured to update one or more application-state tables configured to store information about one or more application processes supported by at least one of the database systems.

5. The system-management tool of claim 2, where updating state information leads to an update of information about one or more application resources required for support of one or more applications.

6. The system of claim 5, where the resources include one or more of the following:

a process, data or a component.

7. A system-management tool for use in managing at least two copies of a relational database in at least two database systems, the tool comprising:

one or more relational tables in each of the database systems configured to store information indicating an operational status of each of the database systems; and

a synchronization component configured to replicate a change made to the one or more tables in one of the database systems within another of the database systems.

8. The system-management tool of claim 7, where the information stored in the one or more relational tables includes information about one or more critical events occurring within at least one of the database systems.

9. The system-management tool of claim 8, where the information about the one or more critical events includes information about an event that makes at least one of the database systems unavailable to process database queries.

10. The system-management tool of claim 7, where the information stored in the one or more relational tables includes information about one or more application processes supported by at least one of the database systems.

11. The system-management tool of claim 10, where the information stored in the one or more relational tables includes information about database system resources required to support the one or more application processes.

12. A method for use in managing at least two copies of a relational database that are stored in at least two database systems, the method comprising:

monitoring for the occurrence of an event within one of the database systems that creates a change in an operational status of that database system; and

updating state information stored in another of the database systems to reflect the change in operational status of the one database system.

13. The method of claim 12, where updating the state information includes updating one or more relational tables in each of the database systems.

14. The method of claim 13, where updating the information stored in one or more relational tables includes updating one or more event tables configured to store information about one or more events occurring within at least one of the database systems.

15. The method of claim 13, where updating the information stored in one or more relational tables includes updating one or more application-state tables configured to store information about one or more application processes supported by at least one of the database systems.

16. The method of claim 15, where updating the one or more application tables leads to updating information about resources required for support of one or more applications.

17. The method of claim 16, where updating information about resources includes updating information about one or more of the following:

a process, data or a component.

18. A method for use in managing at least two copies of a relational database in at least two database systems, the method comprising:

storing in one or more relational tables in each of the database systems information indicating an operational status of each of the database systems; and

replicating a change made to the one or more tables in one of the database systems within another of the database systems.

19. The method of claim 18, where storing information about operational status includes storing information about one or more critical events occurring within at least one of the database systems.

20. The method of claim 19, where storing information about the one or more critical events includes storing information about an event that makes at least one of the database systems unavailable to process database queries.

21. The method of claim 18, where storing information in the one or more tables includes storing information about one or more application processes supported by at least one of the database systems.

22. The method of claim 21, where storing information in the one or more tables includes storing information about database system resources required to support the one or more application processes.