The Next-generation Cross-platform Migration for Oracle Database

Cross-platform Transportable Tablespaces (XTTS), Migration 1 Minute

I am very pleased to share that Oracle has officially launched a new method for cross-platform migrations of Oracle Database.

M5 Cross Endian Platform Migration using Full Transportable Data Pump Export/Import and RMAN Incremental Backups (Doc ID 2999157.1)

The M5 script is the next-generation cross-platform transportable tablespace migration procedure for Oracle Database

You can also use the script for cross-endian migrations, so this is perfect for AIX, HP-UX or SPARC migrations to Exadata Database Machine or any other little endian platform.

Next-generation

Before we launched M5, you would use the XTTS v4 Perl script for such migrations.

Timeline of methods for cross-endian migrations

We launched the latest version of the XTTS v4 Perl script many years ago. Over the last years, as databases grew bigger and bigger, we saw multiple issues with XTTS v4 Perl script, including:

  • No multisection backups for bigfile tablespaces
  • No encrypted tablespaces
  • Inefficient parallelism
  • Incomplete multitenant support

We wanted to solve all those issues with M5 – and we did! M5 uses newer RMAN functionality, and we made the procedure much simpler. It relies entirely on out-of-the-box RMAN functionality. On the source:

BACKUP ... TABLESPACE ... ;

On target we use:

RESTORE ALL FOREIGN DATAFILES ... ;

The latter command was introduced in Oracle Database 18c and enhanced in Oracle Database 19c. This means that the requirements for source and target database are:

Want to Know More?

We have a webinar later today about this new method. If you are interested, we still have open seats.

Cross Platform Migration – Transportable Tablespaces to the Extreme, February 22, 16:00 CET

Next week, we will add the recording to our YouTube channel. Be sure to subscribe so you don’t miss out on anything.

If you want a sneak peek at the slides, go ahead.

I have an elaborate blog post series about cross-platform migrations. I will soon update it with more information about the M5 migration method.

Happy Migrating!

Published

3 thoughts on “The Next-generation Cross-platform Migration for Oracle Database”

  1. have you seen this error before ?

    24-FEB-26 09:59:25.613: ORA-39014: One or more workers have prematurely exited. 24-FEB-26 09:59:25.614: ORA-39029: worker 1 with process name “DW00” prematurely terminated 24-FEB-26 09:59:25.614: ORA-31671: Worker process DW00 had an unhandled exception. ORA-21780: Maximum number of object durations exceeded. ORA-06512: at “SYS.KUPW$WORKER”, line 2684 ORA-06512: at “SYS.KUPW$WORKER”, line 14489 ORA-06512: at “SYS.KUPW$WORKER”, line 7158 ORA-06512: at “SYS.KUPW$WORKER”, line 29241 ORA-06512: at “SYS.KUPW$WORKER”, line 27274 ORA-06512: at “SYS.KUPW$WORKER”, line 27207 ORA-06512: at “SYS.KUPW$WORKER”, line 34987 ORA-06512: at “SYS.KUPW$WORKER”, line 13125

    Like

    Reply

  2. Yes, I have already created a SR on this, but it seems weird, since I did the same cross platform migration with M5 scripts on the test environment, but got this error on the production environment migration. (from Solaris SPARC to Oracle Linux both Oracle 19.25)
    The message “Maximum number of object durations exceeded” is a bit confusing. sound like a datapump limitation.

    Like

    Reply

Leave a comment