Kevin Kempf's Blog

June 29, 2010

Discoverer 11g Installation on 11i

Filed under: 11i, Discoverer — kkempf @ 3:33 pm

Another Upgrade for the sake of Upgrading

Looking at my list of things to do, I recalled that Discoverer 10g ( was on the bubble for upgrade to Discoverer 11g.  If you read here regularly, you’ll recall  that originally, Oracle planned to kill support for in December of 2010, but something changed and they gave AS 10.1.2.x a 1 year reprieve (page 8).  I have no particular inclination to perform this upgrade, except that it’s just another “thing” to do sooner or later, and I had the time to play with it, in earnest, this week.

Product Certification

Like other Fusion entities (EM 11g and possibly R12, sooner than you’d think), Discoverer 11g ditched Oracle application server and moved to Weblogic Server.  Discoverer 11g comes in 3 flavors at the moment:, and  Per Oracle support, the certified version combinations are:

  • Oracle Fusion Middleware is certified with WebLogic Server 10.3.1
  • Oracle Fusion Middleware is certified with WebLogic Server 10.3.2
  • Oracle Fusion Middleware is certified with WebLogic Server 10.3.3

When you add E-Business Suite 11i (or R12), you’re immediately stuck at (as of this moment).  Late breaking news, is now certified

Installation Overview

One of my major gripes with (con)Fusion 11g, is that the installs are so convoluted and peculiar.  In the case of Discoverer 11g, you first have to install Weblogic (10.3.2).  This actually went off without a hitch, and simply provides the framework from within which Discoverer can run.

Next you have to run the Repository Creation Utility (rcu) against your E-Business suite RDBMS.  This is like a mini-install, which effectively just forms a database connection and creates some new tablespaces and upgrades your repository to make it “11g ready”.  What, exactly, it upgrades, is a mystery to me.  Finally, you have to install Discoverer, but the installer includes everything but the kitchen sink.  I kid you not, here’s what’s in the download:

  • HTTP Server
  • WebCache
  • Portal
  • Forms Services
  • Forms Builder
  • Reports Services
  • Report Builder/Compiler
  • Discoverer Administrator
  • Discoverer Plus
  • Discoverer Viewer
  • Discoverer Services
  • Discoverer Desktop
  • Enterprise Manager Fusion Middleware Control

After running the Discoverer install, I’m required to apply patch 9387227 for 11i interoperability.  Of course, this won’t  work until I’ve applied patch 6880880 – you got it, the latest OPatch to the Oracle Home.  You can find Discoverer, the Repository Creation Utility and Weblogic here.   Interestingly, the RCU and  Weblogic are at the end under “Required Additional Software”.   To get 9387227 or 6880880 you can just search from Metalink.

So in the end, to install Discoverer, it’s Weblogic Server 10.3.2 (1 CD),  RCU (1 CD), Discoverer (4 CDs), and 2 one-off patches.  I wish this was bundled in some understandable way, but Fusion appears to be a patchwork of installs in competition with the labyrinth of Minos for clarity.

Weblogic 10.3.2 Installation

Nothing difficult here.  Just choose your paths and follow the bouncing ball, so to speak.  Just remember not to check the Quick Launch at the end.  The screen shots below depict 10.3.3; this is because I forgot to take screen shots during the 10.3.2 install.  They’re virtually identical from a GUI standpoint, I almost don’t even need to include any of them.

Launching the Weblogic Installer from the command line

Welcome Screen

Tell the installer where the Middleware home will reside

Don't call me; I'll call you

Just choose "Typical"

Give it a path. Coherence is new.

Here's the gigabyte of "stuff" I'm going to install

Happily working at installing

Repository Creation Utility

Just figuring out how to launch this thing was annoying.  When unzipped, it creates a folder called rcuHome, which has about 25 directories in it.  From the bin directory, run rcu.  The options and required information is pretty self explanatory until you get to step 3 called “Select Components”.  Under Portal and BI, you select Discoverer (only) and proceed.  Shortly after this time it connects to your ERP database, creates a few tablespaces owned by a schema owner you designated, and ultimately unceremoniously dumps you back to the command prompt.

Launching the Repository Creation Utility

Welcome Screen

Create (as opposed to drop) the components

Provide database connectivity information

Warnings, verifications, etc

You only need to select Discoverer

New Schema Passwords

New Tablespaces will be created

Final look before it runs


First of all, could the versioning be more confusing?  While someone at Oracle may think is a great name for a version, I personally do not.  How about Discoverer 11gR1.2?  Or, perish the thought, just Discoverer 11gR2?  Are there really going to be that many versions of this thing?  Alright, once again, this install was largely “follow the bouncing ball”.   I purposely chose the defaults, and in the process created an near indiscernible mess on the operating system between ORACLE HOME being called as_1 and the ORACLE_INSTANCE being called asinst_1.  I’d urge you to try using something more meaningful.  I did make the weblogic domain name Discoverer, as I suppose, in theory, it could host multiple applications.  Under components, once again I chose to deselect everything I could (including Enterprise Manager for Fusion) and choose only Oracle Discoverer and the Oracle Web Cache.   I used auto port configuration and unchecked the “Use Application Level Identity Store” and we don’t use OID for authentication.  After running at the end, it said it was done successfully.

Launching the Discoverer Installer

Choose Install & Configure

System Prerequisite Checks

Provide the weblogic domain information you wish

Sign up for Oracle spam

Provide details on the installation location(s) and names

Choose Discoverer and web cache, uncheck clustered if applicable. Enterprise Manager at your discretion

Choose Discoverer and web cache, uncheck clustered as applicable. Enterprise Manager at your discretion.

Let Oracle figure out the ports..

Create a connect string: or the like

OID integration, which I don't have to worry about

Installation Summary

Installation in Progress

It's not an install without

Post install configurations

Successful install

Helpful summary of locations and ports

More of helpful summary with URLs

OPatch & Interop Bug

These installed without incident, though the hardest part was figuring out how to set environmental variables for the new Discoverer 11g environment.  For what it’s worth,

the MIDDLEWARE_HOME is the base Middleware directory
the ORACLE_HOME is a subdirectory Middleware/as_1
the ORACLE_INSTANCE is subdirectory Middleware/asinst_1

Webcache Bug

I always hit a problem with the webcache.  The weblogic server was happily up and running, but when I went to the URL for discoverer, I got nothing.  There was some vague message to the effect of:

Failed to assign port 8090: Address family not supported by protocol

After a surprisingly responsive and competent analyst helped me for the better part of the day, I realized I was hitting a bug spelled out in ID 1113163 (which was supposedly only relevant to Suse Linux).  Effectively, there was a problem out of the box with IPv6 (which I didn’t have enabled on the host).  After adding <IPV6 ENABLED=”NO”/> tag below the </MULTIPORT> tag in the webcache.xml file, all was good and I was finally able to log in.

TNS conFusion

Since I started working with Oracle, the tnsnames. ora file has gone in $ORACLE_HOME/network/admin.  So Discoverer requires it in the instance home:  Middleware/asinst_1/config.  Makes sense to me.  Until you put in a valid entry for your ERP database, you cannot connect.  I put the file under the Middleware/as_1/network/admin (aka ORACLE HOME) and made a symbolic link to it in the Middleware/asinst_1/config directory.

Default URLs

Discoverer Plus: http://hostname:8090/discoverer/plus

Discoverer Viewer: http://hostname:8090/discoverer/viewer

Weblogic Server Administration: http://hostname:7001/console

Weblogic Marketing Propoganda: http://hostname:7001

Initial Impressions

Aside from the capacity to remember some of the login information and save it so I don’t have to type everything about my connection every time I go there, there appears to be no fundamental difference between Discoverer 10g and Discoverer 11g.  This truly was an upgrade merely for the sake of upgrading, my favorite kind. </sarcasm>


Creating connections is an improvement over 10g

Saved Session


Profile options

I should note, there’s a bunch of profile option values and autoconfig context file values which you may wish to change.  Realistically, I’m not sure how much they affect, but you should follow note 1073963.

Blog at