I thought I had blogged about this topic already. But it seems to be that I stored this information somewhere else. Randomly I receive this question: Oracle Transportable Tablespaces – Does it work between SE2 and EE?
In addition often the question gets precised: Does it work in both directions or just one-way?… [Read More]
This topic fits very well as I present about +100 TB migrations today at the “Harmony” User Group Conference in Finland.
Finland in May
The question whether the PERL scripts for RMAN incrementally rolled forward backups we deliver via MOS Note 1389592.1 (11G – Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup) will be supported for migrations to non-Exadata systems such as Oracle SuperCluster as well.… [Read More]
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]
We recently worked with a customer who noticed that they were not able to use transportable tablespaces to connect the same tablespace data files to two databases at the same time, even after setting the tablespaces READ ONLY in SQL*Plus. This is new behavior in 12c, and many customers are not yet aware of this change.… [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]
Nice little best practice for statistics and Data Pump when doing either Transportable Tablespaces or Full Transportable Export-Import (credits to Roy and Dean Gagne).
Transport Statistics via a Staging Table
First of all we always recommend to exclude statistics when doing a Data Pump export as the import of such stats takes way longer than transporting them via a stats table.… [Read More]
As we have already mentioned in our recent workshops the MOS Note:1389592.1 is public now:
- MOS Note:1389592.1
Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backups
This technique currently works for migrations to Linux64 and is supported by Oracle Support for Exadata migrations only. It utiliuzes RMAN incremental backups to reduce the large amount of downtime it takes to copy and convert the datafiles cross Endianness.… [Read More]