There are many old problems and their incidents in OEM repository for many years. Here is an example of how to clear those problems by using emcli. Otherwise you might need log on to OEM console by clearing them from one target to another. Imagine your OEM repository might manage thousands of different kinds of targets.
Read more of this content when you subscribe today.
The Enterprise Manager Agent does not automatically clear those stateless alerts.
This post explains how to clean up stateless alerts, also provides shell scripts to generate commands to automatically clean all stateless alerts if possible.
Read more of this content when you subscribe today.
After RAC servers rebooted, or GI cluster restarted, scan listeners show offline on OEM. Now we explore how to resolve this issue here.
Read more of this content when you subscribe today.
For Oracle Enterprise Manager 13c agent, it creates many directories and files under /tmp of Linux server:
... .. . drwxr-----. 2 oracle oinstall 46 Sep 18 10:05 OraInstall2019-09-18_10-05-53AM drwxr-----. 2 oracle oinstall 46 Sep 18 10:05 OraInstall2019-09-18_10-05-57AM drwxr-----. 2 oracle oinstall 46 Sep 18 10:06 OraInstall2019-09-18_10-06-02AM drwxr-----. 2 oracle oinstall 46 Sep 19 10:05 OraInstall2019-09-19_10-05-49AM drwxr-----. 2 oracle oinstall 46 Sep 19 10:05 OraInstall2019-09-19_10-05-53AM drwxr-----. 2 oracle oinstall 46 Sep 19 10:05 OraInstall2019-09-19_10-05-57AM drwxr-----. 2 oracle oinstall 46 Sep 19 10:06 OraInstall2019-09-19_10-06-01AM
$ cd OraInstall2019-09-19_10-06-01AM $ ls -ltr total 4 -rw-r-----. 1 oracle oinstall 129 Sep 19 10:06 nextgen2019-09-19_10-06-01AM.log $cat nextgen2019-09-19_10-06-01AM.log 2019-09-19 10:06:01,829 INFO [1] oracle.sysman.oii.oiio.oiiol.OiiolTextLogger - OiicStandardInventorySession(OPatch,13.8.0.0.0)
It is a bug for OEM 13c agent which tries to collect ORACLE_HOME configurations, etc.
In Oracle Enterprise Manager 13c ( 13.2.0.0.0), auto extending tablespace corrective action is not working as expected, specially when calculating space usage.
*** BEGIN Parameters ***
Increase Bigfile Size (%): 5
Maximum Disk Usage (%): 95
How to Increase Space: Increase by %
...
..
.
ASM disk group is: DATA
Last created datafile: +DATA/RACTEST/3F9C860784456287E053530F040ADB20
/DATAFILE/test.372.1018794017
Tablespace total size (MB): 899964.00
Largest numeric suffix: 0
Datafile filename: test.372
Datafile directory: +DATA/RACTEST/3F9C860784456287E053530F040ADB20/
DATAFILE/
Datafile suffix: .1018794017
ASM space usage for disk group DATA is free(MB): 5817030.000,
total(MB): 28311415.000, required
for mirroring(MB): 0.000, redundancy: 1
ASM projected safely usable free space (MB) is: 1317210.000
ASM projected Space Used (%) is: 95.35
Not enough disk space left in disk group DATA to extend datafile,
95.35% > 95%
Disconnected from database
From the CA job trace file, we can see:
Increase Bigfile Size (%): 5
Maximum Disk Usage (%): 95
How to Increase Space: Increase by %
ASM space usage for disk group DATA is free(MB): 5817030.000,
total(MB): 28311415.000
Current big tablespace size : 899964.00
ASM projected safely usable free space (MB) is: 1317210.000
ASM projected Space Used (%) is: 95.35
Not enough disk space left in disk group DATA to extend datafile,
95.35% > 95%
Disconnected from database
ASM projected safely usable free space (MB) should be :
Current disk group free space - Current Tablespace Size * Increase % = 5817030.000 - 899964*5/100 = 5772031.8 MB
While the Corrective Action trace file shows below ASM projected safely usable free space (MB):
ASM projected safely usable free space (MB) is: 1317210.000
Let’s check the source code from Oracle Enterprise Agent, we can see the code missed Percentage ( %) for tablespace increase rate.
$cd /u01/app/oracle/product/agent/agent_13.2.0.0.0/plugins/
oracle.sysman.db.agent.plugin_13.2.1.0.0/scripts/db
$ls -l dbAddSpaceTS.pl
...
..
.
# Case 1: Increase existing datafile by %
if ($bIncrByPct)
{
$diskFreeMB = $dirAvailMB - ($tsSizeMB * $incrPct);
}
...
..
.
# Case 1: Increase by %
if ($bIncrByPct)
{
$safelyUsableMB = ($dirAvailMB - ($tsSizeMB * $incrPct)
- $dgReqMirror) / $dgRedundancy;
}
...
..
.
so the right code should be :
# Case 1: Increase existing datafile by %
if ($bIncrByPct)
{
$diskFreeMB = $dirAvailMB - ($tsSizeMB * $incrPct)/100;
}
...
..
.
# Case 1: Increase by %
if ($bIncrByPct)
{
$safelyUsableMB = ($dirAvailMB - ($tsSizeMB * $incrPct)/100
- $dgReqMirror) / $dgRedundancy;
}
...
..
.
After modifying the code, everything works fine for Corrective Action job.
Make DBA Life Easy 