Oracle Database 19c: Data Warehousing Concepts — Lesson 2: Dimensional Modeling, Facts, Dimensions, Stars, Snowflakes, and History

Learning Objectives

• Explain the architecture, workflow, or business purpose behind transaction, periodic snapshot, accumulating snapshot, and factless facts.
• Apply conformed, role-playing, junk, degenerate, and slowly changing dimensions and star and snowflake schemas, surrogate keys, hierarchies, and aggregates in a controlled scenario.
• Validate outcomes and troubleshoot risks involving model validation, unknown members, late-arriving data, and semantic consistency.

Detailed Topics

• transaction, periodic snapshot, accumulating snapshot, and factless facts
• conformed, role-playing, junk, degenerate, and slowly changing dimensions
• star and snowflake schemas, surrogate keys, hierarchies, and aggregates
• model validation, unknown members, late-arriving data, and semantic consistency

Instructor Demonstration

Demonstrate transaction, periodic snapshot, accumulating snapshot, and factless facts within an enterprise sales analytics warehouse defined from business questions through trusted dimensional delivery, then capture the exact configuration, command, transaction, report, model, query, code, or process evidence that proves the result for lesson 2.

Hands-On Exercise

Implement a controlled exercise covering conformed, role-playing, junk, degenerate, and slowly changing dimensions and star and snowflake schemas, surrogate keys, hierarchies, and aggregates, then introduce and resolve an exception involving model validation, unknown members, late-arriving data, and semantic consistency while preserving before-and-after evidence.

1. Confirm the environment, identities, inputs, dependencies, risks, and expected outcome.
2. Complete the course-specific configuration, development, analysis, or process workflow.
3. Capture settings, commands, data, outputs, logs, reports, screenshots, calculations, or test results.
4. Compare the observed result with acceptance criteria and document corrective action.

Scenario Analysis

• Identify the technical or business decision that must be made.
• Compare valid approaches and their security, performance, reliability, cost, compliance, and support trade-offs.
• Define rollback, recovery, ownership, communication, and evidence requirements.

Troubleshooting Guidance

Diagnose issues across transaction, periodic snapshot, accumulating snapshot, and factless facts, conformed, role-playing, junk, degenerate, and slowly changing dimensions, star and snowflake schemas, surrogate keys, hierarchies, and aggregates, model validation, unknown members, late-arriving data, and semantic consistency without making an unverified production change. Separate symptoms from causes, gather evidence, test the smallest reversible correction, rerun validation, and record preventive action.

Validation Checklist

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

Lesson Outcome

Learners can apply Dimensional Modeling, Facts, Dimensions, Stars, Snowflakes, and History in a realistic Oracle Database 19c: Data Warehousing Concepts scenario and validate the result with documented evidence.