Search Results cz_db_sizes




Overview
Explore in AI Chat

Overview

The CZ_DB_SIZES table is a core data object within the Oracle E-Business Suite (EBS) Configurator (CZ) module. Functioning as a record-counts table, its primary role is to store quantitative metrics about the data volume within the Configurator schema. It is instrumental during data migration, system analysis, and performance auditing processes. Specifically, it captures snapshot metrics tied to individual migration or transformation runs, enabling administrators and functional consultants to track the scale of configuration data, validate the completeness of data loads, and perform capacity planning. Its existence is critical for maintaining data integrity and providing audit trails for the complex configuration models managed by the Oracle Configurator.

Key Information Stored

The table stores metric data keyed by a specific run identifier and a table name. Based on the provided metadata, the primary key is a composite of RUN_ID and TABLE_NAME, ensuring unique metric records per table for each execution. The essential columns include:

  • RUN_ID: A foreign key linking to the CZ_XFR_RUN_INFOS table. This identifies the specific data transformation or migration execution batch for which the metrics were collected.
  • TABLE_NAME: The name of the CZ schema table (e.g., CZ_MODELS, CZ_CONFIG_ITEMS) whose data metrics are being recorded.
  • METRIC_NAME: Defines the type of metric captured. While the exact values are not detailed in the excerpt, this column typically holds descriptors such as 'RECORD_COUNT', 'STORAGE_SIZE', or other quantitative measures relevant to the associated TABLE_NAME.

The table likely includes additional columns to store the actual metric value (e.g., a NUMBER column like METRIC_VALUE) and possibly timestamps, though these are not explicitly listed in the provided structure.

Common Use Cases and Queries

The primary use case for CZ_DB_SIZES is post-migration validation and reporting. After a Configurator data load or transformation run, queries against this table verify that the expected volume of data was processed. A common analytical query compares record counts across different RUN_IDs to track data growth or identify anomalies in specific tables. For example, a DBA might execute a query to summarize the latest migration's impact:

SELECT TABLE_NAME, METRIC_NAME, METRIC_VALUE FROM CZ.CZ_DB_SIZES WHERE RUN_ID = (SELECT MAX(RUN_ID) FROM CZ.CZ_XFR_RUN_INFOS) ORDER BY TABLE_NAME;

Another critical use case is performance diagnostics. Unusually high record counts in specific transactional tables, as logged in CZ_DB_SIZES, can pinpoint tables that may require indexing or purging of historical data. Reports built on this table are essential for system health checks and planning upgrade or archival projects.

Related Objects

The CZ_DB_SIZES table has a direct and dependent relationship with the CZ_XFR_RUN_INFOS table, as defined by its foreign key constraint. The CZ_XFR_RUN_INFOS table stores high-level metadata about each transformation run, such as start time, end time, and status. Therefore, CZ_DB_SIZES provides the detailed quantitative results for a parent run record in CZ_XFR_RUN_INFOS. This relationship is fundamental for constructing complete audit reports. The table is intrinsically related to all major transactional and master data tables within the CZ schema (e.g., CZ_MODELS, CZ_CONFIG_ITEMS, CZ_RULES) whose names populate the TABLE_NAME column. It serves as a central repository for their volumetric metadata.