Question: Can you EXCLUDE one or more tablespaces when doing a Full Transportable Export/Import?
First of all, this question came up already twice in real world customer migrations. So it’s not a totally unusual question. In one case a tablespace called USERS got precreated and some data did get stored. In the second case we did use RMAN incremental backups to migrate a very large database (>100TB) and some tablespaces weren’t part of the backup set.… [Read More]
Roy and I blogged about Full Transportable Export/Import in the past:
If you haven’t heard of this database feature, it allows you to migrate a full database by using Transportable Tablespaces as a base technology but letting Data Pump do all the manual steps for you in a one-command migration.… [Read More]
All credits go to Don Wolf, an Oracle Advanced Customer Support engineer from Ohio as he dug out this information 🙂 Thanks Don!
Do database character sets have to match EXACTLY for Transportable Tablespaces?
That sounds like a simple question. When you look into our big slide deck the answer will be a straight “Yes”.… [Read More]
One of the really cool and helpful features in Oracle Database 12c is called Full Transportable Export/Import. It combines the basics of transportable tablespaces – of course cross-platform, cross-endianess, cross-version – with Data Pump taking care on all the stuff not stored in tables and indexes, such as views, synonyms, trigger, packages etc.… [Read More]