Kevin Kempf's Blog

January 13, 2011

No more OUI/GUI Agent install for 11.1 on Windows

Filed under: 11g, Enterprise Manager, Windows 2008 — kkempf @ 9:57 am

Oil and Water

Looks like a great Enterprise Solution!

Windows Server and Oracle databases go together like oil and water.  Everything about administering an Oracle database on Windows is annoying.  From the command line interface to starting services before I can start a database it fails in many ways.  Yet all of this is just my opinion.  What I found out yesterday is a new, substantial fact and a good reason to hate Windows even more.

Server 2008

We have a non-Oracle application which has an Oracle back end database.  It happens to be certified (only) on Windows.  It’s the only Windows RDBMS server I have to administer, so I suppose I should be grateful.  Still, as a result of an upgrade, we were able to move it to 64-bit Oracle 11.1 for Windows Server 2008.  All in all, it was a nice refresh/update of the technology stack as it had previously been running 32-bit Oracle 10.2 on Windows Server 2003.

Agent Woes

So I go to pull the 11.1 agent from OTN/Metalink/MOS/Oracle/World’s Slowest Support Site and am humored to find it’s now 500+ MB!  Seriously?  It’s an agent!  Back in the dark ages, under 9i, I swear they were like 40mb.    I put the thing in my $OH/sysman/agent_download/11.1.0.1.0 directory, and sure enough, it shows up as an option under deployments in EM.  I go through the process outlined here to push the install, and it fails because SSH isn’t running on the Windows host.  Who runs SSH on Windows?  I know it’s technically possible, but seriously, who expects that?   Needless to say, I’m annoyed, but I’m not about to go try to get SSH running on a Windows server I don’t want to administer.  So I push the agent download .zip file to the host and run the installer (tried both setup.exe and installer.exe) only to get this error:

Obviously

Time to contact support

I actually did try to create a response file and run it from the Win 2008 CLI.  It failed for an unknown reason, telling me to check the logs.  Of course, the logs weren’t in the directory I was in, and I was beyond annoyed at this point. Reluctantly, I opened an SR to see what I was doing wrong with the GUI install.  It turns out, nothing.  The analyst confirmed that in 11.1, the OUI/GUI installer has been removed.

One step forward, two steps back

Step back and ask yourself, is this a step forward?  Honestly, how many people run SSH on a Windows server?  My only other recourse is to mock up some cryptic response file (in Windows, no less, with notepad!) and then use a command line interface to manually install the agent (silently!).  Seriously, Oracle, this is just plain stupid.  There’s like 4 parameters required in the old GUI: where do you want to install it, what host and port is Grid Control installed on, and what’s the dbsnmp password?  Why not just leave this in the GUI?  Whoever made this call has obviously never worked in the real world.

My Solution

After berating the analyst, I installed the 10.2.0.5 agent (via the OUI GUI) to monitor my 11.1 RDBMS.  Makes more sense than Oracle’s stance.

Advertisements

