Oracle BI 12c: Create Analyses and Dashboards Ed 2 — Lesson 1: Catalog, Subject Areas, and Analysis Foundations

Technical Scope

• Oracle BI home, catalog folders, subject areas, presentation tables, and columns
• analysis criteria, column properties, sorting, totals, and result validation
• saved analyses, permissions, favorites, catalog searches, and object organization
• data grain, null behavior, duplicate rows, and trustworthy query interpretation

Instructor Demonstration

The instructor traces Oracle BI home, catalog folders, subject areas, presentation tables, and columns, then connects it to analysis criteria, column properties, sorting, totals, and result validation. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners complete a controlled exercise that applies analysis criteria, column properties, sorting, totals, and result validation and saved analyses, permissions, favorites, catalog searches, and object organization. The exercise introduces a realistic exception related to data grain, null behavior, duplicate rows, and trustworthy query interpretation and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of saved analyses, permissions, favorites, catalog searches, and object organization, traceable proof for Oracle BI home, catalog folders, subject areas, presentation tables, and columns, and a repeatable recovery path for data grain, null behavior, duplicate rows, and trustworthy query interpretation. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when data grain, null behavior, duplicate rows, and trustworthy query interpretation occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested catalog, subject areas, and analysis foundations implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.