Skip to Main Content
  • Questions
  • Data Pump- Full restore did not drop the table created after export backup

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Kritika.

Asked: November 17, 2022 - 2:56 am UTC

Last updated: November 25, 2022 - 6:00 am UTC

Version: 19.13.0.0.0

Viewed 1000+ times

You Asked

Scenario->
We took Full export of Oracle database on date 10th--> then created few new tables on date 11th--> then ran FULL restore using export backup on 10th--> somehow, the tables created after 10th did not drop and still showing in database. However, the data inside table is gone, meaning zero records in table now.

Shouldn't full import bring back database to it's original state that was on 10th, when new tables did not exist?

and Connor said...

Import is generally *additive* unless you explicitly tinker with parameters (eg TABLE_EXISTS_ACTION). For example, if you have a database with schemas "X" and "Y", and you imported a full datapump export that contained schemas "A", and "B", then once the import is done, you'll have all four schemas.

If you want to be able to bring an entire database back *exactly* to a previous state, then DataPump is not the ideal tool for that. You would be better off taking a full backup with RMAN and then restore that backup.

If you want to persist with datapump, and want to bring the database back to its original state, you're probably better off dropping the schemas you want to replace before commencing the import.

Is this answer out of date? If it is, please let us know via a Comment

More to Explore

Data Pump

All of the database utilities including Data Pump are explained in the Utilities guide.