I would:
Connect via dgmgrl
Show configuration when primary is 'DB_B';
Confirm that redo goes from DB_B to DB_C (and DB_A but we’ll be removing
that later).
If there’s no route then
Edit database 'DB_B' set property redoroutes = '(LOCAL:DB_C)';
And confirm again
If happy, do
Validate database verbose 'DB_B';
And if happy
Switchover to 'DB_B’;
Once switchover complete and you’ve confirmed DB_C is being updated. Remove
DB_A from all redoroutes on B and C (C should look similar to B).
Disable database 'DB_A';
Remove database 'DB_A';
Then you should be okay to shut down DB_A.
Thanks,
Andy
On Fri, Sep 9, 2022 at 1:04 PM, Mike Killough <mwkillough@xxxxxxxxxxx>
wrote:
Sorry for the repeat first send said failed but it didn’t.
Sent from my iPhone
On Sep 9, 2022, at 3:01 PM, Mike Killough <mwkillough@xxxxxxxxxxx> wrote:
Ok so I could do a switchover to B and C and A become standbys, then
remove A from the configuration before shutting it down and closing the
data center? No hard failover. Thanks
Sent from my iPhone
On Sep 9, 2022, at 2:32 PM, Andy Sayer <andysayer@xxxxxxxxx> wrote:
Instead of doing a failover, you would need to do a switchover. You should
set up your redoroutes in advance in dgmgrl. You should also use this to
test the configuration using the
Show configuration when primary is DB_B.
Syntax
Remove the old server from the redo routes before getting rid of it.
Hope that helps,
Andy
On Fri, Sep 9, 2022 at 11:51 AM, Mike Killough <mwkillough@xxxxxxxxxxx>
wrote:
Currently we have a primary database (DB_A) and 2 standbys (DB_B & DB_C).
We are planning on hard failing over to one of the standby databases to
retire the current primary. To protect the future standby when it becomes
primary, we would like to be able to have a standby right away if possible.
When we fail over to DB_B, is there a way to make DB_C immediately be the
standby for DB_B?
Mike Killough
Sent from my iPhone
