This discussion is archived
8 Replies Latest reply: Sep 11, 2013 1:55 AM by user3529761 RSS

11.1.1.7 installation error

user1299751 Newbie
Currently Being Moderated
I am installing 11.1.1.7 with Enterprise Option.


The installation stops at CONFIGURE BI DOMAIN.



Configure BI Domain

Error

Warning: Element Type DOMAIN
Element id: null
Operation Result: FAILED_TO_APPLY_CHANGES
Detail Message: Timeout; Waiting for all managed servers to push configuration changes; [180 secs]; bi_server1

Step Configure BI Domain failed
Configuration Action 'Configure BI Domain' has failed. Please check logs for details.
Step Configure BI Domain failed
  • 1. Re: 11.1.1.7 installation error
    SivakumarBala Newbie
    Currently Being Moderated
    Hi ,

    There are few pre-configuration check up to be performed before installing OBIEE 11.1.1.7,

    1. Make sure there are not default (7000-7999) ports running in the Servers.
    2. Look Back adapter to be Configured , Statis Ip should be configured in Host File.
    3. Check the Java Version of the Server should be greater than JDK 1.5

    Regards,
    Siva.
  • 2. Re: 11.1.1.7 installation error
    user1299751 Newbie
    Currently Being Moderated
    All pre-configuration check were passed when i started installation.
  • 3. Re: 11.1.1.7 installation error
    1003883 Newbie
    Currently Being Moderated
    I am getting the same issue. I feel this has something to do with some component of the older version of OBIEE still being there causing conflict with the new version. Did you have an older version of OBIEE?? Was a full uninstall done including weblogic?? This will give us an idea of the reason behind this error. I am working on it and will get back once I figure it out too.
  • 4. Re: 11.1.1.7 installation error
    user1299751 Newbie
    Currently Being Moderated
    I have 11.1.1.3 installed on this machine before. I deinstall it and also remove registy entries.
  • 5. Re: 11.1.1.7 installation error
    1003883 Newbie
    Currently Being Moderated
    Failed again.. This is the detailed message in the log.. no idea how to decode this.. At least 3 hours of effort cleaning the earlier installation and waiting for the new installation process to reach this stage is wasted.. twice..

    Executing Task: Configure BI Domain
    Failed to rollback: javax.management.RuntimeMBeanException: javax.management.RuntimeMBeanException: Cannot release MBean - not locked
    javax.management.MBeanException: WARNING: Element Type: DOMAIN
    Element Id: null
    Operation Result: FAILED_TO_APPLY_CHANGES
    Detail Message: Timeout; Waiting for all managed servers to push configuration changes; [180 secs]; AdminServer
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
         at javax.management.remote.rmi.RMIConnectionImpl_1035_WLStub.invoke(Unknown Source)
         at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:919)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.security.Security.runAs(Security.java:61)
         at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:917)
         at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
         at oracle.as.install.bi.biconfig.standard.BIDomainConfigureTask.discoverProcessConfigAndOtherBits(BIDomainConfigureTask.java:98)
         at oracle.as.install.bi.biconfig.standard.BIDomainConfigureTask.doExecute(BIDomainConfigureTask.java:66)
         at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
         at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
         at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
         at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
         at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
         at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
         at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
         at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
         at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
         at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: javax.management.OperationsException: WARNING: Element Type: DOMAIN
    Element Id: null
    Operation Result: FAILED_TO_APPLY_CHANGES
    Detail Message: Timeout; Waiting for all managed servers to push configuration changes; [180 secs]; AdminServer
         at oracle.bi.management.adminservices.mbeans.impl.BIDomainMBeanImpl.throwExceptionIfEventLogOverThreshold(BIDomainMBeanImpl.java:291)
         at oracle.bi.management.adminservices.mbeans.impl.BIDomainMBeanImpl.commit(BIDomainMBeanImpl.java:249)
         at oracle.bi.management.adminservices.mbeans.impl.BIDomainMBeanImpl.commit(BIDomainMBeanImpl.java:258)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:1012)
         at oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java:104)
         at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
         at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalInvoke(AbstractMBeanSecurityInterceptor.java:190)
         at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
         at oracle.security.jps.ee.jmx.JpsJmxInterceptor$2.run(JpsJmxInterceptor.java:358)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
         at oracle.security.jps.ee.jmx.JpsJmxInterceptor.internalInvoke(JpsJmxInterceptor.java:374)
         at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
         at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:103)
         at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
         at oracle.as.jmx.framework.generic.spi.interceptors.MBeanRestartInterceptor.internalInvoke(MBeanRestartInterceptor.java:116)
         at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
         at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.invoke(OracleStandardEmitterMBean.java:924)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:349)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
         at java.security.AccessController.doPrivileged(Native Method)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
         at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:263)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
         at java.security.AccessController.doPrivileged(Native Method)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
         at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
         at java.security.AccessController.doPrivileged(Native Method)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
         at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
         at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
         at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11$1.run(JMXConnectorSubjectForwarder.java:663)
         at java.security.AccessController.doPrivileged(Native Method)
         at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:661)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:654)
         at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
         at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
         at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
         at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
         at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
  • 6. Re: 11.1.1.7 installation error
    864639 Explorer
    Currently Being Moderated
    This step comes after restarting AdminServer and bi_server1.

    So please check if both these servers are up and running.

    You can check the same by connecting to Admin Console. http://host:port/console

    Generally default port is 7001.

    if you see any server is Admin state then try to manually stop and start servers and click on Retry on installer.
  • 7. Re: 11.1.1.7 installation error
    user1299751 Newbie
    Currently Being Moderated
    i check. the core bi services does not start. and failed when I try to restart several times.
  • 8. Re: 11.1.1.7 installation error
    user3529761 Newbie
    Currently Being Moderated

    Hi All,

     

    we face the same issue and struggled lot to resolve the issue. Finally with the help of Oracle Support we were able to resolve the issue

     

    Cause: In Linux it is using ipv6 network. OBIEE 11.1.1.7.0 support only ipv4.

     

    ifconfig -a  should show the below o/p


    ifconfig -a

    bond0     Link encap:Ethernet  HWaddr 00:17:A4:77:60:10 

              inet addr:10.0.0.1  Bcast:10.3.4.5  Mask:255.255.254.0

              inet6 addr: fe80::217:a4ff:fe77:6010/64 Scope:Link

    by default ipv6 configured and it causing BI Domain configuration failure. you can verify with the below command

     

    netstat -tulpn | grep 9704


    this should listen to only ipv4 IP. if it listens to IPv6 also then we will get this problem


    Solution:

    I add this line to the /etc/sysctl.conf file:

     

    1. net.ipv6.conf.all.disable_ipv6 = 1

     

    I also did :

     

    chkconfig ip6tables off

     

    After doing both I rebooted the system and able to install the OBIEE succesfully.

     

    Regards,

    Nagarjuna

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points