Results for “total_errors”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CZ_XFR_RUN_INFOS table resides in the CZ schema and belongs to the Oracle Configurator (CZ) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores summary information about batch runs executed by the Configurator's transfer and loading utilities. Each row captures a single batch execution, recording timing, error counts, load path details, and completion state. The table functions as a run-registry or control record for bulk data movement operations, allowing administrators and concurrent programs to track the status of import, export, and data-generation jobs.

From a Data Vault modeling perspective, the metadata's heuristic classification identifies this table as hub-leaning. This suggests treating RUN_ID as a hub business key that anchors run-level identity, with the remaining descriptive attributes (timing, error counts, load state) optionally normalized into an associated satellite. In practice, the flat structure supports straightforward operational querying without requiring joins across multiple dependent tables.

Key Information Stored

The table contains nine documented columns. The most significant are:

• RUN_ID — The surrogate primary key, defined by the unique index CZ_XFR_RUN_INFOS_PK. It uniquely identifies each batch run and serves as the anchor for all foreign key relationships.
• STARTED — Timestamp marking when the batch run began execution.
• LAST_ACTIVITY — Timestamp of the most recent activity, useful for detecting stalled or long-running jobs.
• COMPLETED — Indicator or timestamp reflecting whether the run finished, allowing distinction between in-progress and terminated runs.
• TOTAL_ERRORS — Aggregate count of errors encountered during the run, a primary health metric.
• LOAD_PATH — Identifies the source or target path used during the load operation.
• LOAD_STATE — Current state of the load process, supporting status-driven reporting.
• LABEL — A human-readable descriptor for the run, useful in reports.
• NOTES — Free-form commentary recorded by the process or administrator.

The unique index on RUN_ID is the only documented business-key candidate; no separate natural key column is defined, so RUN_ID serves both as surrogate and business identifier.

Common Use Cases and Queries

Typical usage centers on monitoring batch health, diagnosing failures, and correlating runs with their detailed log entries. A common query retrieves recent runs with elevated error counts:

• SELECT RUN_ID, STARTED, COMPLETED, TOTAL_ERRORS, LOAD_STATE FROM CZ.CZ_XFR_RUN_INFOS WHERE TOTAL_ERRORS > 0 ORDER BY STARTED DESC;
• Detecting stalled runs: compare LAST_ACTIVITY against SYSDATE for rows where COMPLETED is null.
• Auditing load paths and labels for capacity or configuration review: SELECT LOAD_PATH, LABEL, COUNT(*) FROM CZ.CZ_XFR_RUN_INFOS GROUP BY LOAD_PATH, LABEL;
• Joining to CZ_DB_LOGS to retrieve detailed messages for a specific run.

These queries support DBA dashboards, concurrent program monitoring, and post-mortem analysis of failed Configurator imports.

Related Objects

The table participates in several documented foreign key relationships:

• CZ_DB_LOGS — References CZ_XFR_RUN_INFOS.RUN_ID via CZ_DB_LOGS.RUN_ID, supplying detailed log messages for each run.
• CZ_DB_SIZES — References CZ_XFR_RUN_INFOS.RUN_ID via CZ_DB_SIZES.RUN_ID, capturing size metrics associated with the run.
• CZ_XFR_PROJECT_BILLS — References the run table via LAST_IMPORT_RUN_ID, linking project bill records to the import run that last processed them.

Together these dependents make CZ_XFR_RUN_INFOS a central hub for Configurator batch telemetry, with RUN_ID acting as the shared join key across logging, sizing, and project-bill entities.