Manual Method of Installation of OEM Agent 12C

-

 DBAs need to install OEM agent on daily basic in order to promote/discover target server or related targets. 

     (1)   Login to the OEM 12C server and follow the below steps -

     (A) Setup the “.profile_oms” it will setup the environment variables for the OEM 12C

     (B) Login to the sysman account with the “emcli” utility

     (C) Synchronized the OMS 12C

      (D) Verify the Supported Versions in our OMS 12C.We can configure other Agents as well like Hp UNIX etc but in our Cummins environment, we are only using the Solaris, LINUX, AIX and Windows. With this reason, these Agents are configured on the OMS 12C.

     


     (1)  To install the OEM 12C, we have to download the software from the OEM 12C console with the help of “emcli” utility

      


     (2)  SCP this file “12.1.0.2.0_AgentCore_23.zip” to target machine

     (3) Create the Agent 12C response file

 

cat /usr/users/oemagent/solaris/agent.rsp

####################################################################

## copyright (c) 1999, 2012 Oracle. 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 <Value Required> 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

 

 

#-------------------------------------------------------------------------------

#OMS_HOST:<String> OMS host info required to connect to OMS

#EM_UPLOAD_PORT:<String> OMS port info required to connect to OMS

#AGENT_REGISTRATION_PASSWORD:<String> Agent Registration Password needed to

#     establish a secure connection to the OMS.

#AGENT_INSTANCE_HOME:<String> Agent instance home is the location of agent state directory.

#AGENT_PORT:<String> Agent port on which the agent process should be started.

#b_startAgent:<boolean> Agent will not be started after configuration if the value specified is false.

#ORACLE_HOSTNAME:<String> Fully qualified domain name of host where is the agent is deployed.

#s_agentHomeName:<String>Customized Oracle home name for the agent home. Example: s_agentHomeName="agent12gR1"

#-------------------------------------------------------------------------------

OMS_HOST=omshost

EM_UPLOAD_PORT=4900

AGENT_REGISTRATION_PASSWORD=******

AGENT_INSTANCE_HOME=/u01/app/oracle/product/agent12c/agent_inst

AGENT_PORT=1849

b_startAgent=true

ORACLE_HOSTNAME=targethost

s_agentHomeName="agent12c"

#-------------------------------------------------------------------------------

#s_agentServiceName:<String> 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 = "Oracleagent12gAgent"      ;  default value

#      s_agentServiceName = "GridAgent"                 ;  User specified value

#-------------------------------------------------------------------------------

#s_agentServiceName=""

 

####################################################################################

#Please Don't change the values of these variables

####################################################################################

#-------------------------------------------------------------------------------

#EM_INSTALL_TYPE:<STRING> install type

#-------------------------------------------------------------------------------

EM_INSTALL_TYPE="AGENT"

 (4) There are many different ways to deploy the agent on target environment. I am using the silent method with a response file – 

# mkdir –p /u01/app/oracle/product/agent12c 

mkdir –p /u01/app/oracle/product/agent12c r3

Mkdir –p /u01/app/oracle/oraInventory_agent12c

mkdir –p /u01/app/oraInventory_agent12cr3

# /usr/users/oemagent/solaris/agentDeploy.sh AGENT_BASE_DIR=/u01/app/oracle/product/agent12c  RESPONSE_FILE=/usr/users/oemagent/solaris/agent.rsp

(5) Installation

/usr/users/oemagent/solaris/agentDeploy.sh AGENT_BASE_DIR=/u01/app/oracle/product/agent12c RESPONSE_FILE=/usr/users/oemagent/solaris/agent.rsp

 

-e Validating the OMS_HOST & EM_UPLOAD_PORT

Executing command : /u01/app/oracle/product/agent12c/core/12.1.0.2.0/jdk/bin/java -classpath /u01/app/oracle/product/agent12c/core/12.1.0.2.0/jlib/agentInstaller.jar:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /u01/app/oracle/product/agent12c/core/12.1.0.2.0 /usr/users/oemagent/solaris /u01/app/oracle/product/agent12c -prereq

 

