Patent application number | Description | Published |
20090063897 | METHOD OF INCREASING SYSTEM AVAILABILITY BY ASSIGNING PROCESS PAIRS TO PROCESSOR PAIRS - A method is provided of assigning processors in a multiprocessor environment to a plurality of processes that are executed in the multiprocessor environment. Each process has a process pair defined by a primary process that executes on a first processor, and a backup process that executes on a second processor. There are a plurality of process pairs. The processors are in communication with one another via a communication network. The processors are associated with a plurality of predefined processor pairs. First, a plurality of process pairs are provided that are initially assigned to a respective plurality of pairs of processors, wherein at least one of the processors in the plurality of pairs of processors is initially assigned to more than one processor pair. Each processor is then assigned to only one of the predefined processor pairs so that no processor belongs to more than one processor pair. Then, each of the plurality of process pairs are assigned to a respective one of the predefined processor pairs. This assigning process results in a configuration that reduces the number of failure modes from the number of failure modes that exists in the initial configuration. | 03-05-2009 |
20090265352 | METHODS FOR ENSURING FAIR ACCESS TO INFORMATION - Locks placed on corresponding objects held in a plurality of databases located at different nodes in a network during replication are released in accordance with fairness criteria. Propagation delays are determined between a transaction initiating node and one or more other nodes in the network. An object is locked during a transaction being executed at the transaction initiating node. Corresponding objects are locked at one or more other nodes in the network that are manipulated as a result of the replication Upon determining that the object locks should be released, the propagation delays are used to determine when to release the object locks so that all of the object locks at the one or more other nodes are released in accordance with the fairness criteria. | 10-22-2009 |
20100114841 | Referential Integrity, Consistency, and Completeness Loading of Databases - A method is provided for loading data from a source database to a target database that includes at least one table. Prior to loading the data from the source database into the target database, at least one referential integrity constraint and/or at least one consistency requirement regarding the data is automatically identified. A subset of the data that satisfies the at least one referential integrity constraint and/or consistency requirement is then automatically identified. The identified subset of the data is then loaded into the target database as a unit of work. | 05-06-2010 |
20100191884 | METHOD FOR REPLICATING LOCKS IN A DATA REPLICATION ENGINE - An automated method is provided of replicating a locking protocol in a database environment for performing I/O operations wherein the database environment includes a plurality of databases. A locking protocol is performed that includes one or more explicit locking operations on objects in a first database of the database environment. The one or more explicit locking operations are replicated in one or more other databases in the database environment. At least some of the explicit locking operations are performed asynchronously with respect to the explicit locking operations performed in the first database. I/O operations are performed at the first database of the database environment that are associated with the one or more explicit locking operations implemented in the first database. | 07-29-2010 |
20100332448 | METHOD FOR ENSURING REFERENTIAL INTEGRITY IN REPLICATION ENGINES BY RESOLVING LOCK CONFLICTS - A method is provided for processing base level data of a change queue that is not serialized at the logical level. The base level change queue data is transaction data previously posted to a source database. A logical replication engine is provided to replicate and post the change queue data to a target database in the order that the transaction data is stored in the change queue. Upon detection in the logical replication engine of change queue data that is not serialized at the logical level, the change queue data is reserialized at the logical level before the logical replication engine applies the change queue data to the target database. The change queue data that is not serialized at the logical level may be posted to the target database using asynchronous database access. | 12-30-2010 |
20100332449 | METHOD FOR ENSURING REPLICATION WHEN SYSTEM RESOURCES ARE LIMITED - A method is provided for replicating transaction data from a source database to a target database wherein the transaction data is communicated from a change queue associated with the source database to the target database. An initial path is provided between the change queue and the target database for transaction data to flow. The initial path has a maximum transaction load capacity. It is then detected whether the current transaction load is close or equal to the maximum transaction load capacity of the initial path. If so, another path is provided between the change queue and the target database. Also, a method is provided of replicating transaction data from a source database to a target database wherein an associated with the target database has a maximum transaction threshold limit. The applier normally posts transaction data to the target database only upon receipt of a commit step or operation associated with respective transaction data. First, it is detected as to whether the maximum transaction threshold limit of the applier has been reached. If so, a commit step or operation is prematurely conducted on at least some of the transaction data in the applier, thereby causing the transaction data to become posted to the target database and deleted from the applier. | 12-30-2010 |
20120101990 | METHOD FOR ENSURING REPLICATION FROM A CHANGE QUEUE OF A SOURCE DATABASE TO A TARGET DATABASE WHEN TRANSACTION LOAD EXCEEDS DATA PATH BY SPAWNING A NEW TRANSACTION PATH BETWEEN THE CHANGE QUEUE AND THE TARGET DATABASE - A method is provided for replicating transaction data from a source database to a target database wherein the transaction data is communicated from a change queue associated with the source database to the target database. An initial path is provided between the change queue and the target database for transaction data to flow. The initial path has a maximum transaction load capacity. It is then detected whether the current transaction load is close or equal to the maximum transaction load capacity of the initial path. If so, another path is provided between the change queue and the target database. | 04-26-2012 |
20120290548 | Method and article of manufacture for ensuring fair access to information using a fair propagation delay period in a transaction ownership step - A method of performing transactions in accordance with fairness criteria is provided wherein one of a plurality of entities initiates a transaction on an object at a database. The steps or operations of the initiated transaction are immediately processed up to the transaction ownership step. Propagation delays are determined between the database and at least some of the other entities that are capable of initiating transactions to the database. The propagation delays and a fairness criteria is used to determine the fair propagation delay period. Upon determining that the fair propagation delay period has been exceeded, it is detecting whether any of the other entities initiated a transaction on the same object during the fair propagation delay time period. If not, then the transaction initiating entity performs the transaction ownership step on the initiated transaction. | 11-15-2012 |
20120296868 | Method and article of manufacture for ensuring fair access to information using propagation delays to determine when to release object locks - Locks placed on corresponding objects held in a plurality of databases located at different nodes in a network during replication are released in accordance with fairness criteria. Propagation delays are determined between a transaction initiating node and one or more other nodes in the network. An object is locked during a transaction being executed at the transaction initiating node. Corresponding objects are locked at one or more other nodes in the network that are manipulated as a result of the replication Upon determining that the object locks should be released, the propagation delays are used to determine when to release the object locks so that all of the object locks at the one or more other nodes are released in accordance with the fairness criteria. | 11-22-2012 |
20140214669 | Methods for Reducing the Merchant Chargeback Notification Time - A method is provided of alerting a merchant after completion of a transaction that the payment instrument used for the transaction has been identified as being suspect. A reporting processor receives payment instrument indicia regarding payment instruments which have been used for completion of transactions by the merchant, and payment instrument indicia regarding payment instruments which have been identified as being suspect. The reporting processor compares the payment instrument indicia which have been used for completion of transactions by the merchant with the payment instrument indicia which have been identified as being suspect to identify matching payment instrument indicia. The matching payment instrument indicia is associated with suspect payment instrument indicia used by the merchant for completion of the transaction. An electronic communication is provided to the merchant regarding any identified suspect payment instrument indicia. In this manner, the merchant can automatically suspend delivery of a good or service associated with the transaction if payment is suspect. | 07-31-2014 |