Table of Contents
Advertisement
isolation-level
specifies the level of data consistency defined for the transaction and the degree of
concurrency the transaction has with other transactions that use the same data. The default
isolation level is READ COMMITTED.
access-mode
specifies the type of data access that the transaction requires, depending on whether the
transaction changes the database.
If the isolation-level is READ UNCOMMITTED, you cannot specify READ WRITE.
The default access-mode is READ WRITE.
See
"Transaction Access Modes" (page
autocommit-option
specifies whether Neoview SQL commits or rolls back automatically at the end of statement
execution. This option applies to any statement for which the system initiates a transaction.
If this option is set to ON, Neoview SQL automatically commits any changes or rolls back
any changes made to the database at the end of statement execution. AUTOCOMMIT is
on by default at the start of a session.
If this option is set to OFF, the current transaction remains active until the end of the
session unless you explicitly commit or rollback the transaction. AUTOCOMMIT is a
Neoview SQL extension; you cannot use in it with any other option.
Using the AUTOCOMMIT option in a SET TRANSACTION statement does not reset
other transaction attributes that may have been specified in a previous SET
TRANSACTION statement. Similarly, a SET TRANSACTION statement that does not
specify the AUTOCOMMIT attribute does not reset this attribute.
norollback-option
specifies that a transaction does not rollback if it aborts. All changes made to the database
as part of the failed transaction, up to the point of failure, are persistent.
This option can be set to ON only for INSERT, UPDATE, or DELETE operations on a
table that has no dependent objects such as an index, materialized view or trigger. If this
option is set to ON and an INSERT statement is issued on a table with an index, the
INSERT statement will raise an error and will not insert any rows. Setting this option to
ON can provide a significant benefit in error situations for long running INSERT, UPDATE,
or DELETE statements. For such statements, an error midway through execution will
cause the entire transaction to be backed out, if this option is not enabled. Backing out
data as part of the rollback process can be time and resource consuming. This option has
been provided to avoid expensive backout processes.
autoabort-interval
controls the autoabort feature.
timeout
specifies the transaction is aborted automatically when it reaches the duration
indicated. Timeout can be specified in hours, minutes, and seconds.
The minimum value is 20 seconds. The maximum values are 21474836 seconds, 357913
minutes, or 5965 hours. If the timeout value does not satisfy the conditions, an error
message is generated.
0
Turns off the autoabort function for this transaction, eliminating any time limit.
RESET
Reverts to the segment-wide autoabort interval configured.
31).
SET TRANSACTION Statement
189
Advertisement
Table of Contents
