Lesson 6

In Oracle 23c, Oracle Enterprise Manager (OEM) Cloud Control continues to serve as the primary enterprise-grade monitoring and management interface for administering Oracle databases, including Oracle 23c on-premises, in Oracle Cloud Infrastructure (OCI), and hybrid environments.
Here is how OEM Cloud Control is used with Oracle 23c:

1. Centralized Monitoring and Performance Management
   • Monitors Oracle 23c databases for:
     • Wait events, I/O statistics, session activity, memory usage
     • Real-time and historical performance metrics
   • Supports automatic performance diagnostics via:
     • ADDM (Automatic Database Diagnostic Monitor) ^[1]
     • ASH (Active Session History)
     • AWR (Automatic Workload Repository) ^[2]
   • Alerts and thresholds can be set for metrics like:
     • Tablespace usage
     • Query response time
     • CPU and memory consumption
2. 23c Multitenant Architecture Support (CDB/PDB)
   • OEM Cloud Control natively supports 23c Container Databases (CDBs) and Pluggable Databases (PDBs)
   • Enables:
     • PDB-level performance tracking
     • Cross-PDB resource usage comparisons
     • Managing Resource Manager plans across PDBs
   • Visual tools for:
     • Plug/unplug PDBs
     • Monitor PDB availability and metrics

SQL Monitoring and Tuning with 23c Enhancements

• Real-time SQL monitoring tracks:
  • Long-running SQL
  • Execution plan statistics
  • Bind variable analysis
• Integrates with:
  • SQL Tuning Advisor
  • SQL Access Advisor
• Supports new 23c SQL syntax and features, including:
  • Boolean columns
  • JSON Relational Duality Views
  • Annotations for hints

Automated Maintenance and Patch Management

• Schedule automated backups, stats collection, and data masking operations
• Apply patches and updates to Oracle 23c databases via:
  • Fleet Maintenance
  • OPatch integration
  • Provisioning and patching lifecycle plans

Security and Compliance in Oracle 23c

• Centralized view of 23c user privileges, roles, and audit trails
• Integrates with:
  • Unified Audit Trail
  • Database Vault
  • Data Safe
• Reports on Security Baseline Score and GDPR compliance metrics

REST and Cloud Integration

• OEM provides REST endpoints to automate 23c database operations
• Monitors Oracle 23c in OCI, including:
  • Exadata Cloud@Customer
  • Autonomous databases (read-only mode in some cases)
• Integrates with Oracle Management Cloud (OMC) for ML-based anomaly detection (optional extension)

 OEM Cloud Control
    ├── Targets → Oracle 23c CDBs and PDBs
    ├── Performance → AWR, ADDM, SQL Monitor
    ├── Security → Audit Trails, Roles, Compliance
    ├── Jobs → Backup, Stats Gathering, Patching
    ├── Fleet → Patch 23c at scale
    └── Dashboards → Reports for DBAs, Security Teams, CIOs

📌 Key Takeaway:
Oracle Enterprise Manager Cloud Control is fully compatible with Oracle 23c, making it the ideal tool for:

• Managing hybrid and multicloud deployments
• Tuning and optimizing new 23c features
• Simplifying CDB/PDB lifecycle operations
• Ensuring security, compliance, and performance

In Oracle 23c, the traditional fat client vs. thin client distinction has largely been superseded by modern connectivity models, cloud-native architecture, and multi-tier service paradigms. Here's how each has evolved or been replaced:
🧱 1) Fat Clients → Replaced by Browser-Based and Lightweight Desktop Interfaces
🔹 What were Fat Clients?

• Applications installed on user machines
• Contained business logic and user interface
• Connected directly to the Oracle database (often via OCI or SQL*Net)
• Required Oracle Client libraries (e.g., sqlplus, forms)

🔁 Modern Replacements in Oracle 23c

Legacy (Fat Client)	Replacement (Oracle 23c & Cloud)
Oracle Forms Desktop	✅ Oracle APEX (Application Express) (web-based)
SQL Developer (thick)	✅ SQL Developer Web (runs inside Oracle REST Data Services)
Custom VB/Java thick apps	✅ RESTful Web Services, GraphQL, or gRPC APIs
Direct client-to-DB links	✅ Middle tiers (e.g., App Servers or Microservices)

🔸 In Oracle 23c, APEX + REST APIs + ORDS is the standard replacement stack for fat client apps.
🧬 2) Thin Clients → Evolved into Microservices, REST APIs, and Containerized Access
🔹 What were Thin Clients?

• GUI front ends with no business logic
• Relied on centralized application servers
• Used JDBC Thin Driver or Web-based HTTP requests

Legacy (Thin Client)	Replacement (Oracle 23c & Cloud-Native)
JDBC Thin Clients	✅ Still supported, but now optimized for Autonomous DB and OCI
HTTP-based clients	✅ Replaced by RESTful APIs via ORDS
App Servers with JDBC	✅ Now often use Microservices with containerized DB access
Web Forms	✅ Replaced by Oracle APEX, React/Vue frontends, or PL/SQL Web Toolkit

🔸 In Oracle 23c, the "thin client" role is fulfilled by stateless services consuming REST APIs, often deployed via Docker/Kubernetes.
🧠 Conceptual Shift in Oracle 23c

Legacy Paradigm	Modern Paradigm in Oracle 23c
Fat Client vs Thin Client	🆕 Service-Oriented + API-Driven Architecture
Direct DB Access	🆕 RESTful Gateway (ORDS) or GraphQL
Local processing	🆕 Database-side PL/SQL logic or APEX Apps
Installed software	🆕 Zero-install browser tools (SQL Dev Web)

Component	Replaces	Description
Oracle APEX	Oracle Forms/Fat GUI	Low-code web app builder, runs in browser
Oracle REST Data Services	OCI/Thick JDBC clients	Exposes DB objects via RESTful API, deployable via Tomcat/Jetty
SQL Developer Web	Thick SQL Dev client	Browser-based SQL IDE integrated with Autonomous DB and ORDS
JSON Duality Views	Custom ETL to APIs	Directly expose tables as JSON via SQL or REST

✅ Conclusion:
The fat vs. thin client model has been replaced by a cloud-native, API-first architecture in Oracle 23c. Clients are now:

• Stateless and browser-based
• Interfacing via REST or GraphQL
• Often running in containers or serverless environments

1. Batch Job: A process executed without any user interaction on a predefined schedule
2. Event: A threshold activity that can be detected by the Intelligent Agent and monitored by the Enterprise Manager
3. Fat Client: The client computer holds a portion of the application system you install
4. Thin Client: The client computer does to need to store any part of the application system
5. Registered Event: A predefined event scheduled and monitored by the Enterprise Manager

In the next module, you will learn about some important changes in security enforcement that allow your database and your Internet Web site to share their security setup.

[1]ADDM (Automatic Database Diagnostic Monitor) : In Oracle 23c, ADDM (Automatic Database Diagnostic Monitor) is an integral diagnostic tool that automatically analyzes performance data captured in the Automatic Workload Repository (AWR). It identifies root causes of database performance problems, provides recommendations for their correction, and quantifies the expected benefits of implementing those recommendations.

[2]AWR (Automatic Workload Repository):In Oracle 23c, the Automatic Workload Repository (AWR) is a built-in feature that automatically collects, processes, and maintains performance statistics for your database. This data is stored in snapshots, which provide a historical view of database activity, crucial for identifying performance issues and self-tuning the database over time.