I was recently asked to come up with a process for a silent install for EM12c.
My initial thoughts were that’s going to be difficult!
But now that I’ve actually done it (several times!) I’m happy to say how easy it is.
Why might one want to do a silent install? Well working on customer sites there’s not always the option of opening up an X-Windows or VNC session. Also working through install screens can be time consuming and can potentially result in a seat to keyboard interface error. Scripting a silent install also means you have an easily repeatable process.
Cloud Control 18.104.22.168 was released on June 16th 2015. It’s worth pointing out this is the terminal release of EM12c and contains a number of new features particularly around Hybrid Cloud Management. On that subject I’d heartily recommend checking out the blog blitz my colleague Phil is doing on this.
Anyway back to the silent install, let’s assume that you’ve covered off all of the prereqs and you have a database ready to host the OEM repository.
The Cloud Control software should be downloaded and staged on the server. All the zipfiles must be unzipped to the same directory.
The next stage would be to run the EMPrereqKit tool to confirm the database meets all of the prerequisites for hosting the EM repository. The tool is run as part of the install but it’s better to correct any issues up front.
To run the tool execute the following (logfiles will be generated in your current directory):
<STAGEDIR>/install/requisites/bin/emprereqkit -executionType install -prerequisiteXMLRootDir <STAGEDIR>/install/requisites/list -connectString “(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<REPOSITORY_DB_HOST>)(PORT=<PORT>)))(CONNECT_DATA=(SID=<SID>)))” -dbUser SYS -dbPassword <PASSWORD> -dbRole sysdba -reposUser SYSMAN -runPrerequisites -runCorrectiveActions
Some failures can be corrected via the runCorrectiveActions flag.
For more details on any failures consult ./prerequisiteResults/log/LATEST/emprereqkit.out
All failures should be addressed prior to commencing the installation of Cloud Control.
So on to the silent install. There are template response files contained within the software directories in <STAGEDIR>/response. The response file template we need is new_install.rsp
If you were going for a silent upgrade then have a look at upgrade.rsp
We’re also going to use staticports.ini to configure the ports as we want them.
The default response file contains a number of comments, instructions etc. but I’m going to cut these out (via an egrep -v ^’(#|$)’ new_install.rsp) for ease of reading. This gives me, with my amended parameters:
You would of course need to double check all of these parameters tie in with your environment. I’m also only installing the default plugins here but you can add additional ones in the PLUGIN_SELECTION variable as needed.
And not forgetting our staticports.ini:
Admin Server Http SSL Port=7101
Managed Server Http Port=7201
Managed Server Http SSL Port=7301
Enterprise Manager Upload Http Port=4889
Enterprise Manager Upload Http SSL Port=1159
Enterprise Manager Central Console Http Port=7788
Enterprise Manager Central Console Http SSL Port=7799
Node Manager Http SSL Port=7401
Oracle Management Agent Port=3872
So now we can run the silent install. Passwords can be put in the response file but I prefer not to do this for security reasons. Instead I will pass all of the password variables when executing the runInstaller command.
A couple of preflight checks to do before execution:
echo $ORACLE_HOME – Should be null
echo $PATH – Should not include any Oracle Home locations
Then the runInstaller can be run with the -silent option as the oracle software owner as follows:
<SW_STAGING_LOC>/install/runInstaller -silent \
-responseFile /home/oracle/my_new_install.rsp \
On execution this will run in the background but continue to stream output to stdout, as well as logfiles in /tmp and your oraInventory location.
Once completed you will need to run the allroot.sh script as root.
And that’s it!
Well almost…now you would want to backup your emkey and emconfig, configure BI Publisher integration and apply any recommended patches.
And of course start adding your targets!