Re: Migration validation to OCI
Date: Wed, 17 Apr 2024 01:06:22 -0300
Message-ID: <CAJdDhaND=Gq5sP=TkE=exgj7Hczg=G5wy1Ody+i6KAgzJwmfaQ_at_mail.gmail.com>
Thanks Albert for your answer.
Em seg, 15 de abr de 2024 00:54, Al B. <albert.y.balbekov_at_gmail.com> escreveu:
> Since OS on both Exadata and OCI is Linux, why don’t use Dataguard Standby
> based migration approach and stop worrying about object-level mismatch ?
> The Dataguard replication works on binary level, so the object level sync
> is guaranteed.
>
>
> https://docs.oracle.com/en/solutions/reduce-database-migration-downtime/learn-migrating-oracle-data-guard1.html
>
>
> thanks,
> Albert
>
> On Sun, Apr 14, 2024 at 5:28 AM Eriovaldo Andrietta <ecandrietta_at_gmail.com>
> wrote:
>
>> Hello,
>> An exadata database server onpremise will be migrated to OCI As Is to the
>> same Oracle version (12.x).
>> I would like to know what else would have to be validated at OCI to
>> ensure that the migration was successful.
>> I thought I would check:
>>
>> - dba_users
>> - dba_objects (and each object type separately)
>> - dba_tab_privs
>> - dba_sys_privs
>> - dba_roles
>> - dba_synonym
>> - dba_extents (in order to check the volumn)
>> - count the number of lines for each table, or to check at the dba_tables
>> numrows if the statistics are updated.
>> I guess that the number of lines migrated are enough to accept to
>> content of the table
>>
>> The goal is to check only in the context of objects and not configuration
>> (v$parameters, tablespaces, resource manager and other structures).
>> What else could be validated?
>>
>> Regards
>> Eriovaldo
>>
>>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Apr 17 2024 - 06:06:22 CEST