Re: Fwd: RE: convert big endian to medium endian
Date: Sun, 9 Feb 2020 20:24:50 -0500
Message-ID: <6281666b-d832-b634-8084-eb9c1650ac12_at_gmail.com>
Hi Ahmed!
I am just throwing ideas on the table. Nobody can give you the exact
answer as to what to do and how to do it. The first piece of information
is how much downtime can you tolerate and how much will an hour of
downtime cost your company. It your answer includes the word "minutes",
then the only option are various replication tools like GG or SharePlex.
There are also variables like the schema complexity, tablespace
dependencies, LOB columns and domain indexes. One thing that nobody has
mentioned is that you can't do transportable tablespace export if you
have domain indexes, like text indexes. The whole things needs to be
treated like a project with several dry runs and will likely take a
better part of a year.
On 2/9/20 12:19 PM, Ahmed Fikri wrote:
> Thanks a lot for all this information. I think it is at first worth to
> see if the patch suggested by J. Lewis will make the metadata export
> faster. I think if we get the export in less than 24 hours, we will be
> more than happy.
>
> Thanks and regards
> Ahmed
>
--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Feb 10 2020 - 02:24:50 CET