Skip to Main Content
  • Questions
  • Transaction Isolation level - Serialization

Breadcrumb

May 4th

Question and Answer

Chris Saxon

Thanks for the question, Prateek.

Asked: August 23, 2016 - 3:18 pm UTC

Last updated: June 14, 2019 - 4:14 pm UTC

Version: 11g RAC

Viewed 1000+ times

You Asked

Hi,

I know its not recommended to use transaction isolation level as Serialization but for now we have to stick with it. Please pardon my knowledge as I'm new to this.

I currently use Sybase ASA (SQLAnywhere) where we have the isolation level as snapshot which means every transaction has its own snapshot of the DB which ensures the data doesnt change while performing long running transactions (transaction A) and in-case other transaction (transaction B) changes the data used by Transaction A it throws an error.

On oracle, the closest thing I found to this is Serialization. When I set the transaction level isolation to serialization, I keep getting - ORA-08177: can't serialize access for this transaction. The tables involved in two transactions are the same but the rows are totally independent.

Can you please help me understand the cause of this? Or how can I troubleshoot it?

Thanks
- Prateek

and Connor said...

Here's a detailed article on its usage in Oracle

https://blogs.oracle.com/oraclemagazine/on-transaction-isolation-levels

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

There is a dead link

Ryan Burgess, June 14, 2019 - 3:02 pm UTC

Dead link
Chris Saxon
June 14, 2019 - 4:14 pm UTC

Thanks, I've updated the link.

More to Explore

SQL

The Oracle documentation contains a complete SQL reference.