This is a blog post I wanted to write a long time ago – and I missed it. Today, my best buddy Jony Safi shared an issue from a customer migration he had been pulled in the other day. I read the SR, and it dawned me that others may have seen this error as well. As a result, Transportable Tablespaces fails with ORA-01647 – TABLESPACE IS READ-ONLY – and there are two ways to solve this. Let me add ORA-6512 and ORA-1647 in case you search without the trailing zero.

Photo by Ben Harritt on Unsplash

I received an interesting question about how to implement Fallback Strategies with Full Transportable Export/Import several times within the past weeks. So it may be a good idea to showcase some possible scenarios.
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?

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
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).