Is there anything bad about enabling row movement on ALL tables in a schema
cayenneApr 17 2009 — edited Apr 17 2009Hi all,
I'm starting to play around with flashback, and I found that in the literature, that if you want to be able to flashback a table, you need to do an alter table enable row movement BEFORE you can do a flashback table 'query'.
It seems you need to know which tables in advance you might need flashback on....since you can't flashback, it appears , to a time before you enabled row movement.
So, I'm wondering, is there any penalty for writing a little script to enable row movenemt on ALL tables in a schema? Is there a performance hit if you do this on transactions, etc?
Thanks in advance,
cayenne