Installing OEM 13.4 [Silent Install] – Part 3 : Postinstallation Tasks After Installing an Enterprise Manager System

As this is the first Oracle product we just installed on the host, we have to run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home. After successful completion of silent install.

1. As root user run the following script

sh ${MW_HOME}/orainstRoot.sh
sh ${MW_HOME}/allroot.sh

2. Verifying the installation

i. Checking if OMS is up :

$<ORACLE_HOME>/bin/emctl status oms

ii. Checking Management Agent status

$<AGENT_HOME>/bin/emctl status agent

iii. Uploading EMD

$<AGENT_HOME>/bin/emctl upload agent

iv. If the repository prerequisites had failed, and if you had manually run the EM Prerequisite Kit and taken corrective actions to meet the repository requirements, then run the kit again to reset the repository settings to what it had originally.

<ORACLE_HOME>/install/requisites/bin/emprereqkit executionType=install prerequisiteXMLRootDir=<prereq_xmlrootdir_location> connectString="<connect_string>" dbUser=SYS dbPassword=password reposUser=sysman dbRole=sysdba runPrerequisites=true runPostCorrectiveActions=true

3. By default, the following targets get automatically discovered and monitored in the Enterprise Manager Cloud Control Console:

  • Oracle WebLogic Domain (for example, GCDomain)
  • Oracle WebLogic AdminServer
  • Oracle WebLogic Server
  • Oracle Web Tier
  • Application deployments, one for the Enterprise Manager Cloud Control console and one for the platform background services.
  • Oracle Management Service
  • Oracle Management Repository
  • Oracle Management Agent
  • The host on which you installed Enterprise Manager Cloud Control

4. Changing SYSMAN Pass

<ORACLE_HOME>/bin/emctl config oms -change_repos_pwd

5. Backing up emkey

To back up the Management Service configuration including the emkey, run the following command:

<ORACLE_HOME>/bin/emctl exportconfig oms -dir <path_to_backup_location>6. Install a security certificate from a trusted certification authority on the browser.

7. Apply patch 30912308 if the Management Repository is using Oracle Database 12.2, 18.x or 19.x.

8. Oracle recommends to reset the optimizer adaptive features parameters by connecting to the database as SYSDBA and running the following:

alter system reset "_optimizer_nlj_hj_adaptive_join" scope=both sid='*';
alter system reset "_optimizer_strans_adaptive_pruning" scope=both sid='*';
alter system reset "_px_adaptive_dist_method" scope=both sid='*';
alter system reset "_sql_plan_directive_mgmt_control" scope=both sid='*';
alter system reset "_optimizer_dsdir_usage_control" scope=both sid='*';
alter system reset "_optimizer_use_feedback" scope=both sid='*';
alter system reset "_optimizer_gather_feedback" scope=both sid='*';
alter system reset "_optimizer_performance_feedback" scope=both sid='*';

If all looks good, from browser goto

//<hostname>:7799/em/faces/logon/core-uifwk-console-login

Log in with the username “sysman” and the password we specified during your installation.

 

 

 

 

1 thought on “Installing OEM 13.4 [Silent Install] – Part 3 : Postinstallation Tasks After Installing an Enterprise Manager System”

  1. Pingback: Installing OEM 13.4 [Silent Install] : Software-Only Method – Bored DevOps

Leave a Reply