This sounds like a situation where a user inadvertently inserted classified data in an unclassified database. I suppose one could recreate the table(s) with CTAS with a very clever where clause and follow up with a CREATE CONTROLFILE after dropping the offending redo/undo. It would be an interesting exercise if there was enough time to attempt it. Gus Spier Gus.Spier@xxxxxxxxx 540 454 3074 > On Sep 26, 2014, at 4:17, Niall Litchfield <niall.litchfield@xxxxxxxxx> wrote: > > Well you can certainly skip tablespaces , and your backup command doesn't > have to be "backup database" so it's certainly possible not to back it up. > I'd like to know what the rationale was though. > >> On Thu, Sep 25, 2014 at 2:12 PM, Jeremy Schneider >> <jeremy.schneider@xxxxxxxxxxxxxx> wrote: >> someone asked me recently if it's possible to completely remove the data in >> one tablespace from all historical backups of a database. my knee-jerk >> response was simply "no" - thinking that even if you had the tablespace >> backups in their own backupsets, you couldn't remove data from undo and redo >> streams. >> >> nonetheless I'm curious if anyone else on the list has ever thought about >> this and what you've come up with. if there was a business requirement to >> do this, then how close could you come? >> >> -Jeremy >> >> -- >> http://about.me/jeremy_schneider > > > > -- > Niall Litchfield > Oracle DBA > http://www.orawin.info