OBIEE 11g: After Applying A Patchset Upgrade To A Cluster / Scale-Out, Configuration Changes In Enterprise Manager Only Get Changed On Node 1
Last updated on JULY 07, 2015
Applies to:Business Intelligence Suite Enterprise Edition - Version 220.127.116.11.5 and later
Business Intelligence Server Enterprise Edition - Version 18.104.22.168.5 and later
Information in this document applies to any platform.
You have upgraded a cluster environment from OBIEE 22.214.171.124.0 to OBIEE 126.96.36.199.0, 188.8.131.52.0, 184.108.40.206.0. All processes on all servers are running.
If you attempt to change any of the configuration via Enterprise Manager Fusion Middleware Control, the configuration changes are written and made on the primary node, but the are not made on any of the subsequent nodes (node 2, node 3, ... nodeN )
When you try to deploy a repository via Enterprise Manager, you get the following error:
Supplementary information regarding operation: MANAGED_SERVER:bi_server2;FAILED_CONTACTING_MANAGED_SERVERS;Specified BI Managed Servers are shut down: bi_server2.
Changing any other configuration, such as Presentation Server configurations, you may see the following in Enterprise Manager:
" Activate Changes - Completed Successfully
Commit failed with 0 errors and 1 warnings. Problems reported by: bi_server2. See detailed logs for more information."
The Enterprise Manager ( EM ) trace file: emoms.trc may show the following warning:
[20XX-XX-XXT23:44:05.743+10:00] [AdminServer] [WARNING] [EM-02694] [oracle.sysman.emai.view.bi.impl.ProgressDialogHelper] [tid: Thread-88] [userId: weblogic] [ecid: 4142b85b3529d073:53b50ffa:14dce00da51:-8000-000000000000043f,1:23972] [APP: em] Supplementary information regarding operation: MANAGED_SERVER:bi_server2;FAILED_CONTACTING_MANAGED_SERVERS;Specified BI Managed Servers are shut down: bi_server2.
Unregistering the instance and re-registering does not resolve the issue.
ORACLE_INSTANCE/bin/opmnctl registerinstance -adminHost server.domain -adminPort 7001
Scaling in node 2, nodeN and scaling back out does not resolve the issue.
Reviewing the mbean "DomainConfigProxy" in Enterprise Manager, you may notice that this mbean is not registered on bi_server2, bi_serverN. The status of bilocaladmin.ear is showing as OK on all servers.
It should look like this:
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