Oracle AI Database: New Features for Developers Live Class — Lesson 2: JSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage

Learning Objectives

• Explain how jSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage changes the end-to-end technical or business process.
• Configure jSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage with explicit inputs, controls, outputs, exceptions, and rollback points.
• Prove the implementation using SQL and API test results and document unresolved risk.

Detailed Topics

• JSON Relational Duality
• JSON collections
• document-relational access
• transactions
• schema evolution
• API usage
• Ownership, prerequisites, data, and acceptance criteria for jSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage
• Security, control, integration, performance, recovery, compliance, and support implications

Instructor Demonstration

Demonstrate jSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage within an application team evaluating and adopting Oracle AI Database developer features with secure, testable, and supportable implementation patterns. Use representative data and capture SQL and API test results so another practitioner can reproduce and verify the result.

Hands-On Exercise

Complete a controlled activity focused on jSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage. Introduce a realistic case of incorrect JSON or vector query behavior, isolate the cause, apply a reversible correction, and rerun the acceptance checks.

1. Record the requirement, environment, identities, dependencies, data, controls, and expected result.
2. Perform the workflow and capture course-specific evidence before and after each material change.
3. Test normal, boundary, failure, security, reconciliation, recovery, and operational conditions.
4. Document the root cause, correction, rollback, owner, support action, and next improvement priority.

Scenario Analysis

• Map the process from initiating condition through each transformation to the final output.
• Locate the control point most likely to prevent or expose incorrect JSON or vector query behavior.
• Recommend monitoring, escalation, and operational handover requirements.

Troubleshooting Guidance

When jSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage does not produce the expected result, confirm scope, effective dates, identities, data context, dependencies, and recent changes. Review SQL and API test results before modifying configuration or data. Test one reversible hypothesis at a time, verify recovery, and confirm that the fix does not create a new control, security, performance, compliance, or integration defect.

Validation Checklist

• Prerequisites, ownership, data context, settings, and expected outcomes are documented.
• The result is reproducible and supported by SQL and API test results.
• Security, controls, data quality, integration, performance, recovery, compliance, and support conditions are reviewed.
• Exceptions, corrective action, rollback, approvals, monitoring, and handover are recorded.

Lesson Outcome

Learners can apply JSON Relational Duality, JSON collections, document-relational access, transactions, schema evolution, API usage in a realistic Oracle AI Database: New Features for Developers Live Class situation and defend the result with course-specific evidence.