Cloud Control: OSB targets disappearing after patch
We are currently using Enterprise Manager Cloud Control version 18.104.22.168 to monitor all our database and Fusion Middleware targets. The Oracle Service Bus environments always show one target being in pending state. I can remove this target, but it would reappear after (automatic) refresh of the Weblogic domain.
Investigating this further, reveals that something is wrong in the discovery of the OSB targets.
The target ‘osb_server2_osb’ is visible twice in the navigation tree. Once as target type ‘Oracle Service Bus’ (similar to the soa-infra of the SOA Suite) and once as a ‘Clustered Application Deployment’.
So, the ‘Clustered Application Deployment’ is an illegal target and should not be present. Time to open a Service Request with Oracle Support. We needed to supply a trace on both the agent and the OMS (server) side.
Enabling a trace on the agent can be achieved through Cloud Control.
Changing the log level on the OMS side involves one command.
emctl set property -name log4j.rootCategory -value 'DEBUG, emlogAppender, emtrcAppender' -module logging
After uploading all information to support, I was asked to patch Enterprise Manager to the latest patchlevels. I proceeded and patched the agents, the Oracle Management Server and all deployed plugins (22.214.171.124).
Unfortunately, this patch did not fix my problem. It actually made things worse. Now all targets in the OSB domain (farm) were gone from the navigation tree. Rediscovery did not help. You could see the targets when going to the ‘all targets’ view, but when navigating to any target of the OSB domain, it would show up empty.
There is a workaround to this problem: The illegal target type ‘Clustered Application Deployment’ for osb_server2_osb should be removed.
After this target is removed, the OSB targets appear again. Make sure you don’t (automatically) refresh your Weblogic domain, as that would bring back the offending target.
Oracle support is aware of this issue and working on a fix (bug 18042645).
Oracle has released a fix for this issue through FMW Plug-in Bundle Patch 126.96.36.199.3 and FMW Plug-in 188.8.131.52.0: See MOS note 1625453.1