Kevin Kempf's Blog

February 22, 2011

Discoverer 11.1.1.4 certified with 11i

Filed under: 11i, Discoverer — kkempf @ 10:48 am

Of Course

Seems like Discoverer is the only thing I’m posting about these days.  No sooner had I completed the upgrade to 11.1.1.3 when Oracle certified 11.1.1.4 with 11i.

I’ve noticed it only runs on WLS 10.3.4, so that’s a new install too.  It appears that there is some sort of “Smart Update” program to update Weblogic Server to 10.3.4 and the patch set installer will upgrade me from 11.1.1.3 (or 11.1.1.2 if I were using that) to 11.1.1.4.   We’ll see.   At least Oracle has been consistent about incrementing their versioning:

  • Oracle Fusion Middleware 11.1.1.1.0 is certified with WebLogic Server 10.3.1
  • Oracle Fusion Middleware 11.1.1.2.0 is certified with WebLogic Server 10.3.2
  • Oracle Fusion Middleware 11.1.1.3.0 is certified with WebLogic Server 10.3.3
  • Oracle Fusion Middleware 11.1.1.4.0 is certified with WebLogic Server 10.3.4

Upgrade Complete

I’ve successfully upgraded my DEV environment to 11.1.1.4.  It wasn’t as painful as 11.1.1.2 to 11.1.1.3.  Some parts were a pleasant surprise, others were what I would consider to be almost expected failure points now that I’ve run this installer a few times.

Upgrading Weblogic Server

After shutting everything down, you first upgrade Weblogic to 10.3.4.  This is pretty easy.  To find this patch,  go to My Oracle Support, Patches & Updates, Product or Family (Advanced Search).  Type in Oracle Weblogic Server as the Product, and WLS 10.3.4 as the Release.   Hit search and you get appropriate choices (appropriate if you consider PLACEHOLDER BUG FOR WEBLOGIC SERVER 11GR1 (10.3.4) UPGRADE INSTALLER a good name for a patch).  Note how it says upgrade installer.  Well pull this, invoke your environment, run the binary on your Discoverer server, and uncheck “Launch Quickstart”.  Poof!  You’re done.

Upgrading Discoverer

For me, the worst part of this upgrade was finding and downloading the applicable patch.  When I got to My Oracle Support, click on Patches & Updates,  and do a “Product or Family (Advanced Search)” and punch in Oracle Discoverer and version iAS 11.1.1.4 I get 0 results under Linux x86, Linux x86-64, Windows 32-bit.  I know iAS 11.1.1.4 isn’t really what it is (I believe it should read FMW 11.1.1.4 or possibly WLS 11.1.1.4) but given that this is the first version of Discoverer to be called 11.1.1.4, it seems the most logical.  I hate the new My Oracle Support.  It consistently fails, in almost every conceivable way.  In the end, I found the patch numbers (not available on OTN, by the way) in an obscure location in one of the readme’s about how to upgrade FMW, WLS or Discoverer (I forget which).  To save you the time, I’ve listed them here:

  • WLS Upgrade 10.3.4: 11060985
  • Discoverer Upgrade 11.1.1.4: 11060983

In the end, just run the upgrader for Discoverer, and follow the bouncing ball answering the questions.  When I was completely done, two issues.  First, the webcache file permissions were hosed again (https://kkempf.wordpress.com/2011/02/15/discoverer-11g-soup-to-nuts-install-of-11-1-1-3/ Step 5 Number 2) and my passwords were no longer hard coded in the startup and shutdown scripts (https://kkempf.wordpress.com/2011/02/15/discoverer-11g-soup-to-nuts-install-of-11-1-1-3 Step 5 Number 5)

What’s New

Beats me.  The patch says “The list of bugs fixed is not available. Consult the Read Me file.” You won’t find it in the readme.  It will point you to the 11.1.1.4 Portal, Forms, Reports and Discoverer Release Documentation.  I click on release notes there, and select my platform, and it brings me to the Oracle Fusion Middleware Release Notes (11gR1 or 11.1.1) for Linux x86.  I gave up.  I’m going to go with Discoverer 11.1.1.4 is awesome, that’s what’s new.

Edit 4/27/11

It turns out, I had to revert to 11.1.1.3 because some of my reports broke in 11.1.1.4.  This issue revolved around 11.1.1.4’s apparent inability to understand date parameters (in some workbooks) and I wasn’t about to re-write reports for the sake of this lousy upgrade.  All I can say is it was unexpected (I’d never had a problem with a minor skip release like that before) and I recommend you test all your workbooks before upgrading.

Advertisements

11 Comments

  1. Hi Kevin,

    I upgraded WLS from 10.3.3 to 10.3.4 by running patch 11060966:

    -rw-r–r– 1 oraofm dba 21450 Jan 11 16:09 README.html
    -rw-r–r– 1 oraofm dba 1096607099 Feb 22 15:45 p11060966_1034_LINUX.zip
    -rwxr–r– 1 oraofm dba 1099629965 Jan 10 16:36 wls1034_upgrade_linux32.bin

    ./wls1034_upgrade_linux32.bin

    You pointed patch 11060985, which is a .jar file after uncompress:

    -rw-r–r– 1 oraofm dba 21450 Jan 11 16:09 README.html
    -rw-r–r– 1 oraofm dba 1089483531 Feb 24 09:53 p11060985_1034_Generic.zip
    -rwxr–r– 1 oraofm dba 1090382716 Jan 10 16:34 wls1034_upgrade_generic.jar

    I’m not sure what to do with this jar file. I’ll need to upgrade portal from 11.1.1.3 to 11.1.1.4 next.

    Thanks for the posting.
    Jennifer.

    Comment by Jennifer Chen — February 24, 2011 @ 12:22 pm

    • For linux x86 (I did discoverer only, but the patch appears to include portal, forms, reports and discoverer), unzip the patch 11060983 (you had a different number) and cd to Disk1. From there, just ./runInstaller. For x86_64, I imagine it’s the same way?

      $ ls -ltr
      total 12
      drwxrwxr-x 3 oradevl dba 4096 Jan 2 06:24 Disk2
      drwxrwxr-x 3 oradevl dba 4096 Jan 2 06:24 Disk3
      drwxr-xr-x 5 oradevl dba 4096 Jan 10 18:31 Disk1
      $ cd Disk1
      $ ls
      doc install readme.htm runInstaller stage

      Comment by kkempf — February 24, 2011 @ 1:15 pm

  2. I completed WLS 11.3.4 and portal 11.1.1.4 upgrades. I can no longer start node manager – recall that you posted somewhere – there is a permission issue that you encountered?

    Thanks very much!
    Jennifer.

    Comment by Jennifer Chen — February 24, 2011 @ 5:13 pm

    • The most common problems I found were here step 5 #1,2 and 5. You might also double check the startup scripts, which I mention in the same post, step 6.

      Comment by kkempf — February 24, 2011 @ 7:10 pm

  3. Hi Kevin,

    Everything works fine now. The node manager start script is located in a different directory…

    Your posting helped me located the patches – I was downloading from OTN and had compatible issue while upgrading WLS to 10.3.4…

    Thanks again for the blog articles.
    Jennifer.

    Comment by Jennifer Chen — February 24, 2011 @ 7:11 pm

  4. Hi Kevin,

    i would like to know if i could install in the below manner

    1. weblogic server 10.3.4
    2.discoverer 11g(11.1.2)
    3.discoverer 11.1.4

    my doubt is without creating RCU can i JUST install weblogic server & Discoverer and then can i go to RCU install?

    please help i would like to do this because i will get the database details lately .

    i have installed the windows version Disco admin and i will get the EUL by today . i have a test server for which i can check the fusion version , so just want to confirm from you , if i can proceed with the above

    Thanks
    Kanna

    Comment by kanna — March 9, 2011 @ 9:56 am

    • I think you can. I didn’t actually go directly from 11.1.1.2 to 11.1.1.4 so I can’t comment on that part. The key is that you do NOT run the Discoverer configuration piece before the RCU piece. Only do the software install for Discoverer to get it to whichever version you like. The Discoverer configuration piece asks questions about where your repository is, and I suspect it will outright fail if you haven’t done the RCU step already.

      Comment by kkempf — March 9, 2011 @ 10:55 am

  5. Hi Kevin,

    information provided by you is very useful.

    i have seen now discoverer 11.1.1.4.0 is certified with Rel 12.1.3 applications and 11.1.1.4.0 discoverer is certified with 10.3.4 weblogic server. what about RCU version. i could only search in OTN 11.1.1.3.0 and 11.1.1.2.0 which version i should use for Rel 11.1.1.4.0 discoverer.

    i am also doing a fresh install of discoverer. so, can i go directly with 11.1.1.4.0 of discoverer. please help me. Thanks.

    ps: i observed RCU is a 32 bit linux version. is there 64bit version of RCU or can i go with 32 bit version. i am on linux 64 bit version OEL5.

    Best Regards,
    Siva

    Comment by siva — September 9, 2011 @ 4:29 pm

    • I can’t really speak to 11.1.1.4. I tried to upgrade to it, and many of my existing reports stopped working right. When I contacted support to troubleshoot why going to WLS 10.3.4 and Disco 11.1.1.4 they weren’t interested in fixing broken reports. So I gave up and said I have no compelling reason to get to 11.1.1.4 so why go through the headache.

      As to the install, I always did an incremental upgrade path. As I recall, 11.1.1.2 was a mandatory baseline for 11.1.1.3 and 11.1.1.4 so my guess is that you still need to put that down first. I don’t know if there’s a 64-bit version of the RCU, and I’m not sure it would matter. In my case, I ran it from a 32-bit host even though discoverer was 64-bit and my database was 64-bit. It’s not actually landing executables on your host; it’s just upgrading your database schema. I think once it has TNS connectivity, it could care less what else is on the machine it runs from.

      Comment by kkempf — September 12, 2011 @ 12:02 pm

  6. Hi Kevin,

    I am doing 10g discoverer to 11g discoverer,
    Installation of 11g FMW i fallowed the steps as fallows:

    1.Installed Web logic server 10.3.5
    2.created table spaces using RCU 11.1.1.5
    3.Installed 11.1.1.2 pfrd with install software option
    4.upgraded to 11.1.1.4 pfrd and then started configuration,

    here configuration step Creating EM Agent is failing,here is error message,any ideas..?

    agent is creating on both instances(as_1 and asinst_1)

    MBean Server Connection is :javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection@1694516
    disco.discosoft.com 7001
    Instance asinst_1 already exists, continuing with component creation
    /u01/oradisco/Oracle/Middleware/as_1 /u01/oradisco/Oracle/Middleware/asinst_1 asinst_1
    oracle.as.config.ProvisionException: Failed to start the component
    at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:137)
    at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:73)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv._createComponent(ASInstanceProv.java:401)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv.createComponent(ASInstanceProv.java:358)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstanceAndComponents(ASInstanceProv.java:136)
    at oracle.as.provisioning.engine.WorkFlowExecutor._createASInstancesAndComponents(WorkFlowExecutor.java:523)
    at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:439)
    at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
    at oracle.as.install.classic.ca.standard.StandardWorkFlowExecutor.execute(StandardWorkFlowExecutor.java:65)
    at oracle.as.install.classic.ca.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:26)
    at oracle.as.install.classic.ca.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:61)
    at oracle.as.install.classic.ca.ClassicConfigMain.doExecute(ClassicConfigMain.java:124)
    at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
    at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
    at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
    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:63)
    at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
    at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
    at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
    at java.lang.Thread.run(Thread.java:619)
    oracle.as.provisioning.exception.ASProvisioningException

    aused by: oracle.as.provisioning.util.ConfigException:
    Error creating ASComponent emagent_asinst_1.
    Cause:
    An internal operation has failed: Failed to start the component
    Action:
    See logs for more details.
    at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv._createComponent(ASInstanceProv.java:414)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv.createComponent(ASInstanceProv.java:358)
    … 17 more
    Caused by: oracle.as.config.ProvisionException: Failed to start the component
    at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:137)
    at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:73)
    at oracle.as.provisioning.fmwadmin.ASInstanceProv._createComponent(ASInstanceProv.java:401)
    … 18 more

    oradisco@disco asinst_1]$ opmnctl status

    Processes in Instance: asinst_1
    ———————————+——————–+———+———
    ias-component | process-type | pid | status
    ———————————+——————–+———+———
    emagent_asinst_1 | EMAGENT | N/A | Down
    Discoverer_asinst_1 | PreferenceServer | 15616 | Alive
    Discoverer_asinst_1 | ServicesStatus | 15615 | Alive
    webcache1 | WebCache-admin | 15538 | Alive
    webcache1 | WebCache | 15539 | Alive
    ohs1 | OHS | 15405 | Alive

    [oradisco@disco asinst_1]$

    Comment by satishk — February 29, 2012 @ 10:05 am

    • It’s simply been too long since I implemented this. I’d open a ticket with Oracle.

      Comment by kkempf — March 1, 2012 @ 3:17 pm


RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Create a free website or blog at WordPress.com.