Kevin Kempf's Blog

February 15, 2011

Discoverer 11g: Soup to Nuts install of

Filed under: 11g, Discoverer — kkempf @ 11:43 am

Why Soup to Nuts?

I was looking at my statistics on my most visited pages, and the entries on Discoverer 11g installation and Enterprise Manager 11g installation are by far tops.  I was using my own entries as a guide to re-install Discoverer 11g the other day (it needed to be relocated to a new server) and I realized it was a bit confusing, with important information in several different posts.

What’s New?

Details regarding how to change the default Discoverer 11g client timeout (60 mins), how to install Discoverer on a 64-bit platform, and applying the January 2011 CPU.  Other than that, I’m mostly just smoothing wrinkles in the walk through, and putting it all in one place.  I’m not going to detail as it’s just a subset of and you can find the information elsewhere on the blog.

Environment Variables/Paths I reference

MIDDLEWARE_HOME=Middleware Install Location (xxx/xxx/xxx/Middleware)





Step 1: Weblogic

The first step is to determine, download and install the appropriate version of WebLogic server.  According to my Oracle technology salesperson (as opposed to the 11i Apps salesperson), this is free as we are paying for Discoverer.  I encourage you to check your license terms before you assume you’re entitled to this product, as much has changed since the “old days” of 4i.
You can find the downloads at  Note, my experience is only installing on Linux, but I’ve done both 32-bit and 64-bit installs so I can go through those.  This is by far the easiest part of the whole install.

Ensure that your WebLogic version lines up with your planned Discoverer install

Oracle Fusion Middleware is certified (only) with WebLogic Server 10.3.3 and Apps 11i

If you’re running the 32-bit installer, you just execute the downloaded .bin file; it contains java already and is an executable binary.  If you’re installing the 64-bit version, you’re getting a jar file which isn’t platform specific.  You need to start the installer by using syntax: java -jar wls1033_generic.jar or the like.

There’s really nothing to the install.  I went with defaults, although I’m not sure I needed Oracle Coherence, I figured it wasn’t worth the effort of researching it much further.  There’s only one last item of note here: uncheck and don’t run the quickstart when it’s done laying down the files.

Finally, if you screw up, don’t like the install location, or change your mind, there’s an oui uninstaller buried in there somewhere.  That still leaves a mess on the filesystem (and inventory, in my experience) so the other option is to rm -rf the whole install directory and clean up the oracle inventory ($INVENTORY_HOME/oraInventory/ContentsXML/inventory.xml) to remove references to the install you just did.

That’s it.  Check the box, you’re done with the WLS install for now.  Once all the pieces are installed, there’s a few critical files you may wish to manually edit (regarding starting services) but I’ll go over that later.

Step 2: Discoverer Fusion Installation

Once again, you need to pull the install for the appropriate version of Discoverer.  You can find the downloads at towards the bottom of the page.

