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.
Two requirements must be met to use this new functionality:
- Oracle 188.8.131.52 plus Exadata BP12 (patch 12982245)
- One-off patch 13340675 contains the RMAN extension and is currently available on top of BP12 on Oracle 184.108.40.206
Let me know if you have further questions – and this restriction on Oracle 220.127.116.11 with BP12 applies to the intermediate instance you’ll use to roll forward your converted incremental backups only. Source might be Oracle 10.2 whereas target might be also an Oracle 18.104.22.168 installation.
Thank you Mike for such a wonderful blogs and sharing so much of knowledge and your experience. Mike can you help me with few questions :-
dest_scratch_location=/dest_backups/=== Can we mention here ACFS location for backups in XXTS properties file
Can we mentione multiple locations in xxts properties file for dest_scratch_location=dest1,dest2,dest3
What is maximum no of files and max size of ACFS storage.
I have minimum downtime for performing this activity so can you please assist how to tune and optimize the restore which take hours to complete around 8 hours for more then 3 TB dbases. Are they any paramerters which we can set at source or target to expediate this operations.
excluding BCT feature while taking incremental backups.
I really don’t know about ACFS. I know NFS works but ACFS has some limitations. But I could think of it working. Still, never tried it.
If you want to speed up things, at first it is essential to use a BCT for the inc backups to be sped up. And in addition, you may want to run multiple sessions of the PERL scripts, each of them with a separate tablespace set and a separate log tree, in parallel.
Hi Mike. I have a question. After using multiple sessions of perl script xttsv4 for backup, convert, restore and merge. Do I need only one FTEX and import on target for metadata or I need one .dmp for each set?
Very good point: And the answer is “YES, you need only one expdp/impdp”.