Domain 5: OCI Database Management Service (20%)

Domain 5 of the 1Z0-1093-25 Oracle AI Cloud Database Services 2025 Professional exam covers the OCI Database Management service -- its architecture, enablement, fleet monitoring, performance diagnostics, SQL tuning, administration, and integration with other OCI services. At 20% of the exam (approximately 10 questions out of 50), this is one of the heaviest domains. Mastering it requires understanding both the service's capabilities and the precise boundaries between management levels, database types, and feature availability.

1. Service Overview and Architecture

What Database Management Is

OCI Database Management provides a unified cloud-native console for monitoring, performance management, tuning, and administration of Oracle databases -- both in OCI and on-premises. It is the cloud-hosted successor to Oracle Enterprise Manager for database monitoring use cases, eliminating the infrastructure overhead of running OEM while providing comparable diagnostic capabilities. (Database Management Overview)

The service is organized under Observability & Management in the OCI Console, accessed via: Console > Observability & Management > Database Management.

Supported Database Types

(Diagnostics & Management for Oracle Databases)

Exam trap: ExaDB-C@C does not support Basic Management -- only Full Management is available. Also, ExaDB-C@C uses Management Agent exclusively (not Private Endpoint). Know which database types support which connection modes.

Minimum Database Version

Database Management supports Oracle Database 11.2.0.4 and later. However, many advanced features (AWR Explorer, SQL Tuning Advisor, ADDM) require 12.2+ Enterprise Edition. The COMPATIBLE initialization parameter must be set to 12.2.0 or later for these features. (Feature Support Matrix)

How It Differs from Oracle Enterprise Manager

(Database Management FAQ)

Exam trap: Database Management does not replace OEM for non-database targets (middleware, OS, applications). If a question asks about monitoring WebLogic or managing patching orchestration across an entire estate, the answer is OEM, not Database Management.

2. Management Levels: Basic vs. Full

When enabling Diagnostics & Management, you choose between two management levels. This choice directly determines which features are available. (Enable Database Management)

(Feature Support Matrix)

Exam trap: Basic Management is genuinely useful for basic fleet monitoring and ASH Analytics / SQL Monitoring in Performance Hub. It is not a stripped-down placeholder -- it collects 15 real metrics and provides meaningful visibility. But anything involving tuning, administration, or advanced diagnostics requires Full Management.

Exam trap: PDB monitoring is only available with Full Management enabled on the parent CDB. You cannot enable Basic on a CDB and then monitor its PDBs. Full Management on the CDB is a hard prerequisite.

Standard Edition Restrictions

Full Management is available for Standard Edition databases, but with significant restrictions: Performance Hub features, Alert Logs, and AWR Explorer are not included. These are Enterprise Edition features tied to the Diagnostics and Tuning packs. (Enable Database Management)

Licensing Considerations

The advanced diagnostic features in Database Management (ADDM, AWR, SQL Tuning Advisor, Performance Hub advanced tabs) correspond to Oracle Database Diagnostics Pack and Tuning Pack functionality. When using Full Management with Enterprise Edition, these features are included in the Database Management service cost. For External (on-premises) databases, you must hold appropriate Diagnostics and Tuning pack licenses to use these features legally.

3. Enabling Database Management

Prerequisites

1. OCI IAM permissions -- manage dbmgmt-family, use database-family, manage virtual-network-family, manage secret-family
2. Network connectivity -- Private Endpoint or Management Agent configured
3. Database monitoring user -- credentials stored as OCI Vault secret
4. Vault secret -- password stored in OCI Vault; for TCPS, a wallet secret is also needed

Connection Modes

Private Endpoint (for Base DB, ExaDB-D, ExaDB-XS, Autonomous AI):

• A VNIC with private IP addresses in a VCN subnet
• Does not need to be in the same subnet as the database, but must have network connectivity to it
• Cannot span multiple VCNs
• Limits per tenancy per region: 7 single-instance endpoints, 3 RAC endpoints
• One endpoint of each type per VCN
• One endpoint can serve unlimited databases of the same type in the same VCN

Management Agent (for ExaDB-D, ExaDB-C@C, External databases):

• Software agent installed on a host with network access to the database
• Version 240628.1505 or later required for CDB-level metric collection
• For ExaDB-D: cannot change the Management Agent after initial enablement

(Private Endpoints)

