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
A long time ago my colleagues published PERL scripts to assist especially with cross platform Transportable Tablespace migrations. The PERL scripts allow you to utilize incremental backups. This way you can decrease the downtime in a migration with large databases significantly. But there are different MOS Notes for xTTS PERL scripts available. Which one should you take?
The biggest pain points in a transportable tablespace migration are usually the size of the database and its complexity. With RMAN Incrementally Rolled Forward Backups you can tackle the size aspect. Instead of having a long downtime …
Continue reading...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.
And yes, now we got an update into the note saying:
Although preferred destination system is Linux (either 64-bit Oracle Linux or a certified version of RedHat Linux), this procedure can be used …
Continue reading...
RSS Feed for Upgrade your Database – NOW!