Oracle Database 21c: New Features for Administrators — Lesson 2: Security, Availability, Backup, Recovery, Data Guard, and Blockchain Features

Learning Objectives

• Explain the purpose and operating context of authentication, privilege, auditing, encryption, and security enhancements.
• Apply Data Guard, broker, failover, recovery, and availability improvements and RMAN, backup, restore, and recovery enhancements in a controlled environment.
• Validate outcomes and troubleshoot risks involving blockchain tables, immutable data concepts, retention, and governance.

Detailed Topics

• authentication, privilege, auditing, encryption, and security enhancements
• Data Guard, broker, failover, recovery, and availability improvements
• RMAN, backup, restore, and recovery enhancements
• blockchain tables, immutable data concepts, retention, and governance

Instructor Demonstration

Demonstrate authentication, privilege, auditing, encryption, and security enhancements for a 19c estate assessed and tested for selective adoption of Oracle Database 21c capabilities; capture the exact configuration, code, command, transaction, query, dashboard, model, schedule, or report evidence that proves the expected result.

Hands-On Exercise

Complete a controlled Oracle Database 21c: New Features for Administrators exercise covering Data Guard, broker, failover, recovery, and availability improvements and RMAN, backup, restore, and recovery enhancements; introduce an exception involving blockchain tables, immutable data concepts, retention, and governance, diagnose it from evidence, apply the smallest reversible correction, and rerun acceptance checks.

1. Confirm scope, prerequisites, identities, dependencies, data, risks, and expected outcome.
2. Perform the course-specific configuration, development, administration, analysis, or business-process workflow.
3. Capture commands, settings, records, logs, screenshots, reports, metrics, or test results.
4. Compare the observed result with acceptance criteria and document corrective or preventive action.

Scenario Analysis

• Identify the technical or business decision and the stakeholders affected by it.
• Compare security, performance, reliability, compliance, cost, usability, and support trade-offs.
• Define rollback, recovery, communication, evidence, ownership, and escalation requirements.

Troubleshooting Guidance

Diagnose issues involving authentication, privilege, auditing, encryption, and security enhancements, Data Guard, broker, failover, recovery, and availability improvements, RMAN, backup, restore, and recovery enhancements, blockchain tables, immutable data concepts, retention, and governance without making an unverified production change. Separate symptoms from causes, gather time-correlated evidence, test a reversible hypothesis, validate the correction, and record recurrence controls.

Validation Checklist

• The requirement, environment, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by product-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, support actions, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply Security, Availability, Backup, Recovery, Data Guard, and Blockchain Features in a realistic Oracle Database 21c: New Features for Administrators scenario and defend the result with documented evidence.