Exam trap: Private Endpoint and Management Agent are not interchangeable for all database types. ExaDB-C@C only supports Management Agent. Base Database Service only supports Private Endpoint. ExaDB-D supports both. Know the mapping.

Security Rules for Private Endpoints

After creating a Private Endpoint, you must configure:

• Ingress rule on the database's subnet security list or NSG (allow traffic from Private Endpoint IP)
• Egress rule on the Private Endpoint's subnet security list or NSG (allow traffic to database)

You can use Network Security Groups (NSGs) or Security Lists. The Private Endpoint Details page displays the assigned private IP addresses needed for these rules.

Enablement Steps (Cloud Databases)

1. Navigate to Observability & Management > Database Management > Administration
2. Click "Enable Diagnostics & Management"
3. Select database type, system, home, and database name
4. Choose CDB/PDB scope (CDB and all PDBs, CDB only, all PDBs, or single PDB)
5. Configure connection: service name, protocol (TCP/TCPS), port
6. Enter monitoring user credentials (username + Vault secret)
7. Select connection mode (Private Endpoint or Management Agent)
8. Select management option (Full or Basic)
9. Submit -- monitor via Work Requests

Exam trap: Cross-region monitoring is not available. The database and the Database Management resources must be in the same OCI region.

Enablement for External Databases

External databases require an additional registration step:

1. Register the external database via the OCI External Database service
2. Create a Connector (associates a Management Agent with connection details)
3. Enable Diagnostics & Management on the registered database

For Data Guard configurations with physical standby in mounted state, the connector must be created by a monitoring user with SYSDG privilege. Without this, metric collection may stop after role switchover or failover. (Enable for External Databases)

4. IAM Policies

Database Management requires policies across multiple OCI services. (Permissions Required)

Resource Principal policy (required for the managed database to read secrets from Vault):

Allow any-user to read secret-family in compartment ABC
  where ALL {request.principal.type = dbmgmtmanageddatabase}

This policy is created automatically when you click "Add policy" during enablement. It is stored in the DBMgmt_Resource_Policy policy collection.

5. Fleet Monitoring

Fleet Summary Page

The fleet summary provides a single-page view of all managed databases in a compartment or Database Group. (Fleet Monitoring)

Key tiles on the fleet summary page:

Filtering options (left pane):

• Compartment or Database Group scope
• Database type filter (e.g., Autonomous AI)
• Lifecycle state filter (e.g., "Up")
• CDB/PDB view filter
• Tag-based filters

Time periods: Last 60 minutes (default), Last 24 hours, Last 7 days. Comparison percentages show change vs. the same period previously (e.g., "same 60 min yesterday"). A blue arrow indicates change greater than 10%; gray indicates 10% or less.

Database Groups

Database Groups let you organize managed databases from different compartments into logical groups for centralized monitoring and bulk operations. (Database Groups)

• Create a group with a name, description, and optional tags
• Add managed databases from any compartment
• Run SQL jobs against the entire group at once
• View the group on the fleet summary page (switch from Compartment to Database Group scope)

Exam trap: Database Groups work across compartments. You do not need to have all databases in the same compartment to group them. This is specifically designed for organizations that partition databases into separate compartments for IAM isolation but want unified monitoring.

6. Performance Diagnostics

Performance Hub

Performance Hub is the primary diagnostic interface for individual managed databases. It provides real-time and historical views of database activity. It requires Enterprise Edition and Full Management. (Managed Database Monitoring)

Performance Hub tabs:

(Feature Support Matrix)

Exam trap: ASH Analytics and SQL Monitoring are available at both Basic and Full management levels. If a question asks which Performance Hub features are free, these two are the answer.

ADDM Spotlight

ADDM Spotlight displays findings and recommendations from the Automatic Database Diagnostic Monitor by analyzing AWR performance snapshots (typically collected hourly). (Managed Database Monitoring)

• Retention: 8-30 days (or AWR retention period)
• Duration support in Database Management: last 8 days or less
• For longer historical analysis: use OCI Ops Insights
• Recommendation categories: All, Database Parameters, Schema Objects, SQL
• Actions from ADDM: "View SQL Details" (jumps to Performance Hub), "Run SQL Tuning Advisor," "Edit Database Parameters"
• Not available for Autonomous AI Databases
• For PDBs, requires one-time enablement (no restart needed):

