Hi Team,
For this database, I have temporarily reduced the /app filesystem alert threshold to 55%. We may receive alerts at this level for the time being.
This is due to the ongoing backup issue, and we want to avoid any additional risk. Keeping the alert at 55% will help us proactively monitor the filesystem and also serve as a reminder to periodically check and follow up with the backup team.
Thanks.
BCM Automation Dashboard
Overview
The BCM Automation Dashboard provides a centralized view of all BCM database automation requests and their status. While BCM automation handles the execution of activities, this dashboard improves visibility, tracking, and coordination for BCM planners, DBAs, and application teams.
It is especially useful during major or “Big Rock” BCM events, where multiple requests run in parallel within the same window. The dashboard helps teams monitor request status, dependencies, and pending actions from a single place.
Dashboard Sections
1. Change & Task Summary
Shows RNOW BCM changes and user-created RITM requests, including approval status and scheduled BCM execution dates.
2. DBA Action Items
Displays requests currently being handled by the DBA team, helping track progress—especially useful during large BCM events or weekend checkouts.
3. Pending Application Actions
Lists requests waiting for confirmation or action from application teams, helping identify dependencies early.
4. Trend & Analysis
Provides yearly insights of BCM requests by RDBMS platforms, helping track trends and support operational planning.
Purpose
The dashboard helps make BCM operations more transparent, easier to track, and better coordinated across teams. Teams are encouraged to use the dashboard and share feedback for continuous improvements.
Hi Team,
Just checking if there are any updates or findings on the databases we reported earlier that appear to have no backup configuration.
We have also identified several other databases with a similar issue. Appreciate it if the team could review them and configure backups where required, especially if they were part of the migration.
Thanks.
Subject: Action Required: Database Backup Gaps Identified
Dear Team,
As part of our backup monitoring review, we have identified several databases where backups are currently not present. Since backups should be validated as part of the build and migration process, we wanted to bring this to your attention.
The databases highlighted in red appear to be of particular concern, as no backups have been detected for more than six months.
Could you please review and confirm if there are any gaps or if any action is required from the migration side?
Appreciate your support in ensuring backup coverage is in place.
Best regards,
Hi Team,
We have developed a new OEM Backup Compliance Report to improve visibility and monitoring of backup compliance across our Oracle database estate.
This report helps identify:
- Databases that have not been backed up in the last 3 days
- Databases with no backup configuration in place
L1 team members are requested to regularly monitor and leverage this report to proactively identify any backup gaps and initiate remediation where required.
Going forward, this report will also be integrated into our regular operational reviews so that we continuously monitor backup health and address any compliance gaps early.
Please ensure this report is reviewed as part of your routine monitoring activities.
Regards,
Nikhil
Today I’ll be presenting a report that I developed called the OEM Backup Compliance Report. The primary goal of this report is to strengthen our visibility around backup compliance and help us proactively manage risks across our Oracle database landscape.
When we usually check backup information, we tend to rely on Commvault reports. While Commvault provides useful backup data, it only shows information for databases that are already registered and configured in Commvault.
This creates a potential visibility gap.
If a database is not registered in Commvault, we may not even know that it exists from a backup compliance perspective. In other words, there could be databases without backup coverage, and we would have very limited visibility into that.
To address this challenge, I leveraged the OEM repository database to build a report that directly analyzes the databases managed within OEM.
This report is designed to answer two key questions for our Oracle estate:
First, which databases have not been backed up in the last three days?
Second, which databases have never been backed up at all, meaning there is no backup configuration in place.
These two checks allow us to quickly identify systems that might be at risk and require immediate attention.
Let me briefly explain how the report works.
A script periodically scans all Oracle and RAC databases managed by OEM and collects key information such as the database name, the host name, and backup activity details.
The report then consolidates this information and highlights systems that require attention.
It also identifies higher-risk databases, particularly production environments or databases running in NOARCHIVELOG mode, since those environments typically have stricter recovery requirements.
Additionally, the report includes operational indicators such as:
Production status
Archive log configuration
Blackout status
And tracking references for remediation if needed
These details help us quickly understand both the technical state and operational priority of each database.
The real value of this report is proactive monitoring and faster risk identification.
With this visibility we can:
Quickly detect databases with missing or outdated backups
Ensure backup compliance across the Oracle environment
Support audit requirements with transparent reporting
And prioritize remediation for critical systems first
In short, this report gives us a centralized view of backup health across our OEM-managed database estate, which significantly improves our operational awareness.
Going forward, my recommendation is to incorporate this report into our regular operational reviews, so we can continuously monitor backup compliance and address any gaps before they become operational risks.
That concludes the overview.
I’ll now walk you through the report itself and demonstrate how it works.
Hi Vikas,
To improve visibility and coordination around BCM activities, we have created a BCM Automation Dashboard that provides a centralized view of BCM requests, approvals, and execution status.
This should be particularly helpful during major or “Big Rock” BCM events, where multiple requests are executed in parallel on the same day and often within the same time window. The dashboard helps planners and the DBA team quickly track progress, identify pending approvals, and monitor any actions required from application teams.
Dashboard Overview
Change & Task Summary – Displays RNOW changes and user-raised RITM requests, along with approval status and scheduled BCM dates. This helps during planning to quickly identify upcoming BCM activities.
DBA Action Items – Provides visibility into requests currently being processed by the DBA team and their current stage. This is especially useful during high-volume BCM windows and weekend checkouts.
Pending Application Actions – Highlights requests awaiting confirmation or go-ahead from application teams, helping identify dependencies and avoid delays.
Trend & Analysis – Shows BCM requests raised during the year, categorized by RDBMS platform, providing insights into activity trends.
Sharing this with the team as well so everyone involved in BCM activities can leverage the dashboard for better tracking and coordination.
Please feel free to share any suggestions or feedback.
Thanks.
Hello Friends! I am aliena part time blogger from Bihar. I am a student and I manage my study as well as my blog. I am 14 years old and I want to help those people who really want to do something on internet.
Copyright © 201. Metro UI Theme. Designed by: Templateism
