Silent Installation of EM Cloud Control 12c

Silent installation always attracts by its simplicity and power. And the new release 2 of EM 12c proves it by making the installation
smooth and straightforward. RDBMS software, database creation, and the installation of OMS server can be done using command prompt. After the installation, you get access to Web console and continue on with EM configuration.

But before starting the installation, you must make sure that all prerequisites are satisfied to avoid any unpredictable errors during the process: install rpms, configure kernel, modify hosts file, etc.

Let’s start with the silent installation of RDBMS (11.2.0.3 Linux 64-bit). Create a copy of response file and modify it to adjust to the environment or to run with the following variables:

./runInstaller -silent -responseFile ... -showProgress \
oracle.install.option=INSTALL_DB_SWONLY \
UNIX_GROUP_NAME=oinstall \
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1 \
ORACLE_BASE=/u01/app/oracle \
oracle.install.db.InstallEdition=EE \
oracle.install.db.DBA_GROUP=dba \
oracle.install.db.OPER_GROUP=oper \
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false \
DECLINE_SECURITY_UPDATES=true \
oracle.installer.autoupdates.option=SKIP_UPDATES

After successful a installation, it’s time to create a database using dbca in silent mode:

./dbca -silent -createDatabase -gdbName emrep -templateName General_Purpose.dbc \
-emConfiguration none -datafileDestination /u01/oradata -redoLogFileSize 600 \
-sysPassword ...-systemPassword ... -storageType FS \
-initParams filesystemio_options=setall,job_queue_processes=20,log_buffer=10485760,\
open_cursors=300,processes=600,session_cached_cursors=200,shared_pool_size=800m \
-totalMemory 4096

The created database will have SYSMAN account, which should be deleted:

alter user SYSMAN identified by ... account unlock;

./emca -deconfig dbcontrol db -repos drop -silent \
-SYS_PWD … -SYSMAN_PWD … -SID emrep -PORT …

Now it is time to execute the prerequisite utility to see if everything is ready for the OMS installation:

./emprereqkit -executionType install \
-prerequisiteXMLLoc /home/oracle/install/em/install/requisites/list \
-dbHost ... -dbPort ... -dbSid emrep -dbUser SYS -dbPassword ... -dbRole sysdba -runPrerequisites

It will most likely report about scheduled jobs to gather database statistics, which is enabled as auto task but can be turned off as:

exec DBMS_AUTO_TASK_ADMIN.DISABLE(client_name => 'auto optimizer stats collection', operation => NULL, window_name => NULL);

I would also turn off other jobs:

exec DBMS_AUTO_TASK_ADMIN.DISABLE(client_name => 'auto space advisor', operation => NULL, window_name => NULL);
exec DBMS_AUTO_TASK_ADMIN.DISABLE(client_name => 'sql tuning advisor', operation => NULL, window_name => NULL);

It can be worth it to run a prerequisites check once again to see if all requirements satisfied. When database is ready for repository and the server for OMS satisfies all requirements, it’s time to define variables for installation. Due to their large number, it would be definitely
simpler to modify a copy of response file and use it for installation.
However, nothing stops you to put them as parameters in command line:

./runInstaller -silent -responseFile /home/oracle/install/em/response/new_install.rsp \
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false \
DECLINE_SECURITY_UPDATES=true \
INSTALL_UPDATES_SELECTION=skip \
ORACLE_MIDDLEWARE_HOME_LOCATION=/u01/app/oracle/product/em12c \
AGENT_BASE_DIR=/u01/app/oracle/product/agent12c \
WLS_ADMIN_SERVER_PASSWORD=... \
WLS_ADMIN_SERVER_CONFIRM_PASSWORD=... \
NODE_MANAGER_PASSWORD=... \
NODE_MANAGER_CONFIRM_PASSWORD=... \
ORACLE_INSTANCE_HOME_LOCATION=/u01/app/oracle/product/em12c/gc_inst \
DATABASE_HOSTNAME="s1" \
LISTENER_PORT=... \
SERVICENAME_OR_SID="emrep" \
SYS_PASSWORD=... \
SYSMAN_PASSWORD=... \
SYSMAN_CONFIRM_PASSWORD=... \
DEPLOYMENT_SIZE="SMALL" \
MANAGEMENT_TABLESPACE_LOCATION="/u01/oradata/emrep/mgmt.dbf" \
CONFIGURATION_DATA_TABLESPACE_LOCATION="/u01/oradata/emrep/mgmt_ecm_depot1.dbf" \
JVM_DIAGNOSTICS_TABLESPACE_LOCATION="/u01/oradata/emrep/mgmt_ad4j.dbf" \
AGENT_REGISTRATION_PASSWORD=... \
AGENT_REGISTRATION_CONFIRM_PASSWORD=...

At the end of the installation, you will be required to execute the allroot.sh script. OMS will start, so you can connect to the Web Console of EM. However, if something goes wrong, I find it easier to recreate the database and repeat the installation. Several misconfigurations caused me to do it. They were /etc/hosts file and not increased limits for oracle in /etc/security/limits.conf.

Have a good day!