Em12c -> Rac One Node Database Relocation Is Creating Performance Issues on OMR
(Doc ID 2182109.1)
Last updated on FEBRUARY 20, 2019
Applies to:Enterprise Manager for Oracle Database - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 12.1 to 13.1]
Information in this document applies to any platform.
On Enterprise Manager Cloud Control, Target Database, Listener, ASM, Grid Infrastructure (HA)
We are encountering problems with Rac One Node database relocation in EM12c version 184.108.40.206 using database plugin 220.127.116.11.4.
When we are doing database patching on two half rack Exadata on which a lot of rac one databases exist (these two clusters are heavily consolidated) they are observing high concurrency on the OMS repository database and massive blocking sessions and because of this not all Rac One targets are relocated successfully to the other node. In order to avoid total crash of EM12c, as a workaround, they are stopping the agents on the involved servers and then continue with the database relocation. After the agents are stopped, all the locks from the database are gone, the high concurrency decreases immediately and the relocation job remains in suspended status. When the agents are started back, EM starts to correct the things but it didn't manage to do it for all forcing them the update manually the configuration at EM level applying different workarounds (blackout the target, relocate manually the target using emcli, update monitoring configuration accordingly depending on the status on which they;ve remained).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document