Re: Migrate 10.2.0.4 DB Linux IA64 to 11.2.0.4 x86-64

Check MOS Doc ID 1389592.1 Used this as a guide to move a 12TB Data Warehouse from 10.2.0.5 to 11.2.0.4. No downtime was required until the 'Transport' Phase and total downtime was around 4 hours.

On Wed, May 3, 2017 at 9:21 AM, Ls Cheng <exriscer_at_gmail.com> wrote:

> Hi
>
> My understanding is that same endianness database migration those
> tablespaces contain UNDO needs to be converted. I think I can restore a IA
> 64 backup in a x86-64 server then just run the convert for tablespaces with
> UNDO. The problem is that the source database is 4TB and a restore can take
> quite a few hours. If it was possible restore the backup then use IA64
> archivelogs and apply them in the target database the downtime will be
> minimum. Do you know if archivelogs in Linux IA64 can be applied in Linux
> x86-64 :-?
>
> Cheers
>
>
>
> On Wed, May 3, 2017 at 2:37 PM, Schneider <schneider_at_ardentperf.com>
> wrote:
>
>> On Mon, May 1, 2017 at 2:18 PM, Ls Cheng <exriscer_at_gmail.com> wrote:
>>
>>>
>>> I wonder if anyone has experience migrate database running in 10.2.0.4
>>> Linux Itanium 64 to 11.2.0.4 and 12.1.0.2 running in Linux x86-64?
>>> Transportable Database is not an option because the database is 4TB and
>>> transprtable database downtime is high.
>>>
>>> AFIAK we could use cross platform incremental backups + xtts for
>>> different endianess database and versions, does this apply for same
>>> endianess but different CPU architecture (Itanium)? I guess so but wanted
>>> to make sure.
>>>
>>
>> My understanding is that you can restore backup from any platform of same
>> endian-ness onto any other platform of same endian-ness and you don't need
>> to worry about RMAN CONVERT command. So all your normal migration options
>> should apply... data copy with rman restore or transportable tblspc, sync
>> with incrementals or logs (standby/data guard or goldengate/dbvisit), etc.
>>
>>
>>>
>>> For 12c I saw MOS note, Cross-Platform Database Migration (across same
>>> endian) using RMAN backupset in 12c (Doc ID 2013540.1) but it seems like
>>> it's for 12c -> 12c migration. For 11g -> 12c I have to use xtts.
>>>
>>
>> I think "cross-platform" in the oracle docs usually implies different
>> endian-ness. You probably don't need this.
>>
>>
>>> I tried to test this but it is extremely difficult to get hands on Linux
>>> IA servers and test with Solaris x86-64 and Linux x86-64 is not realistic
>>> because they are very compatible.
>>>
>>
>> Some migration methods should not require a second IA64 system for
>> testing. For example, if you just restore from the backup server then it's
>> possible to do the whole thing without *any* connection to the primary
>> database server at all. You can test that as many times as you want and it
>> should only put load on your backup system, not on the source server.
>>
>> -J
>>
>> --
>> http://about.me/jeremy_schneider
>>
>
>

--
http://www.freelists.org/webpage/oracle-l