Friday 23 October 2020

OEM13c - Add agents on remote target host server




Here we add monitoring on OMR database and after that add host on target database server and add monitoring on it using EM 13c Console .

OMR database and OEM 13c are in same server so agent already installed at the time of installation so we add monitoring on server.
  1. Add Discovery target on OMR database
  2. Add OEM agent on target host and add discovery target 
OMR Database : OEMDB

Hostname : oem13c.example.com

New Target host name : srv3.example.com

Target Database : SMRCDB

OEM Console URL : 


 Enterprise Manager Cloud Control URL: https://oem13c.example.com:7803/em also ( https://192.168.56.71:7803/em)

 Admin Server URL: https://oem13c.example.com:7102/console

BI Publisher URL: https://oem13c.example.com:9803/xmlpserver/servlet/home


STEP 1 : Login OEM console and go to setting and add target manually 



STEP 2 : choose 2nd option (Add Non-Host Targets Using Guided Process )



STEP 3 : As default oracle database and listener automatically set on discovery target types.


STEP 4: Target already installed so we select OMR database server oem13c.example.com


STEP 5: OEM will discover host at there end .
 

STEP 6 : Select on checkbox OEMDB database and add password of dbsnmp schema. By default it is locked.
SQL> alter user dbsnmp account unlock identified by dbsnmp;

User altered.

SQL> select USERNAME,DEFAULT_TABLESPACE,ACCOUNT_STATUS from dba_users where username='DBSNMP';

USERNAME                                 DEFAULT_TABLESPACE             ACCOUNT_STATUS
---------------------------------------- ------------------------------ --------------------------------
DBSNMP                                   SYSAUX                         OPEN
 


STEP 7 :  Discovery Target Review



STEP 8 : Target confirmation 
 

STEP 9 :  OEMDB  database and listener Successfully on console. 




Adding OEM Agent on target server  and discover target for monitoring

OS NAME : srv3.example.com

STEP 1: Select add host targets


STEP 2 : Add host targets.

 



STEP 3 : Add named credential of oracle user and then  root (optional) user .


STEP 4 : Add  agent base directory /u01/app/oracle/agents . Instance directory will be automatically created.
Default port is 3872.


STEP 5 : Review Agent target hosts


STEP 6: Deploy agent Summary process 


STEP 7: Agent successfully added on target server.


Add Discovery target on srv3.example.com agent

STEP 1: Choose 2nd option ( Add using guided process  and then further select default oracle database and listener option)



STEP 2 : Add host target details.




STEP 3: Add password dbsnmp user on database discovery results in this server we have CDB database so details will automatically fetch by discovery.



STEP 4: Database discovery review


STEP 5: Configuration of  database and listener target saved successfully.



STEP 6 : Successfully done 



STEP 7: OEM 13c Console Summary dashboard




OEM 13c : Oracle Enterprise manager Installation 13c on linux 64 bit OS.

OMR Database : OEMDB

OMS OEM Console : 13c

Oprerating System : OEL 7.7 64 bit

 OMR Database : 12.2.0.1 

links :  OMR Database minimum recommended parameter


  • Download and install oem 13c  ( we have downloaded OEM 13c already), Here OMR database and OEM13c are in same hosts we can install OMR database and OEM 13c server on different server as well.

[oracle@oem13c oem]$ ll

total 9497096

-rwxrwxr-x. 1 oracle oinstall 1278491093 Oct 20 19:21 em13300_linux64-2.bin

-rwxrwxr-x. 1 oracle oinstall 1742204641 Oct 20 19:22 em13300_linux64-2.zip

-rwxrwxr-x. 1 oracle oinstall 2090882426 Oct 20 19:23 em13300_linux64-3.zip

-rwxrwxr-x. 1 oracle oinstall 2117436260 Oct 20 19:24 em13300_linux64-4.zip

-rwxrwxr-x. 1 oracle oinstall  694002559 Oct 20 19:24 em13300_linux64-5.zip

-rwxrwxr-x. 1 oracle oinstall 1801995711 Oct 20 19:25 em13300_linux64-6.zip

  • Execute /em13300_linux64.bin to begin installation.

[oracle@oem13c oem]$ ./em13300_linux64.bin

STEP 1: skip the security update option :



STEP 2 :
Skip software update 


STEP 3 : Fix warning  in my case i proceed further as kernel parameter and memory is sufficient for installation.


STEP 4 : In my case Proceed with option simple option


STEP 5 : Middleware home location | agent base directory | hostname


STEP 6 :  Provide sysman password which is used for OEM console. and provide OMR database details.


STEP 7:  Disable ( Configure a shared location for oracle BI publisher ) on next screenshot.



STEP 8: Review installation process details.


STEP 9 : After 4-5 hr depends on OS configuration run ./allroot.sh from middleware home.


STEP 10 : Installation complete so copy URL from console https://oem13c.example.com:7102/em

DNS configuration not installed on system for dns visit link :  or use host IP address https://192.168.56.71:7102/em



STEP 11 :
Login OEM console using ip address  user name is sysman
 


STEP 12 :
OEM Console 


This information is also available at: 


/u01/app/oracle/middleware/install/setupinfo.txt


See the following for information pertaining to your Enterprise Manager installation:



Use the following URL to access:


1. Enterprise Manager Cloud Control URL: https://oem13c.example.com:7803/em

2. Admin Server URL: https://oem13c.example.com:7102/console

3. BI Publisher URL: https://oem13c.example.com:9803/xmlpserver/servlet/home


 https://192.168.56.71:7803/em

The following details need to be provided while installing an additional OMS:


1. Admin Server Host Name: oem13c.example.com

2. Admin Server Port: 7102


You can find the details on ports used by this deployment at : /u01/app/oracle/middleware/install/portlist.ini



 NOTE:

 An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the Repository becomes unusable. 


 A backup of the OMS configuration is available in /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/backup on host oem13c.example.com. See Cloud Control Administrators Guide for details on how to back up and recover an OMS.


 NOTE: This backup is valid only for the initial OMS configuration. For example, it will not reflect plug-ins installed later, topology changes like the addition of a load balancer, or changes to other properties made using emctl or emcli. Backups should be created on a regular basis to ensure they capture the current OMS configuration. Use the following command to backup the OMS configuration:

/u01/app/oracle/middleware/bin/emctl exportconfig oms -dir <backup dir>