After An OBI EE Restart, Only The Secondary Node Instance (Instance2) Is Showing Due To The 'topology.xml' & 'obiee-domain.xml' Files Losing Their Reference To The Primary Instance (Instance1)
Last updated on SEPTEMBER 28, 2016
Applies to:Business Intelligence Server Enterprise Edition - Version 18.104.22.168.140114 and later
Information in this document applies to any platform.
The 'Topology.xml' and 'obiee-domain.xml' XML files have become corrupted and no longer refer to the original Instances created.
Currently the Fusion Middleware Control (FMWC) point to the second Node which is not configured to run and therefore the Services do not start up as expected
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms