Hi, With 9i, the solution is to perform an incomplete recovery of tablespaces system+undo+the tablespace containing your table (+the tablespaces needed because of schema dependencies) on a new instance (on another server to limit the risks). Then exp/imp your table between both instances. Jerome On 10/24/05, Zabair Ahmed <roon987@xxxxxxxxxxx> wrote: > 9.2.0.5 on AIX 5L (IBM p670 Servers) > > Currently we are doing the following type of backup - incremental RMAN level > 0, 1 & 2 backups on our 2TB datawarehouse database. > > Recently one of the critical tables was dropped accidently. We have been > able to recover the dropped table by doing a point-in-time recovery. > > We cannot do full database exports as this would take to long in our backup > window. > > I know flashback table exists but only in 10g! > > > My question is how can we improve our backup method so that we are in a > better position to handle such a scenerio. > > What am looking for is how other people handle tables being accidently > dropped in their database > > TIA > > > > > ________________________________ > Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with > voicemail > > -- //www.freelists.org/webpage/oracle-l