Method relating to databases
AssigneeTelefonaktiebolaget LM Ericsson (publ)
InventorUlf Mikael Ronström
Life of this patent
Estimating the term…
Loading patent…
AssigneeTelefonaktiebolaget LM Ericsson (publ)
InventorUlf Mikael Ronström
Estimating the term…
The present invention relates to a method of handling the risk of a deadlock between simultaneous transactions T1, T2 in a database 1. The method is based on allocating to respective objects 01, 02 in the database 1 a lockout queue L1, L2 in which transactions T1, T2, T3, . . . , T8 that request access to an object 01, 02 are placed to await the access to said object of a preceding transaction. The handling procedure comprises going through, or perusing, the lockout queues L1 belonging to different objects 01 to detect so-called locking transactions T1 that can cause a deadlock and, subsequent to detection, comparing said locking transaction with other transactions T2, T6, T1. T7, T8 in other lockout queues L2 therewith enabling the risk of deadlock between a first and a second transaction T1, T2 that have both requested access to the same first and second object 01, 02 to be detected. Combinations of transactions that are ongoing or active in the database and that, according to said comparison, can cause a deadlock are divided into locking and non-locking combinations respectively. Solely the detection of a locking combination will cause further action to be taken.
A method of handling the risk of a deadlock between simultaneous transactions in a database, in which respective objects in said database are allocated at least one lockout queue in which transactions that have requested access to an object are placed and there await the access of a preceding transaction to said object, and in which said handling procedure includes perusing the transactions present in said lockout queues, comprising the steps of providing that a transaction active or ongoing in said database can be categorised as a locking transaction, that a locking transaction can cause a deadlock in combination with one or more other transactions, that combinations of a locking transaction and one or more other transactions are categorised as locking combinations and non-locking combinations respectively, that a non-locking combination never results in a deadlock, that a locking combination can result in a deadlock, that the detection of a locking transaction results in a further perusal of said locking queues, that in said further perusal said locking transaction is compared with transactions that are affiliated to said lockout queues in order to establish whether or not said combination of transactions constitutes a locking or a non-locking combination, and in that solely the detection of a locking combination results in further action.
Dependencies are inferred from the claim text.