Blackout of Weblogic domain blacks out entire database stack
We have an issue where Weblogic Admins are blacking out domains to do weblogic maintenance
but the blackout is automatically including the database system, the primary and all standby
databases and instances, ASM clusters and ASM instances and Listeners on 3 Exadatas.
We cannot control or expect the weblogic admins to sort through all the related
options to remove these from the blackout, so we occasionally find databases in blackout state.
There seems to be a bug in creating "contains" relationships.
A weblogic domain uses a database, but does not contain it.
These are consolidate databases that host multiple domains and applications.