Re: to anyone who has used log miner

I didn't have the SCN, I only had the approximate time. And in this particular case, there were no other delete operations on that table. So finding the UNDO was pretty easy.

Cheers,
Brian

Ryan Gaffuri wrote:
>
> Brian Peasland <dba_at_remove_spam.peasland.com> wrote in message news:<3F2538E7.8CE2C58A_at_remove_spam.peasland.com>...
> > I've found LogMiner to be useful for two areas. One, auditing after the
> > fact. Someone wanted to know "who deleted rows of data from TableX?" and
> > we do not have auditing set up on TableX. A scan of LogMiner can
> > determine who issued which DELETE statements on TableX. Two, restoring
> > lost data that someone accidentally deleted. This has been my most
> > common use of LogMiner. I once had a developer delete every row of data
> > from a table. I could have restored from a backup, but I would have lost
> > changes in other tables. So it was off to mining the logs for me! I was
> > able to determine the UNDO statements I needed to undo the accidental
> > delete.
> >
> > HTH,
> > Brian
> >
> > Ryan Gaffuri wrote:
> > >
> > > I understand the syntax and how to use it. However, I dont have any
> > > experience actually needing to use it. When have you found it useful?
> > > Any times where its been invaluable?
> >
> > --
> > ===================================================================
> >
> > 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"
>
> how did you determine what system change number the developer deleted
> at? so you could do the restore?

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

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"