How to manage OEM monitoring template using administration group

 

Problem statement:Suppose you are upgrading your OEM version from 13.4 to 13.5 or higher.During this upgrade you are also changing your OS platform from SOLARIS to Linux.Since this is a change of platform so we need to install new OMS instance along with repository database.After that we need to add targets either manually or through auto discovery option of OEM.Now, real problem is everytime we add targets we need to apply corresponding monitoring template.This will be really time consuming tasks if you have thousands of non-host targets.This problem can be solved using administration group

This document will guide you how to make this tasks simple and reduces effort.

 

This has been tested in following environments

 

Source	Target
OMS:-13.4	OMS:- 13.5
Agent: -13.4	Agent :-13.5
Repository database:-19.6	Repository database:-19.26
OS:-Solaris 10	OS:- OEL 8

 

Please follow below steps

1.       First create monitoring templates and define metric threshold according to your environment.

I have created 2 simple monitoring templates,one of database instance and other for host.

If you don’t know how to create template use below reference.

Reference:- Using Monitoring Templates

2.       Follow below navigation in OEM console

Setup>Add Targets>Adminstration Groups

You will end up landing in Getting started tab.Click on Hierarchy tab and follow next step

3.       There are different ways you can create hierarchy levels but I found that creating  hierarchy

based on Target Type is simple.Any other attributes needs to be added in target properties.

               Once you select Target Type you will get below warning saying only 10 targets can be selected

 

You can see 10 different targets type appeared by default.

 

Remove and add targets based on your environment.

Now create the group using Create button on top right.You will get a confirmation message

Now you can see targets are automatically added in corresponding hierarchy groups

4.       Now click on Template Collections tab and click on create button.Basically we will add various templates under this like below

 

  Now save the template collections.

 5.       Now Go to association tab where we will associate group with template collections.Click on each group and then associate like below

6.        

Now you can see templates are associated with administration group

7.       Final step is to synchronize this template collection changes to all groups

Go to Targets>Groups and select Adminstration group.

Group page will open and then click on start syncronization

You will see how many targets are synchronized.

 

You are done with all steps.Everytime you add a target it will be automatically assigned to administration group and corresponding templates will be applied based on synchronization schedule.

Hope you have learnt something useful…

 

How to change password of named credential using emcli

Problem statement: Suppose you have a process to change sys/system password of all your databases from a central server. This process has an impact if you are using sys/system as named credential in OEM. All your login through OEM will fail for database targets.Moreover,this can be a time consuming process if you have thousands of database targets.This article will help you to update all impacted named credential after sys/system password change.

Solution: Before jump into solution directly we need to understand how do we update OEM repository database. Definitely we are not going to fire SQL statement directly into OEM repository database.

We shall use emcli tool already available in OMS server.EMCLI is a tool which is nothing but a zython interpreter where you can write python script and call using emcli.I am not going into that scripting part but I will show you some basic commands to resolve this problem.

Step 1: Create a session using sysman user

emcli login -username=sysman -password=********

Login successful

Step 2: Find all database credentials like below

emcli list_named_credentials | grep DBCreds | grep sys

