Oracle BI EE 11g – Upgrading from BI EE 10g – Repository & Web Catalog

August 23rd, 2010 by

BI EE 11g is a significant feature filled release when compared with the previous 10g release. Most customers who are planning to upgrade to 11g have an automated way of upgrading their 10g Web Catalogs and repositories to the 11g version. When moving from 10g to 11g, we will have to go through the upgrade utility as there are significant changes to the repository structure and the web catalog structures. A direct copy & paste into the 11g version will not work.

The upgrade process involves the following steps

1. Install the new 11g version in either the same machine or a different machine.
2. Run the upgrade assistant utility to upgrade the repository & Web Catalogs.
3. Migrate other 10g specific customizations manually to the 11g instance. The different customizations are

a. Any Static files added to the 10g app server
b. Custom XML messages
c. Styles & Skins (The upgrades for this will have to be done carefully as some CSS & files have changed in this release)

4. Upgrade the Scheduler schema (Both BI Delivers & BI Publisher) through the upgrade utility
5. Upgrade BI Publisher

In this blog entry we shall see how to go about upgrading the RPD and Web Catalogs from the 10g to the 11g version. After installing 11g, start up the upgrade assistant utility from {ORACLE_HOME}/bin/ua (or ua.bat if you are on windows)

The upgrade assistant can be used to upgrade the scheduler schema, BI Publisher as well as the RPD & Web Catalogs. Lets start with the first option, i.e. upgrading RPD and Web Catalogs

In the upgrade screen, choose the 10g RPD along with the Web Catalog Path. In the Deliveries folder, choose the 10g deliveries path ({OracleBIData}/web/catalog/deliveries

In the next screen, provide the details of the weblogic server on which we will be deploying the Repository and Web Catalog to.

The upgrade utility does not seem to support remote deployments of the RPD and Web Catalog i.e. Upgrade Utility will only deploy the repository and web catalog on the machine containing the weblogic admin server.

The upgrade process will stop all the components first and then will do the individual RPD and Web Catalog Upgrade.

This is just a utility. We cannot expect all the reports to start working out of the box immediately after an upgrade. Good amount of testing is required to make sure all the older queries of the most commonly used reports are working without any major issues. Also, not all the reports would get migrated seamlessly due to the significant changes across the versions which the utility cannot recognize. Care has to be taken to make sure that all the warnings logged as part of the upgrade process are properly analyzed and corrected manually. A sample upgrade log is shown below (containing 4 warnings)


Comments

  1. Giridhar Says:

    This is an excellent post. Thanks alot Venkatakrishnan

  2. Joe Says:

    Hi Venkat, Thanks for all the excellent blogs. Those have been just fantastic.
    After upgarding the 10G RPD to 11G, the 11G RPD is not able to connect to database.
    When I try to view the data from the Physical layer I am getting the error message “The Connection has failed.” Tried couple of times. Still the same issue.

    More Info here:
    http://forums.oracle.com/forums/thread.jspa?threadID=1118668&tstart=0

  3. Erick Says:

    Venkat,

    Thanks as always for the great posts. For new OBI Apps clients, what are your thoughts on using Obiee 10G infrastructure (as we have always done with Apps 7.9.6.1) or installing 11G and doing the upgrade?

  4. Paul Says:

    Hi Venkat,
    This is a very good article. I also saw your reply to Joe’s question aboveregarding the database connection issue on Oracle Forum. Thanks for that reply.
    I have a simillar question. What if your RPD is connecting to SQL Server, will the migration utility will migrate the RPD successfully? Any important things to follow before doing this migration if your RPD is connecting to SQL Server?

    Thanks again.

    Regards.

  5. Vandana Says:

    Installed 11g OBIEE. Using Oracle apps 7.9.5 RPD.Upgraded the 10g RPD successfully. Now when we try to do any changes in RPD through BI Admin Tool it does not allow us to save changes.
    It gives and error as follows:
    [nQSError 46008] Internal error: File server\Metadata\Src\SMPrettyStringvisitor.cpp, line 1996.
    any idea how it can be resolved?

  6. kolluru Says:

    I am upgrading my Catalog using the UA. I provided all the info needed and got th below error:

    [2010-10-13T15:20:03.021+01:00] [BIEE] [NOTIFICATION] [upgrade.BIEE] 10g Catalog : C:\obiee11\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking\catalog\UsageTracking
    [2010-10-13T15:20:03.175+01:00] [BIEE] [NOTIFICATION] [upgrade.BIEE] 11g Catalog : C:\obiee11\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog\UsageTracking
    [2010-10-13T15:20:03.175+01:00] [BIEE] [NOTIFICATION] [upgrade.BIEE] 10g Deliveries Directory : C:\obiee11\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking\catalog\deliveries
    [2010-10-13T15:20:03.182+01:00] [BIEE] [NOTIFICATION] [upgrade.BIEE] 11g Deliveries Directory : C:\obiee11\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog\deliveries
    [2010-10-13T15:20:30.760+01:00] [BIEE] [ERROR] [upgrade.BIEE] javax.management.RuntimeMBeanException: Cannot refresh – Currently locked[[
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:897)
    at oracle.as.jmx.framework.generic.spi.interceptors.ContextClassLoaderMBeanInterceptor.internalInvoke(ContextClassLoaderMBeanInterceptor.java:94)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:245)
    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:245)
    at oracle.as.jmx.framework.generic.spi.security.AbstractMBeanSecurityInterceptor.internalInvoke(AbstractMBeanSecurityInterceptor.java:174)
    at oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:245)
    at oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.invoke(OracleStandardEmitterMBean.java:803)
    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 weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
    at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:268)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
    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 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 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.invoke(RMIConnectionImpl.java:788)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:590)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:478)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:119)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.IllegalStateException: Cannot refresh – Currently locked
    at oracle.bi.management.adminservices.model.impl.DomainManagerImpl.refresh(DomainManagerImpl.java:382)

    Not sure what it could be! any idea V?

  7. AJ Says:

    Venkat,
    Upgraded web catalog and rdp..everything went fine. Now when upgrading BI Publisher reports, whats the target folder path need to be given where the upgraded BIP reports will be store , so as to access the reports from catalog.

  8. JanaJohnny Says:

    Dear Venkat Ramanan,

    Dont we require to install weblogic server where as a part of OBIEE11g.

Website Design & Build: tymedia.co.uk