OEM13c DG mis-configuration
From: Craig Healey <templar1118_at_gmail.com>
Date: Tue, 17 Jul 2018 11:03:20 +0200
Message-ID: <CAGiM01wOkeHEknv9mA_v+hE5OizxmhSQs2sQ8ZHvaez_VzvQEw_at_mail.gmail.com>
Hi,
We've been moving databases from OEM 12c to 13c. Most of the moves have been OK, but I have 1 problem.
We have an Acceptance DB (12.1 on a Solaris 11.3 virtual machine) without Data Guard
We then have a production database with DG, also 12.1 on Solaris 11.3 virtual machines.
In OEM13c, both the Acceptance and Production databases are shown as having DG set up, and both point to the same DG machine, even though Acceptance isn't using DG.
I've removed and re-added all three to OEM, but I still get the Acceptance DB saying it's got DG.
If I go into Data Guard Administration on the Production Database, under Additional Configuration, it has Remove Data Guard Configuration. But if I do the same on the Acceptance Database it says not configured with Data Guard broker and gives no further options. The three other DBs with similar configurations don't exhibit this behaviour. Any idea as to how to stop OEM thinking the Acceptance DB has DG configured?
Date: Tue, 17 Jul 2018 11:03:20 +0200
Message-ID: <CAGiM01wOkeHEknv9mA_v+hE5OizxmhSQs2sQ8ZHvaez_VzvQEw_at_mail.gmail.com>
Hi,
We've been moving databases from OEM 12c to 13c. Most of the moves have been OK, but I have 1 problem.
We have an Acceptance DB (12.1 on a Solaris 11.3 virtual machine) without Data Guard
We then have a production database with DG, also 12.1 on Solaris 11.3 virtual machines.
In OEM13c, both the Acceptance and Production databases are shown as having DG set up, and both point to the same DG machine, even though Acceptance isn't using DG.
I've removed and re-added all three to OEM, but I still get the Acceptance DB saying it's got DG.
If I go into Data Guard Administration on the Production Database, under Additional Configuration, it has Remove Data Guard Configuration. But if I do the same on the Acceptance Database it says not configured with Data Guard broker and gives no further options. The three other DBs with similar configurations don't exhibit this behaviour. Any idea as to how to stop OEM thinking the Acceptance DB has DG configured?
Regards
Craig
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 17 2018 - 11:03:20 CEST