Kevin Kempf's Blog

July 16, 2010

Starting and stopping Discoverer 11g

Filed under: 11i, Discoverer, Support — kkempf @ 9:20 am

I’ve learned a few things about Discoverer 11g in the past few weeks.

  • Apparently, the model for Discoverer 11g on Linux is: start it once from the installer and pray it never shuts down and that you never need to restart the server.
  • Weblogic people at support don’t have any idea what Discoverer is, but they’re happy to help you troubleshoot the weblogic pieces.  In other words, nobody seems willing to embrace the whole product.  conFusion has arrived!
  • The most difficult part of a Discoverer 11g upgrade/install is figuring out how to start and stop the server

Support Woes

Document 1099996.1 explains the gist of starting/stopping Discoverer 11g on linux (via command prompt).  Not only did the Weblogic analyst I had not know about Discoverer 11g, he was also unfamiliar with Linux, and was apparently helping me troubleshoot my problems via a Windows install of Weblogic.  Seems like not such a great fit.  He was further confounded by the fact that a web conference was unavailable, as my system (OS & browser) failed the checks on their site.

Guess I’ll figure it out myself

At some point in most SRs, it becomes clear that if I really want the solution, it won’t be coming from my analyst.  If I manage to figure it out, I’ll keep the SR open to see if my analyst ever does.  Usually I get annoyed with their irrelevant questions and close the SR as “Determined solution myself”.  Somehow, those SRs are always “Hard Closed” by the analyst as “Solution Provided”.   This is one of those cases.

The gist of the problem starting and stopping all the pieces of Discoverer 11g on Linux is that there’s no good documentation.  Through trial and error, I got this thing working.  There were major problems:

  • The scripts laid out in doc 1099996.1 are not like normal Oracle scripts which automatically run in the background.  They have to be run nohup (no hangup) and with & (background).  This isn’t a problem per se, except some of them are interactive.  Meaning some of these scripts ask for things like username and password.  This doesn’t work nohup’d and backgrounded.
  • There’s too many scripts.  4 scripts to start discoverer; in 10g there were 2 (opmnctl startall and emctl start iasconsole).  It’s a sorry step in the wrong direction.
  • For whatever reason, there’s a t3 in front of the URL argument passed to many of the scripts.  I have no idea why, but it’s required.
  • /yourpath/Middleware/user_projects/domains/ClassicDomain/bin/startManagedWebLogic.sh requires you to hard code values in their script.  Yes, you need to vi the file and put your username and password in the script under WLS_USER and WLS_PW or it will not start except in the foreground on your screen (interactively).  If you do this, you cannot ever close that screen, or Discoverer stops.
    • WLS_USER=”weblogic”
    • WLS_PW=”yourpassword
    • To add insult to injury, the script exports these values, meaning they’re available variables to the host.

Startdisco.sh

#!/bin/bash

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

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/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=disco11g > /tmp/wls_start.log &

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

echo “sleeping”

sleep 60

nohup $DOMAIN_HOME/bin/startManagedWebLogic.sh 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”

Stopdisco.sh

#!/bin/bash
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/stopManagedWebLogic.sh WLS_DISCO t3://(server.domain):7001 weblogic disco11g
# stop the weblogic admin server
$DOMAIN_HOME/bin/stopWebLogic.sh
killall startNodeManager.sh
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
Advertisements

5 Comments

  1. Good information..helped a lot..keep it up.
    Thanks
    Raghu

    Comment by Raghu — December 22, 2010 @ 11:27 pm

  2. Thanks for start and stop scripts…works fine for me.

    Thanks
    Raghu

    Comment by Raghu — April 16, 2011 @ 1:18 am

    • Glad to hear you found them of use.

      Comment by kkempf — April 21, 2011 @ 1:13 pm

  3. I may be a few years late, but wanted you to know you just saved my neck, or at least my Discoverer 11g installation. I don’t feel so alone anymore. This has been the worst installation I’ve ever done. The statement about having to re-install WebLogic and Discoverer to start it up was so true. Thank you!

    Comment by Chris — February 14, 2012 @ 1:42 pm

    • Hey it’s always good to hear I helped someone with my ramblings here. Discoverer 11g installation was a train wreck.

      Comment by kkempf — February 14, 2012 @ 2:15 pm


RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Blog at WordPress.com.