Testing for Upgrade using Dataguard Standby
From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Tue, 23 Mar 2021 14:54:21 -0500
Message-ID: <CAJvnOJYNAQUfPtxpoK1uB1Rn0F_SdLcosgcQ-aKv=rG99kNXxw_at_mail.gmail.com>
For reasons too numerous to list, it is necessary for us to do some upgrade validation testing on our existing dataguard standby of production. This is an upgrade from 11.2.0.4 to the latest 19c version. These are the steps I can see as needed for the process of validation and testing:
Date: Tue, 23 Mar 2021 14:54:21 -0500
Message-ID: <CAJvnOJYNAQUfPtxpoK1uB1Rn0F_SdLcosgcQ-aKv=rG99kNXxw_at_mail.gmail.com>
For reasons too numerous to list, it is necessary for us to do some upgrade validation testing on our existing dataguard standby of production. This is an upgrade from 11.2.0.4 to the latest 19c version. These are the steps I can see as needed for the process of validation and testing:
- Install and patch the 19c software to the most recent version.
- Create a guaranteed restore point on the standby database.
- Open the standby database read-write.
- Run DBUA to upgrade the snapshot standby to 19c.
- Run testing as required
- Shutdown standby
- startup mount the standby from the 11g home and revert to the guaranteed restore point.
- Resume the redo apply on the standby.
Am I missing a step here? Will there be a problem with the control files when I flash the database back to the restore point after an upgrade? I would think there would not be a problem since oracle should be designed to handle this, but I have tried an upgrade of a snapshot standby before, though I have done other destructive testing of course.
-- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.'-- http://www.freelists.org/webpage/oracle-l Received on Tue Mar 23 2021 - 20:54:21 CET