Validating oms host & port with url: http://omshost:4900/empbs/genwallet

Validating oms host & port with url: https://omshpst:4900/empbs/genwallet

Return status:3

Unzipping the agentcoreimage.zip to /u01/app/oracle/product/agent12c ....

12.1.0.2.0_PluginsOneoffs_23.zip

Executing command : /usr/users/oemagent/solaris/unzip -o /usr/users/oemagent/solaris/12.1.0.2.0_PluginsOneoffs_23.zip -d /u01/app/oracle/product/agent12c

Executing command : /u01/app/oracle/product/agent12c/core/12.1.0.2.0/jdk/bin/java  -d64 -classpath /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/jlib/OraInstaller.jar:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/jlib/xmlparserv2.jar:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/jlib/srvm.jar:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/jlib/emCfg.jar:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/jlib/agentInstaller.jar:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller /u01/app/oracle/product/agent12c/core/12.1.0.2.0 /usr/users/oemagent/solaris /u01/app/oracle/product/agent12c /u01/app/oracle/product/agent12c/agent_inst AGENT_BASE_DIR=/u01/app/oracle/product/agent12c AGENT_BASE_DIR=/u01/app/oracle/product/agent12c RESPONSE_FILE=/usr/users/oemagent/solaris/agent.rsp

 

 

Executing agent install prereqs...

Executing command: /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -prereqchecker -silent -ignoreSysPrereqs -waitForCompletion  -prereqlogloc /u01/app/oracle/product/agent12c/core/12.1.0.2.0/cfgtoollogs/agentDeploy -entryPoint oracle.sysman.top.agent_Complete -detailedExitCodes PREREQ_CONFIG_LOCATION=/u01/app/oracle/product/agent12c/core/12.1.0.2.0/prereqs  -J-DORACLE_HOSTNAME=targethost -J-DAGENT_PORT=1849 -J-DAGENT_BASE_DIR=/u01/app/oracle/product/agent12c

Prereq Logs Location:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/cfgtoollogs/agentDeploy/prereq<timestamp>.log

Agent install prereqs completed successfully

 

Cloning the agent home...

Executing command: /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/u01/app/oracle/product/agent12c/core/12.1.0.2.0 -responseFile /usr/users/oemagent/solaris/agent.rsp  AGENT_BASE_DIR=/u01/app/oracle/product/agent12c AGENT_BASE_DIR=/u01/app/oracle/product/agent12c RESPONSE_FILE=/usr/users/oemagent/solaris/agent.rsp -noconfig  ORACLE_HOME_NAME=agent12c -force b_noUpgrade=true

Clone Action Logs Location:/u01/app/oraInventory/logs/cloneActions<timestamp>.log

Cloning of agent home completed successfully

 

Attaching sbin home...

Executing command: /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -attachHome -waitForCompletion -nowait ORACLE_HOME=/u01/app/oracle/product/agent12c/sbin ORACLE_HOME_NAME=sbin12c1 -force

Attach Home Logs Location:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/cfgtoollogs/agentDeploy/AttachHome<timestamp>.log

Attach home for sbin home completed successfully.

 

Updating home dependencies...

Executing command: /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/bin/runInstaller -ignoreSysPrereqs -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/u01/app/oracle/product/agent12c/sbin:/u01/app/oracle/product/agent12c/core/12.1.0.2.0,} -invPtrLoc /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oraInst.loc -force

Update Home Dependencies Location:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/cfgtoollogs/agentDeploy/UpdateHomeDeps<timestamp>.log

Update home dependency completed successfully.

 

Performing the agent configuration...

Executing command: /u01/app/oracle/product/agent12c/core/12.1.0.2.0/oui/bin/runConfig.sh ORACLE_HOME=/u01/app/oracle/product/agent12c/core/12.1.0.2.0 RESPONSE_FILE=/u01/app/oracle/product/agent12c/core/12.1.0.2.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true

Configuration Log Location:/u01/app/oracle/product/agent12c/core/12.1.0.2.0/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log

 

 

Agent Configuration completed successfully

 