Since I’m only concerned with, pull Portal, Forms, Reports and Discoverer ( and Portal, Forms, Reports and Discoverer (  The installer is only an upgrade from, so you have to run both of them.  Note that there’s also the Windows-only Discoverer Desktop and Discoverer Administrator ( which you will probably need, as well as the Repository Creation Utility (RCU)

Start with the Fusion Middleware (FMW) install.  Simply run the installer and follow the bouncing ball, but ensure you select software only install.  There’s no sense trying to configure, you’re not going to use it.   When it’s done, run the installer.

I don’t recall which installer ( or asks for what, but here’s what’s of note during the questions it asks.

  • It will want to know where your Fusion Middleware home is.  Point it to the WLS 10.3.3 install home.
  • Remember the password you provide for the weblogic user, it’s important
  • Stick with the defaults, unless you’re an experienced Weblogic user, regarding Oracle Home name (as_1), Oracle Instance name (asinst_1), and the domain name (ClassicDomain).
  • Under components to install, uncheck everything except Oracle Discoverer and Web Cache. Note there’s a checkbox for Clustered there also.  I unchecked it, have no idea what checking it leads to but it wasn’t applicable to me.

At this point, both installers should be done, but nothing should be configured.

Step 3: Repository Creation Utility (RCU)

The RCU just creates a few tablespaces, new users, and objects in the database.  I don’t know for certain if it uses your existing repository, but it seems that it does.  To launch the RCU, unzip the file, and run the executable called rcu which is in the bin directory.

Of note to the questions it asks:

  • The only thing you need checked on the entire Select Components screen is Discoverer.  (Under Portal and BI-> Discoverer)
  • Remember your new schema user and passwords, they will be required during the configuration of Discoverer and Weblogic.  I recommend SID_DISCOVERER (PROD_DISCOVERER)

Step 4: Configuration

Now you will need to run $MIDDLEWARE_HOME/as_1/bin/ to complete the Discoverer setup.

Most of this should be easy to answer by now, but of note are a few things:

  • Under Specify Schema, use the SID_DISCOVERER (PROD_DISCOVERER) schema you set up with the RCU
  • Unless you’re using OID, uncheck Use Application Level Identity Store.  I missed this once (I don’t use OID) and troubleshooting the startup was impossible.  I had to reinstall the whole stack.
  • I recommend using Auto Port configuration if possible
  • At the end of the GUI, it displays all ports and URLS.  I recommend you save this file to the OS as it’s a handy reference for how to get to the WLS server and Discoverer login page.
  • Follow note 1073963 which details some profile option values which you need to change in 11i to accommodate Discoverer 11g.

Step 5: Fixes

1.  Fix the webcache bug (doc 1113163.1) “Failed to assign port 8090: Address family not supported by protocol”if you hit it

  • Edit the file $MIDDLEWARE_HOME/asinst_1/config/WebCache/webcache1/webcache.xml
  • Add <IPV6 ENABLED=”NO”/> tag below the </MULTIPORT> tag

2.  I also hit a common webcache problem this time, where the webcache wouldn’t start because webcached permissions hadn’t been set right:

  • Navigate to $MIDDLEWARE_HOME/as_1/webcache/bin
  • As root, run setroot (username) where username is the user who installed the webcache
  • Permissions should look like this when you’re done: -rwsr-x— 1 root    dba 6796777 Dec  3 11:32 webcached

3.  Copy/link the approriate (8.0.6 home for 11i installs) tnsnames. ora file to 2 locations with a command like this (substitute cp for ln if you want to simply copy the file, obviously)

  • cd $MIDDLEWARE_HOME/asinst_1/config
  • ln -s $8.0.6_HOME/network/admin/SID_host/tnsnames.ora
  • cd $MIDDLEWARE_HOME/as_1/network/admin4
  • ln -s $8.0.6_HOME/network/admin/SID_host/tnsnames.ora

4.  Change the Discoverer default timeout

  • Edit the attribution Timeout in ORACLE_INSTANCE/config/PreferenceServer/Discoverer_instance-name/pref.txt
  • Run ORACLE_INSTANCE/Discoverer/Discoverer_instance-name/util/

5. Hard code your password in the startup/shutdown scripts

  • Edit $DOMAIN_HOME/bin/ and
  • add entries for:
    • WLS_USER=”weblogic”
    • export WLS_USER
    • WLS_PW=”password”
    • export WLS_PW

Step 6: Starting/Stopping

These scripts works great for me.  You may have to tweak them a bit, but it’s tested and proven.  Note the sleeps are in there because it takes time to crank some of the services, and unless they’re running the next step fails.  60 seconds is generous.


export MIDDLEWARE_HOME=/u02/appdevl/devdisco/Middleware

export DOMAIN_HOME=$MIDDLEWARE_HOME/user_projects/domains/ClassicDomain

export WL_HOME=$MIDDLEWARE_HOME/wlserver_10.3

export ORACLE_HOME=/u02/appdevl/devdisco/Middleware/as_1

xport ORACLE_INSTANCE=/u02/appdevl/devdisco/Middleware/asinst_1

rm -rf nohup.out

rm -rf /tmp/wls_start.log

rm -rf /tmp/start_nodemanager.log

rm -rf /tmp/start_mgdwls.log

echo “Ensure NO processes related to disco 11g are running or this will fail”

nohup $DOMAIN_HOME/bin/ > /tmp/wls_start.log &

nohup $WL_HOME/server/bin/ > /tmp/start_nodemanager.log &

echo “sleeping”

sleep 60

nohup $DOMAIN_HOME/bin/ WLS_DISCO t3://(server.domain):7001 > /tmp/start_mgdwls.log &

echo “sleeping”

sleep 60

$ORACLE_INSTANCE/bin/opmnctl startall

$ORACLE_INSTANCE/bin/opmnctl status

echo “If Discoverer doesn’t start properly, login to http://(server.domain):7001/console”

echo “From the home page, click servers (Under Environment), then the control tab.  Check WLS_DISCO then click the start button below the checkbox”

# Shutdown


export MIDDLEWARE_HOME=/u02/appdevl/devdisco/Middleware

export DOMAIN_HOME=$MIDDLEWARE_HOME/user_projects/domains/ClassicDomain

export WL_HOME=$MIDDLEWARE_HOME/wlserver_10.3

export ORACLE_HOME=/u02/appdevl/devdisco/Middleware/as_1

export ORACLE_INSTANCE=/u02/appdevl/devdisco/Middleware/asinst_1

$ORACLE_INSTANCE/bin/opmnctl stopall

$ORACLE_HOME/opmn/bin/opmnctl status

# stop the discoverer server

$DOMAIN_HOME/bin/ WLS_DISCO t3://(server.domain):7001 weblogic password

# stop the weblogic admin server



killall nmz

echo “There’s probably still 1 disco process running – ps -ef|grep jrockit and kill it (java)”echo “It’s probably pid:”ps -ef|grep jrockit|cut -c10-15

Step 7 CPU (optional)

I had no problem applying CPU0111 (patch 10233533), though my ORACLE_HOME required a more recent Opatch (patch 6880880) version than the installer provided.

Step 8 Navigation Reference (Default)

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

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

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

Weblogic Marketing Propoganda: http://hostname:7001



  1. […]  When I was completely done, two issues.  First, the webcache file permissions were hosed again ( Step 5 Number 2) and my passwords were no longer hard coded in the startup and shutdown scripts […]

    Pingback by Discoverer certified with 11i « Kevin Kempf's Blog — February 23, 2011 @ 2:11 pm

  2. Thanks for the blog on this. Do you know if having DBA privilages is required to complete the install of Discoverer 11g 11.1.3? We do not get these privliges from our DBA group. Our support stack includes Middleware but cannot gain DBA access. Thanks!

    Comment by Andrew — May 10, 2011 @ 8:33 am

    • You will definitely need sys access to create the new schemas in the database, so yes, DBA privs are required. In addition, you will need pretty thorough operating system access as well (at least on Linux!)

      Comment by kkempf — May 10, 2011 @ 8:53 am

  3. Hi Kemp,

    i have installed Fusion middleware Discoverer 11g ina new sandbox

    according to me everything went fine .

    but when i am creating a connection in Discoverer plus. i am facing the ORA-12154.

    i have taken the tnsnames.ora and sqlnet.ora file from our DBA’s ,so they cant be wrong .

    could you please let me know what should i do to eliminate the error as i need to implement the same in the production

    Comment by kanna — May 10, 2011 @ 2:13 pm

    • There’s so many variables involved, and you didn’t specify how far you got or what screen you were on when you received the error. ORA-12154 is tns related; I’m assuming that you already checked to ensure that the tnsnames.ora and sqlnet.ora files on the discoverer server are in the right spot?

      Comment by kkempf — May 10, 2011 @ 7:43 pm

  4. Hey, worked through my issues. Appreciate the write-up. Worked great!

    Comment by Andrew — May 11, 2011 @ 5:10 pm

  5. Hi Kemp,

    Installation of FMW completed successfully i fallowed the steps as fallows:

    1.Installed Web logic server 10.3.5
    2.created new users and table spaces using RCU
    3.Installed FMW with install software only option
    4.Installed FWM and configured
    5.Copied dbc and tnsnames.ora files from EBS 11i to BI Discoverer
    6.Applied the AD patch 9393984
    7.Upgrade from earlier versions of Discoverer End User Layers to Discoverer 11g

    in the above command i entered the user nameAPPS) which is owned by 4i EUL tables and it got completed

    8.updated application xml file and ran auto config also updated Profile options based on metalink note:1073963.1
    9.copied $AU_TOP/discover directory including language specific *.eex files to 11g Discover under /ORACLE_HOME/discoverer and ran the import process using the script
    10.Refresh the Discoverer 11.1.1 End User Layer using the script

    After this when i tried to access with user name which i was created using RCU while installation getting error message “Connection error EUL tables are not accessible by the provided username or schema”.

    My question is by using which username i can access work books, using discoverer/viewer URL Please suggest me?


    Comment by Shine — September 11, 2011 @ 4:09 am

    • Regrettably, my experience with upgrading EULs is usually a roll of the dice (especially from 4!). I think you need to contact Oracle support; if it’s integrated with 11i/R12 you need to use a username who runs reports. Think responsibility based users, not database users.

      I think before you call Oracle, you might want to gather more information such as:

      Is the Weblogic Server running?
      Weblogic Marketing Propoganda: http://hostname:7001

      Is the Weblogic Server console running?
      Weblogic Server Administration: http://hostname:7001/console

      Are you sure you have your ports right? (you can use netstat -anb on Linux)

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

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

      • Hi Kemp,

        All the URL’s which you mentioned are working with out any issues,also i am able to login with APPS User and EUL Owned tables user.Thanks alot for your Reply.

        The Blog is very usefull for me to install Oracle FMW.Thank you very much once again


        Comment by Shine — September 13, 2011 @ 1:47 am

  6. Hi Kemp,

    I hope you can help me. It seems to me you are professional in the Discoverer install and configuration.

    I installed the Discoverer version onto a SLES11 64 bit platform and used the JDK v1.6.26_x64. Our users want to use the Plus with Hungarian language, but the special Hungarian charters (áéűő etc.) appear erroneously – in the menu and in all texts boxes (e.g.: Súgó – S?g? or Cím – C?m) – all special charters replaced with “?” question mark.

    Do you have any idea what is wrong and where should can I change any config parameter for the good result?

    Thanks in advance for your help.


    Comment by András — September 15, 2011 @ 1:54 am

    • Unfortunately I have no experience with the characterset question you are asking in regards to discoverer. I’d recommend opening an SR with Oracle support.

      Comment by kkempf — September 15, 2011 @ 7:10 am

      • Hi Kemp,

        In the meantime I found the solution.

        I have to change the _res.jar file in the ORACLE_HOME/discoverer/plus_files/resources directory with the same file from windows install package, and finally download again the thin client to your computer. Because the linux and the windows jar files use different coding during the compile…


        Comment by András — September 19, 2011 @ 9:52 am

  7. Has anyone run into the issue of running Discoverer 11i alongside Discoverer 10g (R2) on the same server? I am receiving CORBA connection errors and the Oracle technician said it is not recommended to run them at the same time on the same server. In my QA environment have tried installing the 11i version while 10 is running as well as running with the staticports.ini file configured. Still it seems there is some issue. When I have our DEV environment running the same install on a server which does not have 10g installed it works without issue. I have access to only one production server for our BI products and need to keep 10g running until 11i is ready for production users. Without a working install in our QA enviornment I can’t perform my production install.

    If anyone can provide direction on these two version co-habitating please chime in.

    Comment by Andrew — October 8, 2011 @ 2:18 pm

  8. Hi,

    We are going to upgrade Oracle database 10g to 11g R2 and for that very reason we want to migrade our oracle discovere 10g to oracle discoverer 11g.

    Here I read all the post and find out the installation procedure of FMW 11g but I still have one question.Once we create new schema using RCU for oracle discovere 11g , then how can we migrate our old schema of oracle discovere 10g in to new oracle discovere 11g schema created by RCU.?

    Your help would eb much appreciated.


    Comment by Ashwani — November 10, 2011 @ 11:34 am

    • The new schemas created by the RCU are SID_DISCOVERER and SID_DISCOVERER_PS. It detected and “upgraded” my old schema automatically as this was an “in place” upgrade on my database so it was “still” EUL_US. In other words, in Discoverer 10g, my end user layer was called EUL_US and held all my important report data and metadata. Since I was upgrading and pointing to the same database, it didn’t change where my EUL was: it was still called EUL_US after the upgrade to 11g, it just happened to have these other 2 schemas that it needed.

      Comment by kkempf — November 10, 2011 @ 12:47 pm

  9. Hi,

    Thanks for your prompt response.

    Here in my case, we are moving to new database and new application server together.We have one schema for oracle discoverer 10g on Oracle database 10g.Now we will new schema through RCU on oralc database 11g R2 for Oracle discoverer 11g.

    So logically I don’t understand how can it automatically detect to old schema without any reference of old database.?Can you please suggest me something for described condition in which I am fallling?

    Also for the EUL , Can we use export and import wizard for migration in Oracle discoverer 11g?

    Thanks in advance.


    Comment by Ashwani — November 10, 2011 @ 3:05 pm

    • Obviously I didn’t do what you’re asking, so my response here is speculation. But it seems logical to me, that even when you migrate to a new server and upgrade, that you’re migrating your datafiles/tablespaces and upgrading your database right? So EUL_US (or whatever you called your Discoverer 10g End User Layer schema) will be there for RCU to detect. If you’re not bringing that schema with you on your upgrade… well no, then RCU will just install the framework and you have to rebuild your EUL and reports. Maybe you can use Discoverer tools to export and import the EUL and reports. I don’t know. Even if you could, that would not be the route I would take.

      Comment by kkempf — November 10, 2011 @ 3:43 pm

  10. Yes, we are migrating whole database from 10g to 11g with the schema for discoverer(FREMS_EUL), then how can RCU detect this schema to create new schema.?

    Can you please help me in this to understand the process, it would be very much appreciated.?


    Comment by Ashwani — November 10, 2011 @ 4:26 pm

  11. Does RCU create new schemas and also detect old schema(FREMS_EUL) for discoverer to upgrade it simultaneously?

    Comment by Ashwani — November 10, 2011 @ 4:28 pm

  12. HI Kevin,

    I also have few question and I hope you would like to share your experience with us.

    1) Did you use same tablespaces names for Default and Temp tablespace that you were using for Discoverer 10g End User Layer schema?

    2) You mentioned that RCU creates 2 schemas SID_DISCOVERER and SID_DISCOVERER_PS, which one should we use for installation of discoveer?

    3) How can we verify that is automatically upgrade the our old Discoverer 10g End User Layer schema for dicoverer 11g?

    Comment by Ashwani — November 10, 2011 @ 5:09 pm

    • 1) My Discoverer End User Layer (EUL_US schema) resides in my 11i database. So I had the same everything. My database was 100% unchanged when I started the upgrade.
      2) Discoverer creates those schemas and populates them with metadata. Your only concern will be pointing the RCU at FREMS_EUL, which it should upgrade “in place” to 11g.
      3) Do it in a TEST environment first, and verify your process. This will make your question 2 much clearer as well.

      Comment by kkempf — November 10, 2011 @ 8:45 pm

  13. Hi Kevin,

    Thanks for your very suggestive response but I am still confused in how can I pointing the RCU at FREMS_EUL?

    If I am not going on wrong track then, when we install discoverer or configure discovere then it asks about the discoverer schema , should we use there FREMS_EUL or the schema created by RCU?

    I would also like to know when you created schema through RCU ,did it automatically detects default and temp tablespace names or you manually assigned those tablespace name that you were using for EUL_US schema?

    Please suggest me something.


    Comment by Ashwani — November 11, 2011 @ 10:05 am

  14. Hi Kevin,

    It would be very much appreicated if you could follow up with me in giving answers of my question.I am neophyte for discoverer upgrade and for that very reason you might find some of my questions not very much considerable but I am trying my best to learn whole procedure of this upgrade with the help of you.

    1) Two Schemas is created by RCU are being used in installation of discoverer but how they detect our EUL_US schema that we were using for 10g?

    2) Did you use same tablespaces name while created schemas by RCS?

    Thanks in advance.


    Comment by Ashwani — November 14, 2011 @ 12:57 pm

    • I’m trying to figure out the best way to answer your question. In truth, I think your best bet is to perform this upgrade in a non-production environment and the answers will be self-evident; I did this upgrade over a year ago and I simply don’t recall exactly what the RCU did. I can say that I didn’t sweat the questions you’re asking, I simply “followed the bouncing ball” of the RCU and it made logical decisions. In the end, I wouldn’t consider myself a Discoverer expert by any means and I’d recommend opening an SR with Oracle if you have further questions.

      1. In my case, RCU either autodetected or I had to tell it where my existing (Disco 10g) repository was. It may default to EUL_US, I simply don’t recall. In addition to upgrading the existing EUL, it created the two new schemas. I don’t know what’s in them, and frankly, it’s not relevant. They’re simply required for Discoverer 11g and should not be messed with, in my opinion.

      2. I’m not sure I understand your question. You might check out my earlier post here

      Comment by kkempf — November 14, 2011 @ 7:22 pm

  15. Hi Kevin,

    Thanks dear for your recommendation and whatever you could better suggest me.

    I think I have to play with it to make it possible.


    Comment by Ashwani — November 15, 2011 @ 9:19 am

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Blog at