Oracle Autonomous Database Workshop 2024 ELS — Lesson 1: Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity

Learning Objectives

• Translate a realistic requirement into an executable approach for Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity.
• Use provisioned database and connectivity verification to verify completeness, access, and process behaviour.
• Explain how to recover safely when wallet or TLS configuration preventing a client connection occurs.

Detailed Topics

• Autonomous Database concepts
• Licensing
• Infrastructure
• Workload selection
• Provisioning
• And connectivity
• Decision ownership, prerequisites, and acceptance evidence for Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity from requirement through execution and review. Learners see where evidence should be collected, how provisioned database and connectivity verification supports verification, and which warning signs demand investigation.

Hands-On Exercise

Complete a guided task covering Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity. After establishing a working baseline, reproduce “wallet or TLS configuration preventing a client connection,” isolate the responsible setting or data condition, apply a reversible fix, and update provisioned database and connectivity verification with before-and-after proof.

1. Define the requirement and identify dependencies before changing the environment.
2. Create a baseline result that can be compared with later changes.
3. Reproduce the exception and test one hypothesis at a time.
4. Complete the evidence record and obtain peer or instructor review.

Scenario Analysis

• Clarify the business trigger, affected roles, required records, and acceptable result for Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how provisioned database and connectivity verification should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid editing multiple settings at once when troubleshooting Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity. Preserve the failing example, review provisioned database and connectivity verification, and verify whether “wallet or TLS configuration preventing a client connection” is the root cause. After remediation, repeat the transaction, confirm downstream effects, and record any monitoring action.

Validation Checklist

• Prerequisites and role permissions for Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity have been confirmed before execution.
• The result agrees with the expected values documented in provisioned database and connectivity verification.
• Exceptions are explained with evidence rather than hidden by manual correction.
• The final record names the approver, monitoring point, and next improvement action.

Lesson Outcome

Learners can apply Autonomous Database concepts, licensing, infrastructure, workload selection, provisioning, and connectivity, explain the decisions made, and defend the result with provisioned database and connectivity verification.