Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there any conceptual difference between a SERIALIZABLE Transaction and a Flashback Query?

share|improve this question
up vote 6 down vote accepted

They are completely unrelated concepts.

  • Serializable is a type of isolation level (read here for more info)
  • Flashback Query is an Oracle technology for getting querying data as it was at a certain point in time - for example, if certain conditions are met you can use Flashback Query to get those million rows back after committing that transaction that accidentally deleted them.
share|improve this answer
"querying data as it was at a certain point in time" ... and with an isolation level of serializable I'm seeing the data as it was at the beginning of my transaction, regardless of any commits in other session, right? That's why I thought they are conceptually related ... – Martin May 15 '11 at 15:06
I see your point - they are similar in that sense, but used for very different purposes, serializable to "give each serializable transaction a "frozen" picture of the database at the point in time the transaction began" and flashback typically to save your blushes when something has gone awry – Jack Douglas May 16 '11 at 20:29

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.