Oracle Enterprise Manager 13.5 Release Update with Summary Dashboard

 

Oracle Enterprise Manager 13.5 Release Update 2

In Oracle Enterprise Manager 13.5 the custom dashboard option was not visible in the base 13.5 release.


Dashboards allow you to visualize monitoring and management data in real-time, enable youto monitor your enterprise at a glance, and simplify potential problems resolution. With RU2, Enterprise Manager introduces out-of-the-box dashboards that provide a summary of the health, compliance status, grouping of your targets, and other details of your assets. The health and status data is organized, summarized, and presented graphically as various widgets. To further analyze and diagnose potential issues, you can drill down to more information from each widget. These dashboards can further be copied and customized as you see fit for your environment and your monitoring guidelines.

you can find more information in the below doc.

13.5.0 Enterprise Manager Cloud Control Base Platform Monthly Release Update (RU) 2 (Doc ID 2822316.1)

https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/emcon/new-features-focus-area.html#GUID-39680664-C8BD-4A25-911B-46B4B4A76AF7

Comments

Post a Comment

Popular posts from this blog

Resolving 19c Oracle Database Performance Woes: Unraveling the Mystery of 'Free Buffer Waits'

Image
  Introduction:   A recent upgrade from version 19.21 left a customer grappling with a perplexing performance decline, marked by a surge in "free buffer waits." Tasks that once took a manageable two hours were suddenly stretching beyond the tolerable 10-hour mark, prompting a closer examination of the underlying issues. The customer had implemented a multi-tenant architecture utilizing a single Pluggable Database (PDB).   Unveiling the Culprit:   The initial investigation pinpointed a conspicuous increase in "free buffer waits," casting a shadow on system efficiency and causing disruptions in the normal flow of operations. Recognizing the critical nature of this bottleneck, the focus shifted to conducting a thorough hanganalyze to unravel the intricacies of the problem. Chains most likely to have caused the hang:   [a] Chain 1 Signature: 'rdbms ipc message'<='free buffer waits'       Chain 1 Signature Hash: 0x8e1d98d...
Read more

Unveiling the Mystery Behind a Critical Downtime Incident: Default TRANSMIT_MODE Behavior in Oracle Database 19c's Log Archive Destinations

Image
Recently, one of our valued customers experienced a significant downtime event when their complete 6-node RAC cluster fell into a hang state due to a massive pile-up of sessions, exceeding 6000. The gravity of the situation was immediately apparent as the downtime persisted intermittently for nearly four hours, from 2:10 PM to 5:30 PM, impacting critical transactions and leading to declines. Upon their reaching out to us for assistance, our troubleshooting journey commenced, aiming to uncover the root cause and provide recommendations to rectify the issue. Problem Statement: The 6-node cluster entered a hang state despite attempted reboots, resulting in a prolonged outage with severe implications for transaction processing. Unraveling the Culprit: The issue presented itself as a perplexing anomaly, requiring thorough analysis of diagnostic data within the live system. Initial investigations revealed a high occurrence of GC and logfile sync wait events amidst other contention factors. N...
Read more

Investigating a CPU Spike and Resource/cluster Hang in Oracle RAC Environment

Introduction: In a complex Oracle Real Application Clusters (RAC) environment, unexpected issues can arise, leading to system instability and performance degradation. In this blog post, we will delve into a specific incident involving a CPU spike and resource hang that occurred during the execution of a high parallelism SQL job. We will analyze the root causes and explore potential solutions to mitigate such problems in the future. The Incident: On a particular day between 2:00 PM and 6:30 PM IST, an SQL job with a Degree of Parallelism (DoP) set to 200 was initiated on Node#3 around 2:12 PM IST. Soon after, the CPU Idle% dropped to single digits, reaching as low as 1% at 3:10 PM IST. This performance degradation led to Node#6 being evicted following a dirty detach reconfiguration. During the incident, it was observed that the shutdown process remained hung for an extended period, and the system was only restarted at 4:44 PM as per the Syslog. The Cluster Ready Services (CRS) stack cam...
Read more