Oracle Database 21c: New Features for Administrators — Lesson 3: SQL, JSON, Developer, In-Memory, Sharding, and Data-Management Features

Learning Objectives

• Explain the purpose and operating context of SQL enhancements, expressions, usability, and administrative impact.
• Apply native JSON datatype, indexing, validation, and application integration and in-memory, sharding, graph, spatial, and developer-service awareness in a controlled environment.
• Validate outcomes and troubleshoot risks involving schema design, compatibility tests, migration impact, and regression control.

Detailed Topics

• SQL enhancements, expressions, usability, and administrative impact
• native JSON datatype, indexing, validation, and application integration
• in-memory, sharding, graph, spatial, and developer-service awareness
• schema design, compatibility tests, migration impact, and regression control

Instructor Demonstration

Demonstrate SQL enhancements, expressions, usability, and administrative impact 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 native JSON datatype, indexing, validation, and application integration and in-memory, sharding, graph, spatial, and developer-service awareness; introduce an exception involving schema design, compatibility tests, migration impact, and regression control, 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 SQL enhancements, expressions, usability, and administrative impact, native JSON datatype, indexing, validation, and application integration, in-memory, sharding, graph, spatial, and developer-service awareness, schema design, compatibility tests, migration impact, and regression control 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 SQL, JSON, Developer, In-Memory, Sharding, and Data-Management Features in a realistic Oracle Database 21c: New Features for Administrators scenario and defend the result with documented evidence.