ALTER SESSION SET CONTAINER=<container_name>;
ALTER SYSTEM SET AWR_PDB_AUTOFLUSH_ENABLED=TRUE;
EXEC DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS(INTERVAL=>60);

AWR Explorer

AWR Explorer lets you visualize historical performance data from AWR snapshots in chart form. You can also import AWR data from other databases into a central repository for comparison. Requires Enterprise Edition 12.2+ and Full Management.

7. SQL Tuning Advisor

SQL Tuning Advisor analyzes SQL statements using the Automatic Tuning Optimizer and provides recommendations to improve execution performance. It requires Enterprise Edition 12.2+ with COMPATIBLE parameter set to 12.2.0 or later. (SQL Tuning Advisor)

Required Privileges

GRANT ADVISOR TO <admin_user>;
GRANT CREATE JOB TO <admin_user>;
GRANT CREATE SESSION TO <admin_user>;
GRANT SELECT ANY DICTIONARY TO <admin_user>;
GRANT INHERIT ANY PRIVILEGES TO <admin_user>;
GRANT ADMINISTER SQL TUNING SET TO <admin_user>;

Recommendation Types

Running a Tuning Task

Two entry points:

1. From Performance Hub -- select SQL IDs on the ASH Analytics tab, click "Tune SQL"
2. From SQL Tuning Advisor -- click "Tune SQL" in the SQL Tuning Advisor tasks section

Input sources:

• Selected SQL statements (pre-selected from Performance Hub)
• SQL Tuning Set (STS) -- a database object containing captured SQL workload

Scope of analysis:

Implementing Recommendations

After a tuning task completes, you can implement recommendations directly from the Console:

• Implement all SQL profile recommendations -- batch implementation with optional forced matching
• Implement single SQL profile -- for individual SQL IDs
• Implement index recommendation -- creates the suggested index in a specified tablespace
• Implement statistics recommendation -- gathers the recommended statistics
• Compare explain plans -- side-by-side graphical or tabular comparison of original vs. optimized plans

Implementation runs as a SQL Job and appears in the Managed Database Jobs section.

SQL Tuning Sets

A SQL Tuning Set (STS) is a database object that groups SQL statements with execution metadata. You can create, load, and manage SQL tuning sets through Database Management. An STS serves as input to SQL Tuning Advisor for workload-level analysis.

SQL Plan Management (SPM)

Database Management provides visibility into SPM configuration and SQL plan baselines. Key capabilities:

• View and manage SPM configuration
• Monitor SQL plan baselines
• Automatic SPM Evolve Advisor (12.2+)
• Selective plan capturing (12.2+)
• High-frequency SPM Evolve (19c+ on Exadata only)
• AWR loading for plan baselines (12.2+)

Exam trap: Autonomous AI Databases support SQL Plan Management but not SPM configuration tasks. Configuration must be done differently for Autonomous.

8. Optimizer Statistics

Database Management enables monitoring and management of optimizer statistics through the Optimizer Statistics section on the Managed Database details page.

What You Can Do

• Monitor Automatic Statistics Collection jobs (status, completions, failures)
• Monitor High-Frequency Statistics collection
• Monitor Manual Statistics collection jobs
• View Optimizer Statistics Advisor task executions over the last 7 days
• Drill into individual Advisor tasks to examine findings
• Implement Advisor recommendations directly from the Console

The Optimizer Statistics Advisor is a diagnostic tool built into Oracle Database that assesses the quality of statistics, discovers problems with how statistics are gathered, and generates recommendations. Database Management surfaces these findings in the OCI Console rather than requiring direct SQL access. Requires Enterprise Edition 12.2+.

Exam trap: Optimizer Statistics Advisor is disabled by default for Autonomous AI Databases. It is active by default for External and Cloud databases with Full Management.

9. Administration Tasks

Full Management enables several administration capabilities on the Managed Database details page.

Tablespace Management

• View all tablespaces and their datafiles
• Create new tablespaces
• Add or edit datafiles
• Monitor storage allocation and utilization per tablespace
• Not available for Autonomous AI Databases (storage is auto-managed)

User Management

View database users with: account status, expiration date, profile, roles, system privileges, consumer group privileges, proxy users, and container data access. Requires specific grants on the monitoring user:

