Andrew
I agree that doing upgrade using manual or with DBUA might not take more time
but had to plan to make sure Rollback is not issue due to any issue in upgrade.
So standby can be one way and can you share any link as how this can be planned
and tested. If I am correct that we might have to switch Physical standby to
logical or so for this planning so that once Standby is upgraded and make it
primary, then main primary can be upgraded. I will try this option also as one
option even that might add more complexity due to datatypes and steps
TxSanjay
On Monday, November 16, 2020, 06:16:01 PM EST, Andrew Kerber
<andrew.kerber@xxxxxxxxx> wrote:
Well, the upgrade time really isn’t dependent on the size of the database. I
do recall there can be issues upgrading the time zone via dbua, so you don’t
want to check that option. I expect you can do the upgrade with just an hour or
so of downtime. Make sure you go through the documentation on upgrading the
standby first. If zero downtime is required, that gets a lot harder considering
the amount of data that needs to be copied.
Sent from my iPad
On Nov 16, 2020, at 16:05, Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx> wrote:
Hi Everyone
I had 160 Tb Database in 12.2 and had to upgrade to 19c. Can you please suggest
the best option that can help to update with small downtime and also option to
rollback for any failure without going for big Restore that can take day for
the restore. Some details for the database and option that can be used are
- 12.2 is CDB with one PDB that has to be upgraded
- ASM storage has additional 200 Tb available to be used for this upgrade
purpose ,if required for any option
- It is Exadata with two node
- Environment also has Dataguard on another Data Center with same hardware
like primary
- Golden Gate license is available for any option that can save downtime
Thanks for your time and suggestion
Sanjay