The following configuration scripts need to be executed as the "root" user.

#!/bin/sh

#Root script to run

 /u01/app/oracle/product/agent12c/core/12.1.0.2.0/root.sh

To execute the configuration scripts:

1. Open a terminal window

2. Log in as "root"

3. Run the scripts

Agent Deployment Successful.

Agent deployment log location:

/u01/app/oracle/product/agent12c/core/12.1.0.2.0/cfgtoollogs/agentDeploy/agentDeploy_2013-02-07_17-50-07-PM.log

Agent deployment completed successfully.


      



I     Installation completed.


       Please check our blog for GUI based installation as well. 

You can learn more about oracle database administration: 

Pro Oracle GoldenGate for the DBA

Oracle Security Tools Installation and Configuration

Expert Oracle Exadata 

Oracle Database 12c Release 2 Real Application Clusters Handbook: Concepts, Administration, Tuning & Troubleshooting

Expert Oracle RAC 12c


 ==========================================================

Please check our other blogs for OEM & OMS. 

Location: Singapore

Comments

Post a Comment

Please do not enter any spam link in comment Section suggestions are Always Appreciated. Thanks.. !

Popular posts from this blog

Restore MySQL Database from mysqlbackup

-
Image
 Restore MySQL Database from mysqlbackup  In todays world, One of the most common activity is to perform database restore using old backup or performing PIT recovery for database.  In this blog , We will show you how to perform restore and recovery of the MySQL database using backup taken via mysqlbackup. In order to restore Mysql database from MySQL backup , We will follow below steps: 1) Shut down MySQL Database Server/Service Check the status of the mysql service using command : systemctl status mysql Shut down mysql service using command : systemctl stop mysql 2) Delete all existing file of MySQL Server Delete all files inside the server's data directory. Also delete all files inside the directories specified by the --innodb_data_home_dir, --innodb_log_group_home_dir, and --innodb_undo_directory options for restore, if the directories are different from the data directory. 3) Restore full Backup mysqlbackup  --defaults-file=/etc/mysql/mysql.conf.d/mysqld.cnf --datadir=/var/lib
Read more

Oracle 19c New Features

-
Oracle 19c New Features As Oracle Support have made 12.2 version of Oracle ,its has become important for us to upgrade our 12c database to 19c.And before upgrade any database to latest version , We need to know the latest new features of that particular version.  In the current blog , We are going to discuss about new features of the Oracle 19C database : 1)Automatic Indexing  This is one of the important Oracle database 19c New feature. Automatic Indexing is one of the great feature included in 19c . It automates index management tasks, such as creating, rebuilding, and dropping indexes in an Oracle Database based on changes in the application workload. This feature improves database performance by managing indexes automatically in an Oracle Database. Oracle has provided new package DBMS_AUTO_INDEX for this. This enables automatic indexing in a database, but creates any new auto indexes as invisible indexes, so that they cannot be used in SQL statements: EXEC DBMS_AUTO_INDEX.CONFIGURE
Read more

Install & Configure MySQL Router - MySQL InnoDB Cluster

-
Image
Install & Configure MySQL Router -  MySQL InnoDB Cluster MySQL Router is one of the important component of MySQL InnoDB Cluster as it's used by applications to connect to the MySQL DBs running on cluster.  In this blog, We will show How we can install and configure MySQL Router either on application server or on dedicated server for MySQL Router. Below are the step to install and configure MySQL Router: 1) Install MySQL Router on the Server(In our case , We are restoring MySQL Router on the ubuntu server). Run command as root user : apt-get install MySQL-router 2) Bootstrap or Configure MySQL Router mysqlrouter --bootstrap clusteradmin@mysqlhost01:3306 --user=mysqlrouter In Case of any issue in configuring MySQL Router ,We can use -force option of the bootstrap. mysqlrouter --bootstrap clusteradmin@n4ldbdev5030:3306 --directory=/home/myrouter --user=mysqlrouter --force 3) Test Connectivity via MySQL Router. mysqlsh --uri clusteradmin@localhost:6446 you can learn more about
Read more