Search Results cz_xfr_run_infos_pk




Overview
Explore in AI Chat

Overview

The CZ.CZ_XFR_RUN_INFOS table is a core repository for summary-level metadata and status tracking of batch processing operations within the Oracle Configurator module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a central log for critical batch runs, including model import, logic generation, user interface generation/refresh, and publication. This table is essential for system administrators and functional users to monitor the execution, progress, and completion status of these resource-intensive processes, providing a historical audit trail and a means to diagnose issues related to Configurator data management.

Key Information Stored

The table's columns capture the lifecycle and outcome of a batch run. The primary identifier, RUN_ID, is a unique sequence number for each execution. Temporal data is stored in STARTED and LAST_ACTIVITY DATE columns, which track initiation and the most recent status update, respectively. The COMPLETED flag, where '1' indicates the run has finalized, provides a quick status check. The LABEL column (VARCHAR2(20)) is crucial for distinguishing the type of run, such as 'Import', 'Publish', or 'Purge'. For import operations specifically, LOAD_PATH and LOAD_STATE indicate the source directory and the next processing phase. Error management is supported by the TOTAL_ERRORS NUMBER column, while free-form NOTES (VARCHAR2(2000)) allow for additional descriptive context.

Common Use Cases and Queries

A primary use case is monitoring active or recently completed batch jobs to ensure successful system operation. Administrators frequently query this table to identify failed runs (high TOTAL_ERRORS or COMPLETED not equal to '1' for stale jobs) or to audit the history of model publications. A typical monitoring query would filter on recent STARTED dates and order by RUN_ID descending. The table is also central to troubleshooting; the RUN_ID from CZ_XFR_RUN_INFOS is used to join with detailed log tables like CZ_DB_LOGS to investigate specific errors. The standard query pattern, as indicated in the metadata, is:

  • SELECT RUN_ID, STARTED, LAST_ACTIVITY, TOTAL_ERRORS, COMPLETED, LOAD_PATH, LOAD_STATE, LABEL, NOTES FROM CZ.CZ_XFR_RUN_INFOS WHERE LABEL = 'Import' ORDER BY RUN_ID DESC;

Related Objects

CZ_XFR_RUN_INFOS acts as a parent table in several key relationships via its primary key, CZ_XFR_RUN_INFOS_PK (RUN_ID). It is referenced by the following foreign keys, creating a linked data model for Configurator batch processing:

  • CZ_DB_LOGS.RUN_ID: References this table to associate detailed diagnostic log entries with a specific high-level run record.
  • CZ_DB_SIZES.RUN_ID: References this table to link database sizing metrics or statistics captured during a batch operation to its run summary.
  • CZ_XFR_PROJECT_BILLS.LAST_IMPORT_RUN_ID: References this table to track the most recent import run ID associated with a specific Configurator project bill, linking transactional data to its processing history.