transactions

Oracle 10.0.1:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: Transactions deadlocked one another while waiting for resources.

Action: Look at the trace file to see the transactions and resources involved. Retry if necessary.

ORA-00099: timed out while waiting for resource, potential PDML deadlock

Cause: The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system.

Action: Increase the the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then retry the operation.

ORA-00155: cannot perform work outside of global transaction

Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.

Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work. //

ORA-01545: rollback segment '%s' specified not available

Cause: Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file.

Action: Either: 1) Make the rollback segment available; for example, bring an offline tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. 3) Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. 4) Same as 3). 5) Remove the name from the _corrupted_rollback_segments parameter.

ORA-01554: out of transaction slots in transaction tables

Cause: Too many concurrent transactions

Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again

ORA-01574: maximum number of concurrent transactions exceeded

Cause: the limit on the number of concurrent transactions has been hit

Action: shutdown the system, increase the INIT.ORA parameter 'transactions' , and then restart the system.

ORA-01626: rollback segment number '%s' cannot handle more transactions

Cause: Too many transactions in this segment.

Action: Choose a different rollback segment, or reduce the number of concurrent transactions.

ORA-01640: cannot make tablespace read only with active transactions

Cause: Attempting to make a tablespace read only while there are active transactions in the database. All transactions must commit or rollback to insure that there is no undo for a tablespace before it can be made read only. This includes in doubt distributed transactions.

Action: Prevent any more transactions from being started. Putting the database in restricted mode usually helps. If there are any in doubt transactions they must also be resolved.

ORA-02042: too many distributed transactions

Cause: the distributed transaction table was full because too many distributed transactions were active.

Action: Run fewer transactions. If you are sure you don't have too many concurrent distributed transactions, this indicates an internal error and support should be notified. Instance shutdown/restart would be a work-around.

ORA-02088: distributed database option not installed

Cause: the distributed transaction table was full because too many distributed transactions were active.

Action: Run fewer transactions. If you are sure you don't have too many concurrent distributed transactions, this indicates an internal error and support should be notified. Instance shutdown/restart would be a work-around.

ORA-06519: active autonomous transaction detected and rolled back

Cause: Before returning from an autonomous PL/SQL block, all autonomous transactions started within the block must be completed (either committed or rolled back). If not, the active autonomous transaction is implicitly rolled back and this error is raised.

Action: Ensure that before returning from an autonomous PL/SQL block, any active autonomous transactions are explicitly committed or rolled back. //----------------------------------------------------------------------- // 06520 through 06529 reserved for Foreign function errors // //

ORA-08176: consistent read failure; rollback data not available

Cause: Encountered data changed by an operation that does not generate rollback data : create index, direct load or discrete transaction.

Action: In read/write transactions, retry the intended operation. Read only transactions must be restarted.

ORA-12062: transaction %s received out of sequence from site %s

Cause: A transaction from the client site was received out of sequence. This implies that one or more transactions were missing.

Action: Ensure that the transaction queue at the client site is valid and has not been corrupted. //

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ transactions ] on the Oracle FAQ.