I have detailed instructions for handling this scenario on my website. You
can view this info online via the following link, then scroll down to
Recovery Scenario #8.
http://www.dotcomsolutionsinc.net/products/installgen/win_901_32bit_files/in
stallgen_win901_39_.html#recovery_scenarios
http://www.dotcomsolutionsinc.net/products/installgen/sol_901_32bit_files/in
stallgen_sol901_39_.html#recovery_scenarios
--
David Simpson
www.dotcomsolutionsinc.net
"Burton Peltier" <burttemp1REMOVE_THIS_at_bellsouth.net> wrote in message
news:GWiNa.539$x_4.17_at_fe03.atl2.webusenet.com...
> For future reference ... just my paranoid opinion...
>
> Nightly full exports to disk in compressed mode take up very little room -
> you would be amazed how small a 50Gig database full export compressed
really
> is (depending on data could be less than 2 or 3 Gig - easily).
>
> Highly recommened you do at least a full export backup (given your
> noarchivelog mode). I personally do 4 types of backups on dev(actually
> acceptance testing DBs) and prod databases:
> - nightly hot (requires archivelog mode)
> - daily archive log backups (if in archivelog mode - 2 copies of each
log )
> - nightly full exports (start out with consistent=y, but might need to
> change to consistent=n if lots of activity during export time - which
cannot
> be change)
> - weekly cold backups (ok in our env , but probably not in others)
>
> Note: I would also have 2 copies of everything at all times and archive to
> tape, especially if easy to have an existing backup process pick up your
> backup files.
>
> --
> "MJ Wood" <maryjanewood_at_hotmail.com> wrote in message
> news:73q7gvsqbfeb4amjb6pt8304kc65h5npdt_at_4ax.com...
> > Hi,
> >
> > It happened a few day ago that one of our developer "accidentally"
> > dropped a table in our development database(no archive log). The data
> > in this table (about 100 lines) is not very important so the data was
> > re-created manually.
> > Anyway, I just wondering how can I recover the data in the dropped
> > table. This table was dropped around 4pm and at 6pm this database was
> > idle. I think the data was still in the redo log.
> > How can I rollback the tablespace to a specific time (e.g. 4pm) and
> > the transactions between 4am to 6pm can be preserved? Or it is just
> > impossible to do so?
> > Thanks in advance for any input.
> >
> > MJW
>
>
>
Received on Tue Jul 15 2003 - 18:02:49 CDT
