Em12c -> Rac One Node Database Relocation Is Creating Performance Issues on OMR
Last updated on MARCH 08, 2017
Applies to:Enterprise Manager for Oracle Database - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Enterprise Manager Cloud Control 22.214.171.124.0 using database plugin 126.96.36.199.4, Target Database, Listener, ASM, Grid Infrastructure (HA)
We are encountering problems with Rac One Node database relocation in EM12c version 188.8.131.52 using database plugin 184.108.40.206.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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms