We built a plug-in for a storage array. The topology view doesn't seem to be refreshed after removing a target. Let me try to explain.
One of its configuration metrics shows the mapping of ASM disks on the host down to the device on the target (array).
If ASM on another host uses the same storage array, we can deploy the plug-in to that host as well and get the mapping from that ASM's disks to the same array (same target type, but under different target_name). When we display the topology (via either of the targets in OEM), it will show the relationship that the array has with the ASM instances of the hosts where the plug-in is deployed.
In my test scenario I have target 1 and target 2 (of same target_type) deployed to 2 different hosts. ASM on these hosts use the same storage array.
After the initial refresh of their ECM snapshots, the topology reflected the correct situation.
Then I removed target 2, expecting that the topology of target 1 would be updated at some point, to reflect the change.
This is not happening; it is still showing the old situation. I have even refreshed the ECM snapshot of target 1, thinking this would set off the derived associations trigger.
When I run the association query directly in Oracle, it shows the correct result!
Where is this old metadata kept?
Why is it not being refreshed to reflect the new situation?