Re: Bad Field Update

DBMS_FLASHBACK is a great option if you database is set up to use it and your data is still accessible in the UNDO segments. Point in time recovery will work, but you'll lose transactions after that point in time.

Another option is to mine your archived redo logs for the SQL_UNDO statements to undo your transaction. This assumes that you are in archive log mode.

HTH,
Brian

Tanel Poder wrote:
>
> Hi!
>
> Is it too late to rollback?
>
> On which version are you? If on 9i, you might be able to use dbms_flashback
> package to see old state of your table, then copy the contents, drop
> original table and rename the copy back to original name (variations could
> be used if don't want to drop because of constraints & dependencies).
>
> Otherwise you could do point in time recovery if you got a backup and
> logfiles from start of this backup until to point before you started your
> update (or before commiting this update works as well).
>
> Tanel.
>
> "MikeP" <nhojnacki_at_cox.net> wrote in message
> news:df791f74.0308100630.1596064b_at_posting.google.com...
> > I intended to update certain rows in one table, instead I updated them
> > all. What is the best way to recover the previous data in this one
> > field, Or do I need to run a script that populates the field from
> > another table. There is a table that does contain the correct data,
> > but it is a one to many relationship ( the bad data has one value but
> > the other has mulitple values for the same record ) and I'm not sure
> > how this can be handled.
> >
> > regards
> >
> > -Mike

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"