EM 12c, 13c: 'CPU Utilization (%) of a cpu' Metric Showing 'No data to display' On All Metrics In EM Console

 EM 12c, 13c: 'CPU Utilization (%) of a cpu' Metric Showing 'No data to display' On All Metrics In EM Console

Login to OEM Console -> Navigate to the Host target -> Monitoring -> All Metrics -> Expand "CPU Usage" -> Select "CPU Utilization (%) of a CPU" -> Select Last 24 Hours next to "View Data"

Last 24 hours' Graphs Data for the "CPU Utilization (%) of a CPU" metric of Host Target is Not Being Displayed in OEM Cloud Control.

 'Usage Type' of 'Use of Metric Data' is setting "Alerting Only".

⇒This setting means, 'Upload Interval' of this metric is「On Alert].

SOLUTION 

1) Change 'Usage Type' of 'Use of Metric Data' is setting from "Alerting Only" to "Alerting and Historical Trending".

2)'Upload Interval' setting  a value except "0". ※The number must be greater than or equal to 1.

3) Click the "OK" button.

4) Wait for 15 minutes and verify the  EM Console, it will show metrics data.

※It can be changed too, in the following in EM console.

Login to OEM Console -> Navigate to the Host target -> Monitoring -> Metric and Collection Settings -> Edit Collection Settings: <Metric_name>

Document ID - 2630530.1

Oracle Database Deployment: EC2 vs. RDS vs. Custom RDS

 

Oracle Database Deployment: EC2 vs. RDS vs. Custom RDS

Overview

This summary contrasts three deployment models for Oracle databases, assessing control, cost, management, scalability, and availability to guide strategic decision-making.

Deployment Options

Amazon EC2 (Self-Managed Oracle)

• Control: Maximum, with complete customization.
• Management: High responsibility; manual updates, maintenance.
• Cost: Higher due to manual management and operational expenses.
• Flexibility: Full, manual scalability and availability configurations.
• Use Case: Niche applications requiring unique configurations or specific Oracle features.

Amazon RDS for Oracle

• Control: Moderate, with managed service benefits.
• Management: Lowered by automated tasks (backups, patching).
• Cost: Reduced through managed services and no upfront hardware investment.
• Flexibility: Built-in scalability and high availability (Multi-AZ).
• Use Case: General business applications seeking balance between management ease and customization.

Custom RDS Solution for Oracle

• Control: High, tailored environment for Oracle.
• Management: Significant, akin to EC2 but with potential for cloud-agnostic deployment.
• Cost: Varied, influenced by design complexity and infrastructure choice.
• Flexibility: Custom-configured for scalability and DR.
• Use Case: Specific scenarios needing cloud-agnostic setups or advanced Oracle functionalities not available in Amazon RDS.

Key Considerations

• Operational Overhead vs. Automation: Choose between hands-on control (EC2, Custom RDS) and operational efficiency (Amazon RDS).
• Cost Implications: Consider long-term TCO, balancing upfront investments against ongoing operational savings.
• Scalability and Reliability: Weigh the need for manual setup and customization against the convenience of managed scalability and availability.

Recommendation

Aligning with business objectives and IT capabilities is paramount. Amazon RDS for Oracle is recommended for most use cases due to its balance of ease of use, cost-effectiveness, and built-in features. EC2 or Custom RDS may be suited for specialized requirements outside RDS's scope.

For a concise, one-page summary in a comparative format that highlights the differences between Amazon EC2, Amazon RDS for Oracle, and custom RDS solutions for Oracle, a table is an effective way to present the information clearly and facilitate quick comparison. This format supports executive decision-making by directly contrasting key aspects of each option.

---

Comparative Summary: Oracle Database Deployment Options

Criteria	Amazon EC2	Amazon RDS for Oracle	Custom RDS Solution
Control	Maximum (full OS and DB control)	Moderate (managed DB settings)	High (customizable environment)
Management Effort	High (manual setup and maintenance)	Low (automated backups, patching)	High (requires manual management)
Cost Efficiency	Variable (depends on management and scaling)	High (reduced operational costs)	Variable (depends on complexity)
Scalability	Manual (requires planning and execution)	Automated (easy scaling options)	Manual (flexible but complex)
High Availability	Manual setup (custom HA configurations)	Built-in (Multi-AZ for automatic failover)	Manual setup (custom HA solutions)
Backup and Recovery	Self-managed (custom backup solutions)	Automated (with point-in-time recovery)	Self-managed (flexible strategies)
Security	Self-managed (custom security measures)	Managed (encryption, network isolation)	Self-managed (customizable security)
Use Case	Specialized needs (specific configurations)	General business applications (balance of ease and functionality)	Specific scenarios (cloud-agnostic or advanced Oracle features)

Key Takeaways

• Amazon EC2 offers the highest level of control and customization, suited for specialized deployments that require specific Oracle features or configurations not supported by RDS.
• Amazon RDS for Oracle provides a managed service that balances ease of use with flexibility, ideal for businesses looking for cost-effective and scalable database solutions without the need for extensive database administration.
• Custom RDS Solution is tailored for unique requirements, offering high control and flexibility, particularly for scenarios demanding cloud-agnostic deployments or leveraging advanced Oracle functionalities beyond RDS capabilities.

Strategic Recommendation

Evaluate business needs, technical requirements, and resource availability to select the most suitable deployment option. Consider Amazon RDS for its operational efficiency and cost benefits for standard applications, while EC2 or custom RDS solutions might be better suited for specialized requirements.bad

 

Check the Oracle database is Exadata

How do you check that the Oracle database is running on Exadata?

For checking we have to run the following command in SQLPLUS:

select decode(count(cell_path),0,'Non-Exadata','Exadata') "System" from v$cell;