two-phase commit

(redirected from 2-phase commit)
Also found in: Wikipedia.

two-phase commit

(database)
A technique for maintaining integrity in distributed databases. Where a system uses two or more database, a transaction among the distibuted database should be atomic ("all or nothing"). This is done by handling the transaction in two phases. First the databases prepare the transaction, confirm that it is possible to process it, and lock the relevant record.

Once all the required databases confirm that the transaction is viable, the system instructs them all to commit it - i.e. to make it permanent. If it is not possible to process it, the system will instruct the databases to rollback (undo) the transaction.

two-phase commit

A technique for ensuring that a transaction successfully updates all appropriate files in a distributed database environment. All DBMSs involved in the transaction first confirm that the transaction has been received and is recoverable (stored on disk). Then each DBMS is told to commit the transaction (do the actual updating).

Traditionally, two-phase-commit meant updating databases in two or more servers, but the term is also applied to updating two or more different databases within the same server. See transaction, transaction file and transaction processing.
References in periodicals archive ?
BizFlow Integration Studio provides a development environment for the IT integration specialists involved in process improvement projects; enables the rapid development and orchestration of services-oriented transactions, with advanced features such as 2-phase commit with rollback, exception handling, visual point and click data transformation services, embedded testing and debugging tools, UDDI, and more.
When WebSphere Enterprise Edition's 2-phase commit features are combined with the host communication capabilities provided by SNAP-IX, these updates can be kept consistent across systems.
It provides full support for Session and Entity Beans, Java Naming and Directory Interface (JDNI), JTA including 2-phase commit, Security Management, RMI over IIOP and XML-based deployment descriptors.
Ejipt's distributed 2-phase commit transaction management allows for robust solutions to complex business demands.
In addition, 46 new resource monitors and 15 new workload monitors are available for claim/drain activity, I/O processing, buffer pool activity, archive log data, hiperpool activity and distributed 2-phase commit.
Support for multiple resource types - OTS, XA, and 1-phase -- 2-phase commits with presumed rollback -- Single resource and last resource optimizations -- Interposition of inherited transactions -- In-process and Out-of-process (for pure clients) -- Support for Oracle and Cloudscape JDBC XA drivers -- Visual monitoring provided by the jBroker Console (see related jBroker announcement issued December 4, 2001)