OEM can not handle to remove one instance from a 3 node cluster DB
Hi,
The problem is that we had a 3-node cluster database and we removed one instance, so now the database is running just on 2 nodes. Because of this modification our jobs/metrics don't work because oem tries to execute those on the master node (master agent), but no instance on that node.
Underlying Issue is that we removed the instance on the master node(Master Agent Host), and OEM did not update its information correctly and displaying error message when we click on Database home page (java.lang.Exception: No Such Target ) ,and also all the scheduled jobs are going to suspended state as they are not able access the instance.
The problem is that we had a 3-node cluster database and we removed one instance, so now the database is running just on 2 nodes. Because of this modification our jobs/metrics don't work because oem tries to execute those on the master node (master agent), but no instance on that node.
Underlying Issue is that we removed the instance on the master node(Master Agent Host), and OEM did not update its information correctly and displaying error message when we click on Database home page (java.lang.Exception: No Such Target ) ,and also all the scheduled jobs are going to suspended state as they are not able access the instance.
0