Subscribe to Blog via Email
Events & Presentations
- RMOUG Training Days 2017 more » on Feb 07 2017
Sometimes you want to change the way you are managing, monitoring or notifying in your EM12c environment that may require you to delete and recreate you administration groups. If you are testing out administration groups, then you may very likely create, delete and recreate, as they are not something you can edit as you go along, (the system even warns you of this as you create them.
As I was working through a unique notification issue and how to handle it with administartion groups, I experienced a failure on creation after the deletion of a former admin group in EM12c, BP1:
As the previous admin group had been deleted and this failed, it was obvious that something hadn’t cleaned up properly after the previous admin group. I’m not a fan of tearing into the SYSMAN schema, but this one was worth a look at not much was connected to it to begin with.
The error gave us a clear indicator of what we needed to look into:
We now knew what column and the table this came from. How much data was contained in this table?
As there was only one row and it only contained the group hierarchy row info, I made a copy of the table, deleted the row, then committed it.
Can I now create my administration group?
Success. I removed the copy of the table and proceeded to create the new monitoring templates for the groups.
Knowing the data behind the scenes, still making a copy of it, “just in case” is important when you are required to do a quick fix so toproceed forward when a job to clean up something like an administration group hasn’t cleaned up as much as it should have.