RE: the best approach to migrate a database to new server

From: Clay Jackson (cjackson) <"Clay>
Date: Fri, 31 Jan 2020 21:30:33 +0000
Message-ID: <MWHPR19MB0141F4CFF5ECD549E36FE6E59B070@MWHPR19MB0141.namprd19.prod.outlook.com>



Not sure I get why you’d need the dblink; but you should be able to at least test datapump to get timings and the like.

Of course, if your source database is at all busy, you’ll have to do have a big flashback area, or take downtime (or look at something like replication)

Clay Jackson
Database Solutions Sales Engineer
clay.jackson_at_quest.com<mailto:clay.jackson_at_quest.com> office 949-754-1203 mobile 425-802-9603

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of ahmed.fikri_at_t-online.de Sent: Friday, January 31, 2020 1:11 PM
To: oracle-l_at_freelists.org
Subject: AW: the best approach to migrate a database to new server

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

Hi,

would it make sense to use datapump (dop = 32) via a dblink to migrate the data schema-wise?

I would also like to use the opportunity to use different tablespaces for the different schemas. And maybe doing the migration schema by schema.

Has anyone had the experience of copying 10 TB from 11g (under AIX) to 12c (oracle linux) using a data pump and dblink

Regards

Ahmed

-----Original-Nachricht-----

Betreff: AW: Re: Re: the best approach to migrate a database to new server

Datum: 2020-01-31T18:29:55+0100

Von: "ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de>" <ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de>>

An: "oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>" <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>>

Hi,

we have a lot of table partitions. The vendor application on the db uses in my opinion the partitioning abuselly. Everyday the application generate a thousand of new partitions. But this will be a subject for another question.

Thanks a lot for sharing your experience Ahmed



Gesendet mit der Telekom Mail App<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkommunikationsdienste.t-online.de%2Fredirects%2Femail_app_android_sendmail_footer&data=02%7C01%7Cclay.jackson%40quest.com%7Cf5635fd0607e45383e6208d7a692286d%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637161018988872347&sdata=KhiThmtIVFi2JpzHkLICjfOdSU%2BbvAQZOdahGDolDRU%3D&reserved=0>
  • Original-Nachricht --- Von: Ls Cheng Betreff: Re: Re: the best approach to migrate a database to new server Datum: 31.01.2020, 18:16 Uhr An: ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de>

Hi

I have done around 80 migrations with TTS and incremental backups. Downtime from 20, 30 minutes to 2, 3 hours.

The downtime is NOT 0. It depends on the number of database objects because the data refresh part is fast because it uses incremental backups but the export and import time depends on number of objects.

BR

On Fri, Jan 31, 2020 at 6:13 PM ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de> < ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de>> wrote: I guess that's exactly what we need and everything else doesn't make sense. However does someone know how long could take the migration of the 16 TB db? I found article that said the downtime is 0

https://ittutorial.org/new-oracle-xtts-v4-reduce-transportable-tablespace-downtime-using-cross-platform-incremental-backup<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fittutorial.org%2Fnew-oracle-xtts-v4-reduce-transportable-tablespace-downtime-using-cross-platform-incremental-backup&data=02%7C01%7Cclay.jackson%40quest.com%7Cf5635fd0607e45383e6208d7a692286d%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637161018988872347&sdata=aOLWZ6%2FK9mObNB4FiusrpopBzw6OhofnhzwuJ6ZB6vI%3D&reserved=0>/

Regards
Ahmed



Gesendet mit der Telekom Mail App<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkommunikationsdienste.t-online.de%2Fredirects%2Femail_app_android_sendmail_footer&data=02%7C01%7Cclay.jackson%40quest.com%7Cf5635fd0607e45383e6208d7a692286d%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637161018988882342&sdata=7KUt5TD3Zdu%2BD1i6aE%2Fvx0fYJjN9Gce2eeTyb9Q3mxY%3D&reserved=0>
  • Original-Nachricht --- Von: Ls Cheng Betreff: Re: the best approach to migrate a database to new server Datum: 31.01.2020, 17:42 Uhr An: ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de> Cc: oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>

Hi

Try

V4 Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 2471245.1)

BR

On Fri, Jan 31, 2020 at 3:25 PM ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de> < ahmed.fikri_at_t-online.de<mailto:ahmed.fikri_at_t-online.de>> wrote: Hi all,

we are planning to migrate a 16 Terabyte database from 11g on aix machine to 12c on linux. In the target db is Dataguard used. The DB has about 50 Schemas the biggest one is about 11 TB the second is 2.6 TB then four with each one 1 TB the rest is each one less than 1 TB. Unfortunately all Schemas share the table spaces.

Wich approach could we use with less downtime?

My idea was to move the schemas to separate tablespaces an migrate the Schemas using transportable ts. Or somehow copying the metadata to do new instance in such way the new db use the old data files and then copy them separately one by one.

Or even copying the Schemas separately using dblink and data pump.

Any idea please?

Regards
Ahmed Fikri



Gesendet mit der Telekom Mail App<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkommunikationsdienste.t-online.de%2Fredirects%2Femail_app_android_sendmail_footer&data=02%7C01%7Cclay.jackson%40quest.com%7Cf5635fd0607e45383e6208d7a692286d%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637161018988882342&sdata=7KUt5TD3Zdu%2BD1i6aE%2Fvx0fYJjN9Gce2eeTyb9Q3mxY%3D&reserved=0> 
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jan 31 2020 - 22:30:33 CET

Original text of this message