EBSGP5_SYS                     SYSMAN            oracle_database              DBCreds         cebsgp5                              sys
NC_CEBSGP5__2021-05-28-162346  SYSMAN            oracle_database              DBCreds         cebsgp5_EBSGP5                       sys
NC_TESTD2_2025-04-08-092927     SYSMAN            oracle_database              DBCreds         testd2                                sys
NC_TESTD3_2024-05-27-035554     SYSMAN            oracle_database              DBCreds         TESTD3                                sys
NC_TESTD4_2025-02-05-164844     SYSMAN            oracle_database              DBCreds         testd4                                sys
NC_TESTPREP6_2025-05-05-140633  SYSMAN            oracle_database              DBCreds         testprep6                             sys
NC_TESTPREP9                    SYSMAN            oracle_database              DBCreds         testprep9                             sys
NC_TESTQ2_2024-12-20-102450     SYSMAN            oracle_database              DBCreds         TESTQ2                                sys
NC_TESTQ3_2024-02-29-101701     SYSMAN            oracle_database              DBCreds         testq3                                system
NC_TESTT1_2024-01-31-135804     SYSMAN            oracle_database              DBCreds         testt1                                system
NC_TESTT2_2024-08-22-093600     SYSMAN            oracle_database              DBCreds         testt2                                sys
NC_TESTT3_2024-09-26-062948     SYSMAN            oracle_database              DBCreds         TESTT3                                sys
NC_TESTT4_2025-03-15-082356     SYSMAN            oracle_database              DBCreds         testt4                                sys
NC_TESTDWD                        SYSMAN            oracle_database              DBCreds         testdwd                                 sys
NC_TESTDWQ                        SYSMAN            oracle_database              DBCreds         testdwq                                 sys
NC_TESTDWT_2023-07-26-154146      SYSMAN            oracle_database              DBCreds         testdwt                                 system
NC_TESTDWT_2025-03-14-094116      SYSMAN            oracle_database              DBCreds         testdwt                                 system
NC_TESTMD1ODA_2024-06-13-012130  SYSMAN            oracle_database              DBCreds         testmd1oda                             sys
NC_TESTMQ1ODA_2024-07-03-080029  SYSMAN            oracle_database              DBCreds         testmq1oda                             sys
NC_TESTMQ3ODA_SYS                SYSMAN            oracle_database              DBCreds         testmq3oda                             sys
NC_TESTMT2ODA                    SYSMAN            oracle_database              DBCreds         testmt2oda                             sys
NC_TESTMT3ODA                    SYSMAN            oracle_database              DBCreds         testmt3oda                             sys
NC_ORACLE_D_2020-05-01-115902  SYSMAN            oracle_database              DBCreds                                              sys
NC_ORACLE_D_2022-06-03-084945  SYSMAN            oracle_database              DBCreds                                              sys
NC_ORACLE_D_2024-07-24-015533  SYSMAN            oracle_database              DBCreds         testmt1oda                             sys
 
Step 3. Validate any existing named credential like below
 
emcli modify_named_credential -cred_name=NC_TESTD2_2025-04-08-092927 -cred_type=DBCreds -cred_scope=Instance -target_name=testd2 -target_type=oracle_database -test
Credential test failed for testd2:oracle_database
Authentication failed ORA-01017: invalid username/password; logon denied
 
It shows that existing password is not working
 
Step 4. Change the password with test validation now
 
emcli modify_named_credential -cred_name=NC_TESTD2_2025-04-08-092927  -attributes="DBUserName:sys;DBPassword:******" -test
Credential updated.
 
Now same things can be automated using below simple shell script.
 
Disclaimer: This is just an example.Please modify and test the script in non-prod before deploying into production.
 
#!/bin/sh
ORACLE_BASE=/u01/app/oracle/gc_inst
ORACLE_HOME=/u01/app/oracle/13_4_0_0_middleware
echo "Enter repository database connection using format host:port/service_name:"
read repdb
echo "Enter sys/system password:"
read cookie
echo "Enter password for sysman existing in OMS repository:"
read sysmanpwd
emcli login -username=sysman -password=$sysmanpwd
emcli list_named_credentials | grep DBCreds | grep sys | awk -F " " '{if ($5 != "sys") print $1,$5,$6}' >~/named_cred.txt
while read line
do
cred_name=`echo $line | awk -F ' ' '{print $1}'`
db_target_name=`echo $line | awk -F ' ' '{print $2}'`
username=`echo $line | awk -F ' ' '{print $3}'`
echo "Changing password for $cred_name....."
if [ "$username" = "sys" ]; then
emcli modify_named_credential -cred_name=$cred_name -attributes="DBUserName:$username;DBPassword:${cookie};DBRole:sysdba" -test
else
emcli modify_named_credential -cred_name=$cred_name -attributes="DBUserName:$username;DBPassword:${cookie}" -test
fi
done < ~/named_cred.txt
emcli logout
 
Hope you have learnt something useful… 

Reference:-

https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.4/emcli/

Conditional tablespace alert using OEM

 Problem Statement: Lets assume as a DBA you wrote some script which moves old partitioned data of a table into some monthly archival tablespace. After data movement you found that utilization of archival tablespace is more than 90 percent. Since there will not be any DML operation on those data so you don’t want any OEM alert from those archival tablespace. This document will guide you how to achieve this requirement using OEM.

In my case there are at least 12 tablespaces which is dedicated for each month and starts with a string

Follow below navigation.

Oracle Database>Monitoring>Metric and Collection Settings

 

 

Click on pencil icon from below

Now you can see below that tablespace name selected as all others which means  it will send alert for all tablespaces but you want to exclude certain tablespace which starts with a matching string

 

Click on add button and leave warning and critical threshold which means any tableapce whose name starts with IND will be excluded as we have disabled without putting any threshold value.Now click on continue.

Click on ok button to save it in repository

From the incident manager you can validate that those alert is now cleared.

 

Hope you have learnt something useful...