ORA-08177: can't serialize access for this transaction
A SERIALIZABLE transaction tried to change a row that another transaction changed and committed after this one began. Roll back and retry.
- Error code
ORA-08177- Category
- Transactions and locking
What it means
In SERIALIZABLE isolation, a transaction sees the database as of its start. If it tries to update or delete a row that another transaction modified and committed after that point, Oracle can't make the result look serial and raises ORA-08177. The transaction should be rolled back and run again.
Common causes
- Concurrent updates to the same rows under
ISOLATION LEVEL SERIALIZABLE. - Long serializable transactions on busy tables.
How to fix it
-
Roll back and retry the transaction in the application.
ROLLBACK;
-
Use the default
READ COMMITTEDisolation unless the transaction really needs serializable behavior, and keep serializable transactions short.SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
Related errors
ORA-00060deadlock detected while waiting for resource40001PostgreSQL: could not serialize access3960SQL Server: Snapshot isolation update conflictSQLITE_BUSY_SNAPSHOTSQLite: stale read can't become a write
More transactions and locking errors
The code and message text are from the Oracle Database Error Help. Browse the full Oracle error list or search every database error.
Work on Oracle in SQLly
A native SQL client for macOS, Windows and Linux with schema-aware IntelliSense, guardrails for risky statements and clear error messages, for Oracle and the other databases you use.