Question - standby database from Exadata to non-exadata ?
From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Wed, 18 Jul 2018 07:36:44 -0500
Message-ID: <CAP79kiTRvPHWYSg_d_BWW-ZpU+6rVZcyw5tkiVPgcwVkMhSGmw_at_mail.gmail.com>
We're gearing up for a massive migration to an Exadata machine and in the process we're going to be freeing up a lot of our previous hardware and storage. The current storage is Pure m70.
2. If so, what issues (gotchas) did you run into that we may need to consider?
3. Does this sound like a 'bad idea' already? My gut is telling me this may be a bad idea.
Date: Wed, 18 Jul 2018 07:36:44 -0500
Message-ID: <CAP79kiTRvPHWYSg_d_BWW-ZpU+6rVZcyw5tkiVPgcwVkMhSGmw_at_mail.gmail.com>
We're gearing up for a massive migration to an Exadata machine and in the process we're going to be freeing up a lot of our previous hardware and storage. The current storage is Pure m70.
What we 'thought' we were going to do was something like this (high level):
1. Migrate DB to Exadata 2. Rebuild standby dbs on non-exadata using the now freed up Pure storage 3. Clone dev/test/staging environments from Standby DB on Pure
HOWEVER, I'm not sure that's doable as Exadata uses TDE and Advanced Compression. It doesn't appear that Pure likes using AC at the DB layer and instead prefers managing the compression and deduplication internally.
Question(s):
1. Has anyone here built a standby on different hardware from Exadata when
primary is on Exadata?
2. If so, what issues (gotchas) did you run into that we may need to consider?
3. Does this sound like a 'bad idea' already? My gut is telling me this may be a bad idea.
Chris
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Jul 18 2018 - 14:36:44 CEST