|Oracle9i SQL Reference
Release 1 (9.0.1)
Part Number A90125-01
ALTER TRIGGER to constraint_clause, 11 of 12
COMMIT statement to end your current transaction and make permanent all changes performed in the transaction. A transaction is a sequence of SQL statements that Oracle treats as a single unit. This statement also erases all savepoints in the transaction and releases the transaction's locks.
You can also use this statement to
Oracle Corporation recommends that you explicitly end every transaction in your application programs with a
ROLLBACK statement, including the last transaction, before disconnecting from Oracle. If you do not explicitly commit the transaction and the program terminates abnormally, the last uncommitted transaction is automatically rolled back.
A normal exit from most Oracle utilities and tools causes the current transaction to be committed. A normal exit from an Oracle precompiler program does not commit the transaction and relies on Oracle to roll back the current transaction.
You need no privileges to commit your current transaction.
To manually commit a distributed in-doubt transaction that you originally committed, you must have
TRANSACTION system privilege. To manually commit a distributed in-doubt transaction that was originally committed by another user, you must have
TRANSACTION system privilege.
WORK keyword is supported for compliance with standard SQL. The statements
WORK are equivalent.
Specify a comment to be associated with the current transaction. The '
text' is a quoted literal of up to 255 bytes that Oracle stores in the data dictionary view
DBA_2PC_PENDING along with the transaction ID if the transaction becomes in doubt.
COMMENT for more information on adding comments to SQL statements
In a distributed database system, the
FORCE clause lets you manually commit an in-doubt distributed transaction. The transaction is identified by the '
text' containing its local or global transaction ID. To find the IDs of such transactions, query the data dictionary view
DBA_2PC_PENDING. You can use
integer to specifically assign the transaction a system change number (SCN). If you omit
integer, the transaction is committed using the current SCN.
COMMIT statements using the
FORCE clause are not supported in PL/SQL.
Oracle9i Distributed Database Systems for more information on these topics
This statement inserts a row into the
hr.regions table and commits this change:
The following statement commits the current transaction and associates a comment with it:
If a network or machine failure prevents this distributed transaction from committing properly, Oracle stores the comment in the data dictionary along with the transaction ID. The comment indicates the part of the application in which the failure occurred and provides information for contacting the administrator of the database where the transaction was committed.
The following statement manually commits an in-doubt distributed transaction: