Method of ensuring availability of event notification registrations of a database management system

• US 7,761,413 B2
• Filed: 06/19/2006
• Issued: 07/20/2010
• Est. Priority Date: 05/10/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Mishra, Shailendra, Surlaker, Kapil
• Primary Examiner(s): Stevens; Robert
• Application Number:
  US11/471,405
• Publication Number:
  US 20070266052A1
• Time in Patent Office: 1,492 Days
• Field of Search: 707/202, 707/200, 707/610, 707/674
• US Class Current: 707/610
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

A method of ensuring availability of event notification registrations of a database management system is described and provided. The method comprises creating the event notification registrations and storing the event notification registrations in a database of the database management system. Further, the event notification registrations are replicated in a designated database management system to create replicated event notification registrations. If the database management system fails, the replicated event notification registrations are utilized.

Claims

1. A method of ensuring availability of event notification registrations of a first database management system, said method comprising:

creating said event notification registrations, each event notification registration specifying an event occurrence in the first database management system for which a client should be notified;

receiving a replication preference for each event notification registration, said replication preference indicating whether to replicate a respective event notification registration;

storing said event notification registrations in a database of said first database management system;

based on said replication preference, replicating said event notification registrations in a designated second database management system to create replicated event notification registrations; and

subsequent to a failure of the first database management system, notifying the client of the occurrence of events in the second database management system that match events specified by the replicated event notification registrations.

2. The method as recited in claim 1 wherein said replicating comprises:

replicating additions to said event notification registrations;

replicating deletions to said event notification registrations; and

replicating modifications to said event notification registrations.

3. The method as recited in claim 1 wherein said first database management system and said designated second database management system are in a common cluster.

4. The method as recited in claim 1 wherein said first database management system and said designated second database management system are in different clusters.

5. The method as recited in claim 1, wherein said replication preference indicates a preference of the client that the event notification registration should be available if the first database management system fails.

6. A computer-readable medium comprising computer-executable instructions stored therein for performing a method of ensuring availability of event notification registrations of a first database management system, said method comprising:

creating said event notification registrations, each event notification registration specifying an event occurrence in the first database management system for which a client should be notified;

receiving a replication preference for each event notification registration, said replication preference indicating whether to replicate a respective event notification registration;

storing said event notification registrations in a database of said first database management system;

based on said replication preference, replicating said event notification registrations in a designated second database management system to create replicated event notification registrations; and

subsequent to a failure of the first database management system, notifying the client of the occurrence of events in the second database management system that match events specified by the replicated event notification registrations.

7. The computer-readable medium as recited in claim 6 wherein said replicating comprises:

replicating additions to said event notification registrations;

replicating deletions to said event notification registrations; and

replicating modifications to said event notification registrations.

8. The computer-readable medium as recited in claim 6 wherein said first database management system and said designated second database management system are in a common cluster.

9. The computer-readable medium as recited in claim 6 wherein said first database management system and said designated second database management system are in different clusters.

10. The computer-readable medium as recited in claim 6, wherein said replication preference indicates a preference of the client that the event notification registration should be available if the first database management system fails.

11. An apparatus comprising:

a memory comprising instructions stored therein; and

a processor for executing said instructions to perform a method of ensuring availability of event notification registrations of a first database management system, comprising;

creating said event notification registrations, each event notification registration specifying an event occurrence in the first database management system for which a client should be notified;

receiving a replication preference for each event notification registration, said replication preference indicating whether to replicate a respective event notification registration;

storing said event notification registrations in a database of said first database management system;

based on said replication preference, replicating said event notification registrations in a designated second database management system to create replicated event notification registrations; and

subsequent to a failure of the first database management system, notifying the client of the occurrence of events in the second database management system that match events specified by the replicated event notification registrations.

12. The apparatus as recited in claim 11 wherein said replicating comprises:

replicating additions to said event notification registrations;

replicating deletions to said event notification registrations; and

replicating modifications to said event notification registrations.

13. The apparatus as recited in claim 11 wherein said first database management system and said designated second database management system are in a common cluster.

14. The apparatus as recited in claim 11 wherein said first database management system and said designated second database management system are in a common cluster.

15. The apparatus as recited in claim 11, wherein said replication preference indicates a preference of the client that the event notification registration should be available if the first database management system fails.