Oracle NoSQL Database for Administrators Ed 2 — Lesson 4: Monitoring, Expansion, Rebalancing, Performance, Upgrades, and Incidents

Learning Objectives

• Explain the purpose and operating context of admin CLI, status, metrics, logs, events, and health checks.
• Apply storage-node expansion, redistribution, rebalancing, and capacity and latency, throughput, cache, heap, garbage collection, and hotspots in a controlled environment.
• Validate outcomes and troubleshoot risks involving rolling upgrade, failed plans, partitions, network faults, and administrator runbook.

Detailed Topics

• admin CLI, status, metrics, logs, events, and health checks
• storage-node expansion, redistribution, rebalancing, and capacity
• latency, throughput, cache, heap, garbage collection, and hotspots
• rolling upgrade, failed plans, partitions, network faults, and administrator runbook

Instructor Demonstration

Demonstrate admin CLI, status, metrics, logs, events, and health checks for a distributed key-value and table workload deployed, secured, expanded, and recovered across storage nodes; 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 NoSQL Database for Administrators Ed 2 exercise covering storage-node expansion, redistribution, rebalancing, and capacity and latency, throughput, cache, heap, garbage collection, and hotspots; introduce an exception involving rolling upgrade, failed plans, partitions, network faults, and administrator runbook, 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 admin CLI, status, metrics, logs, events, and health checks, storage-node expansion, redistribution, rebalancing, and capacity, latency, throughput, cache, heap, garbage collection, and hotspots, rolling upgrade, failed plans, partitions, network faults, and administrator runbook 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 Monitoring, Expansion, Rebalancing, Performance, Upgrades, and Incidents in a realistic Oracle NoSQL Database for Administrators Ed 2 scenario and defend the result with documented evidence.