5 Comments

  1. Hi Kevin!
    I do agree on you that it is stupid to REMOVE a feature, ie. installing MA using GUI – for installing one/few servers this is nicer than having to setup “mass deployment” procedures 😉

    I’ve managed to install 11.1 MA on Windows 2008 using this response file:

    ####################################################################
    ## Copyright(c) Oracle Corporation 1998,2007. All rights reserved.##
    ## ##
    ## Specify values for the variables listed below to customize ##
    ## your installation. ##
    ## ##
    ## Each variable is associated with a comment. The comment ##
    ## identifies the variable type. ##
    ## ##
    ## Please specify the values in the following format: ##
    ## ##
    ## Type Example ##
    ## String “Sample Value” ##
    ## Boolean True or False ##
    ## Number 1000 ##
    ## StringList {“String value 1″,”String Value 2”} ##
    ## ##
    ## The values that are given as need to be ##
    ## specified for a silent installation to be successful. ##
    ## ##
    ## ##
    ## This response file is generated by Oracle Software ##
    ## Packager. ##
    ####################################################################

    RESPONSEFILE_VERSION=2.2.1.0.0

    ####################################################################
    ## Standard Oracle Universal Installer variables ##
    ####################################################################

    #——————————————————————————-
    #TOPLEVEL_COMPONENT: The top level component to be installed in the
    # current session.Value should contain only one of the following available
    # choices.The choices are of the form Internal Name, Version : External name.
    # Please use the internal name and version while specifying the value.
    # oracle.sysman.top.agent, 10.3.0.0.0 : Oracle Management Agent 10.3.0.0.0
    # Example: TOPLEVEL_COMPONENT = {“oracle.sysman.top.agent”,”10.3.0.0.0″}
    #——————————————————————————-
    TOPLEVEL_COMPONENT={“oracle.sysman.top.agent”,”11.1.0.1.0″}

    #——————————————————————————-
    #DEINSTALL_LIST: List of components to be deinstalled during a
    # deinstall session.The following choices are available. The value should
    # contain only one of these choices.The choices are of the form
    # Internal Name, Version : External name. Please use the internal name and
    # version while specifying the value.
    # oracle.sysman.top.agent, 10.2.0.0.0 : Oracle Management Agent 10.2.0.0.0
    #——————————————————————————-
    DEINSTALL_LIST={“oracle.sysman.top.agent”,”11.1.0.1.0″}

    #——————————————————————————-
    #COMPONENT_LANGUAGES: Languages in which the components will be installed.
    # The following choices are available. The value should contain only one of
    # these choices.The choices are of the form Internal Name : External name.
    # Please use the internal name while specifying the value.
    # en, : English
    # de, : German
    # es, : Latin American Spanish
    # es_MX, : Mexican Spanish
    # es_ES, : Spanish
    # fr, : French
    # fr_CA, : Canadian French
    # it, : Italian
    # iw, : Hebrew
    # ja, : Japanese
    # ko, : Korean
    # pt_BR, : Brazilian Portuguese
    # zh_CN, : Simplified Chinese
    # zh_TW, : Traditional Chinese
    #Example: COMPONENT_LANGUAGES = {“en”}
    #——————————————————————————-
    COMPONENT_LANGUAGES={“en”}

    ####################################################################
    ## Variables for Enterprise Manager Agent installation ##
    ####################################################################
    #
    # Notes on Installing with a Secure Management Service
    #
    # If you are configuring the agent to communicate with a Management Service
    # which is running in secure mode, you will need to specify the agent
    # password. For security reasons, that password should not be recorded in
    # a file.
    #
    # You will also need to change the OPTIONAL_CONFIG_TOOLS variable (below)
    # to execute the agentsecure config tool in addition to the agentca tool.
    #
    #——————————————————————————-
    #OPTIONAL_CONFIG_TOOLS: List of optional config tools to be launched.
    #Example: OPTIONAL_CONFIG_TOOLS = {“agentca”}
    #——————————————————————————-
    OPTIONAL_CONFIG_TOOLS={“agentca”,”agentsecure”}

    #——————————————————————————-
    #s_OMSHost: OMS host info required to connect to OMS
    #s_OMSPort: OMS port info required to connect to OMS
    #AGENT_REGISTRATION_PASSWORD: Agent Registration Password needed to
    # establish a secure connection to the OMS.
    #——————————————————————————-
    s_OMSHost=oraclegrid.mydomain.com
    s_OMSPort=4889
    AGENT_REGISTRATION_PASSWORD=

    #——————————————————————————-
    #b_doAgentConfig: whether to run the Agent Configuration Assistant
    #b_doDiscovery:whether to perform target discovery in the post-install phase
    #b_startAgent:whether to start the agent after the installation
    #b_secureOMS: “Since the OMS is always Secure, the agent Which gets installed
    # should be secure, hence setting the value to true”
    #s_encrSecurePwd:”Since the OMS is always Secure, the agent Which gets installed
    # should be secured, hence setting the value to OMS encrypted Secure Password”
    #BaseDir: Complete path of the Oracle Home.
    #——————————————————————————-
    b_doAgentConfig=true
    b_doDiscovery=true
    b_startAgent=true
    b_secureOMS=true
    BASEDIR=”E:\Oracle\Product\Grid”

    #——————————————————————————-
    #s_agentServiceName:Sets the agent Service Name and this variable can be
    # used to overrite the agent service name calculated by the install. This is
    # required for only Windows.
    #Example:
    # s_agentServiceName = “Oracleagent10gAgent” ; default value
    # s_agentServiceName = “GridAgent” ; User specified value
    #——————————————————————————-
    #s_agentServiceName=””

    #################################################################################
    #Inputs for Oracle Configuration Manager
    #################################################################################
    #——————————————————————————-
    #SECURITY_UPDATES_VIA_MYORACLESUPPORT: Whether security updates are reqi-
    # uired via My Oracle Support
    #DECLINE_SECURITY_UPDATES: Whether security updates should be declined.
    #MYORACLESUPPORT_USERNAME & MYORACLESUPPORT_PASSWORD: User name and passw-
    # ord for My Oracle Support access, these will be effected only when SECU-
    # RITY_UPDATES_VIA_MYORACLESUPPORT=true
    #——————————————————————————-
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
    DECLINE_SECURITY_UPDATES=true
    MYORACLESUPPORT_USERNAME=
    MYORACLESUPPORT_PASSWORD=

    ################################################################################
    #PROXY DETAILS FOR SECURITY UPDATES/ SOFTWARE UPDATES
    ################################################################################
    #——————————————————————————-
    #PROXY_USER: User name for proxy access.
    #PROXY_PWD: Password for proxy access.
    #PROXY_HOST: Server providing proxy access.
    #PROXY_PORT: Port for proxy access.
    #——————————————————————————
    PROXY_USER=
    PROXY_PWD=
    PROXY_HOST=
    PROXY_PORT=

    #——————————————————————————-
    #COLLECTOR_RESPONSE_FILE:
    #——————————————————————————-
    COLLECTOR_RESPONSE_FILE=

    ####################################################################################
    #Please Don’t change the values of these variables
    ####################################################################################
    #——————————————————————————-
    #FROM_LOCATION: Complete path to the products.jar.
    #b_upgrade: “whether it is Upgrade or not”
    #b_silentInstall: The user should not change this value
    #——————————————————————————-
    FROM_LOCATION=F:\Oracle_Installationsfiler\MA\Windows_X64_Grid_Control_agent_download_11_1_0_1_0\windows_x64\agent\stage\products.xml
    b_upgrade=false
    b_silentInstall=true

    #——————————————————————————-
    #s_installType:Type of Enterprise Manager install
    #INSTALL_TYPE:Installation type of the component.
    #b_doValidation:
    #——————————————————————————
    oracle.sysman.top.agent:s_installType=”AGENT”
    INSTALL_TYPE=”Complete”
    oracle.sysman.ccr:b_doValidation=false

    OUI_HOSTNAME=oracle1.mydomain.com
    ORACLE_AGENT_HOME_LOCATION=E:\Oracle\Product\Grid
    OMS_HOST=oraclegrid.mydomain.com
    OMS_PORT=4889

    ———————————–
    NOTICE, some parameters in the beginning of the file too…

    I then installed from CLI using something like this:
    cd F:\Oracle_Installationsfiler\MA\Windows_X64_Grid_Control_agent_download_11_1_0_1_0\windows_x64\agent

    .\setup.exe -silent -responsefile F:\Oracle_Installationsfiler\MA\Windows_X64_Grid_Control_agent_download_11_1_0_1_0\MA-oracle1.rsp

    Cheers
    Lars Bo

    Comment by Lars Bo — March 24, 2011 @ 6:26 am

    • Thanks for the response file. This should prove helpful in the future

      Comment by kkempf — March 24, 2011 @ 7:08 am

  2. This is going to sound bizarre – but I had exactly the same problem. Fixed it by swapping the arguments around!

    setup.exe -silent -responseFile D:\additional_agent.rsp was failing, but:

    setup.exe -responseFile D:\additional_agent.rsp -silent

    was fine!

    I also needed to change the following two settings in the response file:
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=FALSE
    DECLINE_SECURITY_UPDATES=TRUE

    Finally – doublecheck your downloads from OTN. The first time I did it, there was no SETUP.EXE file!

    Comment by Gary — November 18, 2011 @ 10:41 am

    • Hi,

      I had the same problem!
      first trial, i run setup.exe -silent -responseFile …\additional_agent.rsp
      second trial, i run setup.exe -silent -responseFile …\additional_agent.rsp
      And it works!!!!
      The difference is :
      1st trial responseFile
      2nd trial responsefile!!!!!

      Comment by Tahar A. — December 6, 2011 @ 11:32 am

      • In the end, I suppose my point is that I don’t WANT to use a response file. It’s Windows: The OS that was made for interactive GUI’s. Why would they make our lives more complicated, by removing a feature we obviously already were all using? I’m still running a 10g agent on my handful of Windows servers… where the installer is still graphical!

        Comment by kkempf — December 6, 2011 @ 11:43 am


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.