GRANT READ ON DBA_USERS TO <monitoring_user>;
GRANT READ ON DBA_ROLE_PRIVS TO <monitoring_user>;
GRANT READ ON DBA_TAB_PRIVS TO <monitoring_user>;
GRANT READ ON DBA_SYS_PRIVS TO <monitoring_user>;

Database Parameters

View and edit initialization parameters. ADDM Spotlight integrates here by providing recommendations for parameter changes.

• Not available for Autonomous AI Databases (parameters are auto-managed)

SQL Job Management

• Create and schedule SQL jobs against a single database or an entire Database Group
• Monitor job runs and executions
• Job execution metrics are tracked via the dbmgmtJobExecutionsCount metric (1-minute collection interval)
• Job output can be stored in an OCI Object Storage bucket

Alert Logs and Attention Logs

• Alert Log: XML file with chronological error messages. Displays 1000 most recent entries. Filter by level (Critical, Severe, Important) or type (Error, Warning, Notification). Supports regex search.
• Attention Log: Structured file for critical database events. Available for Enterprise Edition 21c+. Categorized by urgency (Immediate, Soon, Deferrable). Not available for Autonomous AI Databases.

10. Metrics and Alarms

Metric Namespace

All Database Management metrics are emitted in the oracle_oci_database namespace. Metrics are retained for 90 days. Minimum alarm interval is 5 minutes. (Metrics)

Basic Management Metrics (15 metrics, free)

Key Full Management Metrics (selected, additional to Basic)

Common Dimensions (all metrics)

Integration with OCI Monitoring and Alarms

Database Management metrics integrate directly with OCI Monitoring. You can:

• Build metric queries using the Monitoring service
• Create alarms that trigger when metric thresholds are breached
• Route alarm notifications via OCI Notifications (email, Slack, PagerDuty, custom HTTPS)
• Correlate with OCI Events for automation
• View alarm summaries on the fleet summary page and managed database details page
• Create Oracle-recommended alarm definitions from the managed database page

Exam trap: Alarms on the fleet summary page only display if the resourceId dimension contains the database OCID. This is an important detail -- if alarms are not appearing on fleet summary, check the dimension configuration.

11. Integration with Other OCI Services

Exam trap: For ADDM analysis beyond 8 days, you need OCI Ops Insights, not Database Management alone. Database Management ADDM Spotlight covers the last 8 days maximum.

12. Data Guard Monitoring

Database Management monitors Oracle Data Guard configurations including primary and physical standby CDBs. Key Data Guard metrics collected:

Data Guard monitoring is available on the High Availability fleet summary page and on individual managed database details pages.

Important restrictions:

• Data Guard per PDB (DGPDB) is not supported
• Physical standby in mounted state is not supported with Management Agent
• Monitoring user requires SYSDG privilege for Data Guard configurations

13. Feature Support Quick Reference by Database Version

EE = Enterprise Edition required.

14. Common Exam Traps Summary

1. Basic vs. Full: ASH Analytics and SQL Monitoring are available at Basic level. Everything else diagnostic/administrative requires Full.
2. PDB monitoring: Requires Full Management on the CDB. Cannot do Basic on CDB and then monitor PDBs.
3. ExaDB-C@C: No Basic Management option, Management Agent only (no Private Endpoint).
4. Cross-region: Not supported. Database and Database Management must be in the same region.
5. Standard Edition: Full Management exists for SE but excludes Performance Hub, Alert Logs, and AWR Explorer.
6. Autonomous AI Databases: No tablespace management, no database parameters, no Attention Log, Optimizer Statistics Advisor disabled by default.
7. Private Endpoint limits: 7 single-instance + 3 RAC per tenancy per region. One of each type per VCN.
8. ADDM history: 8 days max in Database Management. Use Ops Insights for longer.
9. SQL Tuning Advisor scope: "Limited" = no SQL profiling. "Comprehensive" = includes SQL profiling.
10. Metric namespace: oracle_oci_database (not oci_database or database_management).

References

• OCI Database Management Documentation
• Database Management Overview
• Diagnostics & Management for Oracle Databases
• Feature Support Matrix
• Enable Database Management for Oracle Cloud Databases
• Enable Database Management for External Databases
• Create Private Endpoint
• Fleet Monitoring
• Managed Database Monitoring
• Oracle Cloud Database Metrics
• SQL Tuning Advisor
• Database Groups
• IAM Permissions Required
• Database Management FAQ