OBIEE 11g: 'Name is null' Error Happens When Using Mbean Browser Commit to Enable Usage Tracking

(Doc ID 2281299.1)

Last updated on JULY 04, 2017

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.7.150120 and later
Information in this document applies to any platform.

Symptoms

You are trying to implement the steps in 9 Managing Usage Tracking to enable Usage Tracking. After completed the first 9 steps and prepared to implement step 10 to release the lock on domain as following,

------------------------

9.2.2 Setting Direct Insertion Parameters

...

   10. After applying your changes, release the lock on the domain, as follows:

          a. Return to the BIDomain MBean where group=Service under oracle.biee.admin, Domain:bifoundation_domain, BIDomain.

          b. Display the Operations tab.

          c. Click one of the commit operations.
------------------------

you may notice that there are 2 Commit buttons on the screen as following:

 

 

According to above step 10, you clicked the commit button with Description of "Saves any changes made to the domain and releases the lock..." and then clicked Invoke button with no parameter in Value text box,

 

it fails with "Name is null" error:

------------------------

Error occurred while executing operation.
javax.management.RuntimeMBeanException: Name is null

javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: Name is null at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222) at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1022) at weblogic.management.remote.wlx.ClientProvider$WLXMBeanServerConnectionWrapper.invoke(ClientProvider.java:291) at weblogic.management.remote.wlx.ClientProvider$WLXMBeanServerConnectionWrapper.invoke(ClientProvider.java:291) at oracle.sysman.emas.model.browser.JMXAccess.invokeOperation(JMXAccess.java:1812) at oracle.sysman.emas.model.browser.JMXAccess.invoke(JMXAccess.java:1806) at oracle.sysman.emas.model.browser.JMXAccess.invoke(JMXAccess.java:1777) at oracle.sysman.emas.model.browser.MBeanNodeInfo.invokeOperation(MBeanNodeInfo.java:809) at oracle.sysman.emas.view.browser.MBeanBrowserViewBean.operationInvoke(MBeanBrowserViewBean.java:1216) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.sun.el.parser.AstValue.invoke(AstValue.java:187) at

...

------------------------

Cause

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