I was curious if anyone has run into this problem before. We've done monthly data guard switch overs without issue in the past. We recently upgraded our OEM to 12c. Our data guard databases were correctly identified in there as primary and standby. We performed the first switch over with 12c - however now each database target type now shows database instance: primary - even though the usoh3 one in the case below is now standby.
The data guard broker shows the configuration correctly. And when you log into the database target via OEM and drill into it, it also shows the configuration correctly. However the main page shows both instances as primary. Has anyone perhaps seen that sort of behavior before?
Also new is when choosing 'verify configuration' in OEM for the data guard setup - it hangs on the step showing 'updating dataguard configuration' - so i suspect it is related, but I am not sure what. The data guard setup is working as expected - but would like to resolve this OEM issue to keep future switchovers from potentially running into issues. thanks!