If you own enough GoldenGate core licenses for source and target, then it is
fairly straight forward as in the end it is really only data movement. If you
don’t own the licenses then it is a spendy proposition.
You can also mix and match the different movement methodologies to port from
AIX to Linux.
I ported a 50TB database 2 years ago AIX to Linux with Materialized Views and
expdp/imdp for certain of the tables across a single weekend ($0 cost for any
extra technology Golden Gate or Delphix).
For 100TB in a decent time frame you need to make sure you have sufficient
Network bandwidth and check with the sysadmins if they used Hardware
virtualization on the AIX side as the Virtualized I/O adapter is a bottleneck
on the system.
For large scale tables you need to watch out for high transaction rates to
establish the initial table port. If it is a DW then probably not a problem as
much as a highly transactive OLTP system.
If the main system is overtaxed you may need to look at a standby to pull data
from, which used before going HPUX to Linux on a highly transactive OLTP system.
Matthew Parker
Chief Technologist
425-891-7934 (cell)
Dimensional.dba@xxxxxxxxxxx
<http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's
profile on LinkedIn
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Deepak Sharma (Redacted sender "sharmakdeep_oracle" for DMARC)
Sent: Tuesday, October 27, 2015 10:20 PM
To: tim@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: AIX to Linux
Thank you all for your feedback. We'll dig into your suggestions.
In a related discussion, there was a mention of using GoldenGate to achieve the
transport from AIX to Linux.
Thoughts ?
On Tuesday, October 27, 2015 10:28 AM, Tim Gorman <tim@xxxxxxxxx> wrote:
Shameless plug follows, but hey! it's definitely relevant...
Delphix data virtualization also supports (and improves upon)
cross-platform provisioning (a.k.a. UNIX-to-Linux or "U2L").
Cross-platform provisioning has an initial validation step that requires
the use of the DBMS_TDB.CHECK_DB procedure against a READ ONLY
database. Since I'm betting that you can't set your production database
to READ ONLY even for a moment, this would necessitate creating a copy
of that 100TB database so that you can do so. Creating a 100TB virtual
database is a whole lot faster and easier than creating a 100 TB
physical database, and setting that virtual database to READ ONLY has no
impact on production.
In the same way, after the validation (presumably) succeeds and during
conversion, Delphix automates the steps of creating a virtual database
to act as a READ ONLY source and then also automates and orchestrates
the transportable tablespace (TTS) operations for the RMAN CONVERT
DATAFILE to create a virtual Linux database. Both virtual databases
(i.e. source and target) take up practically no space even with the
endian-conversion, but the two longest-running operations are the TTS
metadata export/import (which is single-threaded through Data Pump) and
the RMAN CONVERT DATAFILES themselves, which are parallelized but still
involve copying every bytes of database from source to target.
Data virtualization works really well for creating test images of the
converted Linux database to test the migrated application. For doing
the final cutover of AIX to Linux, data virtualization can also
"re-hydrate" a physical copy from the converted virtual copy, but for
some requirements this may be an overly lengthy process.
On 10/26/15 23:58, Oracle List (Redacted sender sharmakdeep_oracle for
DMARC) wrote:
What are some of the options of migrating version 11.2.0.4 DB, 100TB sized
database from AIX to Linux. This question relates to only Storage element,
like Endian conversion.
--
//www.freelists.org/webpage/oracle-l