Flashback Database [message #618936] |
Wed, 16 July 2014 11:07 |
|
jerstep
Messages: 1 Registered: July 2014
|
Junior Member |
|
|
Is it common to use Oracle Flashback Database to rollback code releases (DDL, DML) to Development and/or Production environments instead of writing rollback scripts ? What are the pros/cons of such an approach?
|
|
|
|
|
|
|
|
|
Re: Flashback Database [message #618997 is a reply to message #618993] |
Thu, 17 July 2014 04:15 |
gazzag
Messages: 1119 Registered: November 2010 Location: Bedwas, UK
|
Senior Member |
|
|
Why don't you go and clarify your first post in this thread instead of tearing mine to pieces? No wonder your post count is so high <_<
|
|
|
|
Re: Flashback Database [message #619001 is a reply to message #618989] |
Thu, 17 July 2014 04:46 |
John Watson
Messages: 8964 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
gazzag wrote on Thu, 17 July 2014 09:32Like everything, the answer is "it depends"
I don't use Flashback on production as there is an obvious overhead - flashback logs have to be written, for example. Also, to flashback a database means that all work done on that database will be rolled back which will probably not be acceptable for your users.
Generally, I use Flashback on test or UAT systems. This means that the database can be returned to a known state at any point during the testing phase.
HTH
-g Exactly my usual working practice. That having been said, I suspect that the overhead of flashback is not significant. Theoretically, one can calculate it. v$flashback_database_stat shows the volumes of data written to data files, online redo logs, and flashback logs. So one should be able work out what proportion of your I/O capacity is taken by flashback. But I am not confident in my ability to generate meaningful data from this.
|
|
|
Re: Flashback Database [message #619013 is a reply to message #619001] |
Thu, 17 July 2014 05:30 |
gazzag
Messages: 1119 Registered: November 2010 Location: Bedwas, UK
|
Senior Member |
|
|
I've had problems persuading management to invest in the additional disk space that they perceive as "unnecessary", John
|
|
|