Project: YugabyteDB (App Definition and Development / Database)
File: transactions-errorcodes-ysql.md

title: Transaction Error Codes in YSQL headerTitle: Transaction error codes in YSQL linkTitle: Error codes description: Understand the error codes returned during transactions. menu: stable: identifier: transaction-errorcodes-ysql parent: acid-transactions-1-ysql weight: 570 type: docs Due to the strong properties guaranteed by YugabyteDB, failures during transactions are inevitable. You need to design your applications to take appropriate action on failed statements to ensure they are highly available. YugabyteDB returns various error codes for errors that occur during transaction processing. The following error codes typically occur during transaction processing. This error occurs when certain statements that should be run outside a transaction block, typically because they have non-rollback-able side effects or do internal commits, are executed inside a transaction block. For example, issuing a `BEGIN` statement inside a transaction. ```output WARNING: 25001: there is already a transaction in progress ``` {{<note>}} 25001 errors are just warnings. But the code needs to be fixed to avoid future warnings. {{</note>}} This error occurs when certain statements are executed in a read-only transaction that violate the read-only constraint. For example, modifying records inside a read-only transaction. ```output ERROR: 25006: cannot execute UPDATE in a read-only transaction ``` {{<note>}} 25006 errors are . Writes should be removed from the read-only transaction code. {{</note>}} This error occurs when certain statements that should be executed in a transaction are executed outside of a transaction. For example, issuing a `ROLLBACK` outside a transaction. ```output WARNING: 25P01: there is no transaction in progress ``` {{<note>}} 25P01 errors are just warnings. But the code needs to be fixed to avoid future warnings. {{</note>}} This error occurs when statements have failed inside a transaction and another statement other than `COMMIT` or `ROLLBACK` is executed. ```output ERROR: 25P02: current transaction is aborted, commands ignored until end of transaction block ``` {{<note>}} 25P02 errors are . Proper error handling via a `try..catch` block and either `COMMIT` or `ROLLBACK` should be executed appropriately. {{</note>}} This occurs when an application stays idle longer than `idleintransactionsessiontimeout` in the middle of a transaction. ```output FATAL: 25P03: terminating connection due to idle-in-transaction timeout ``` {{<note>}} The client can reconnect to the server and retry the transaction. {{</note>}} This error occurs when a transaction cannot be applied or progress further because of other conflicting transactions. For example, when multiple transactions are modifying the same key. ```output ERROR: 40001: Operation expired: Transaction XXXX expired or aborted by a conflict ``` {{<tip>}} Serialization failure errors can be retried by the client. See . {{</tip>}} This error occurs when a transaction is terminated either by a `COMMIT` or a `ROLLBACK` in an invalid location. For example, when a `COMMIT` is issued inside a stored procedure that is called from inside a transaction. ```output ERROR: 2D000: invalid transaction termination ``` {{<note>}} 2D000 errors are . The transaction code needs to be fixed to get around this error. {{</note>}} This error occurs when you try to `ROLLBACK` to or `RELEASE` a savepoint that has not been defined. ```output ERROR: 3B001: savepoint "FIRST_SAVE" does not exist ``` {{<note>}} 3B001 errors are . The transaction code needs to be fixed to specify the correct savepoint name to fix this error. {{</note>}} - Various isolation levels that are supported by YugabyteDB. - Policies to handle conflicts between transactions. - Priority buckets for transactions. - Options supported by transactions.