Results for “cz_db_logs”

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

Overview

CZ_DB_LOGS is a Configurator (CZ) module table owned by the CZ schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Log reporting table," and it functions as the diagnostic and audit logging surface for the Configurator runtime engine. Whenever the Configurator processes a model selection, executes a rules invocation, performs a model conversion, or communicates with a Configurator server node, the runtime writes a row to CZ_DB_LOGS capturing the caller, urgency, status code, and free-text message. Because the table records events that occur across a distributed Configurator deployment, it is typically the first place administrators and support engineers look when diagnosing configuration failures, slow model instantiation, or inter-node communication errors.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table hangs off two parent entities — CZ_XFR_RUN_INFOS (through RUN_ID) and CZ_PS_NODES (through PS_NODE_ID) — and carries descriptive, non-key attributes such as URGENCY, MESSAGE, STATUSCODE, and ERROR_STACK. This is characteristic of a satellite attached to a run or node hub, rather than a standalone hub or a many-to-many link. Treating it as a satellite is a modeling suggestion only; the physical table is a conventional transactional logging table with no enforced uniqueness beyond its surrogate key.

Key Information Stored

• LOGTIME / LOGUSER — The timestamp and database user recorded at the moment the log entry was written. These two columns form the primary temporal and attribution axis for any log review.
• URGENCY — Severity or priority classification of the entry. This is the primary filter column for isolating errors from routine informational messages.
• STATUSCODE — Numeric or coded outcome of the logged operation, allowing aggregation of success versus failure rates without parsing text.
• CALLER / MESSAGE / MESSAGE_ID — The calling program or routine, the human-readable message text, and the message identifier used for lookup against the message repository and translation layer.
• RUN_ID — Foreign key to CZ_XFR_RUN_INFOS. This ties each log line to a specific Configurator run, which is the single most important join for run-level reporting.
• PS_NODE_ID — Foreign key to CZ_PS_NODES. Identifies the Configurator server node that produced the entry in a multi-node deployment.
• SESSION_ID — The user or runtime session that generated the log entry, enabling end-to-end tracing of a single configuration session.
• MODEL_ID / MODEL_CONVERSION_SET_ID / RULE_ID — Identifiers for the model, conversion set, and rule involved, providing the business context of the logged event.
• OBJECT_ID / OBJECT_TYPE / ELEMENT_ID / ELEMENT_TYPE — Generic object and element references that pinpoint the specific configuration component being processed when the entry was created.
• ERROR_STACK — The captured error stack for exception conditions. This is the highest-value column when performing root-cause analysis.
• CREATED_BY / CREATION_DATE — Standard EBS audit columns. Note that these may differ from LOGTIME and LOGUSER when rows are inserted by a background process on behalf of another user.

The surrogate primary key is the row identifier implied by the logging insert; the columns most qualified as business-key candidates for querying are LOGTIME, SESSION_ID, RUN_ID, and PS_NODE_ID, which together describe when, where, and for whom an event occurred.

Common Use Cases and Queries

The dominant use case is run-level error triage. A support engineer joins CZ_DB_LOGS to CZ_XFR_RUN_INFOS on RUN_ID to reconstruct the full sequence of events for a failed configuration run:

• Retrieve all rows for a given run ordered by LOGTIME to reconstruct the execution timeline.
• Filter on URGENCY or STATUSCODE to surface only errors and warnings for a date range.
• Group by PS_NODE_ID to confirm whether a fault is isolated to one Configurator server node or affects the whole cluster.
• Search ERROR_STACK for a known exception signature, such as a Java class name, to find recurring defect patterns across runs.
• Group by MESSAGE_ID or MESSAGE to identify the highest-frequency failure messages over a reporting period, which supports trend reporting and targeted remediation.
• Trace a single SESSION_ID across MODEL_ID and OBJECT_ID to follow a user's configuration path through the model hierarchy.

Because the table is append-only and can grow large in high-volume Configurator implementations, queries should always be bounded by LOGTIME or RUN_ID rather than scanned in full. Archival and purge routines are typically scheduled against LOGTIME.

Related Objects

• CZ_XFR_RUN_INFOS — Parent of CZ_DB_LOGS via RUN_ID → CZ_XFR_RUN_INFOS. The primary join for run-level diagnostics.
• CZ_PS_NODES — Parent of CZ_DB_LOGS via PS_NODE_ID → CZ_PS_NODES. Provides node identification for distributed Configurator deployments, and the definitive note that CZ_DB_LOGS carries at least two foreign keys.
• CZ Models and Model Structures — Referenced indirectly through MODEL_ID. Model metadata tables supply the model name and context for a given log entry.
• CZ Rules — Referenced through RULE_ID. Rule definitions identify which rule fired or failed when a log entry is associated with rule execution.
• CZ Model Conversion Sets — Referenced through MODEL_CONVERSION_SET_ID, supporting analysis of conversion-related failures.
• FND Messages / Message Repository — Referenced conceptually through MESSAGE_ID; resolves message text and translation for reporting.
• FND Logging and Concurrent Manager — Parallel logging infrastructure; concurrent requests that invoke Configurator processing can be correlated through SESSION_ID and RUN_ID to link database log entries with concurrent program output.

No dependent child tables or public APIs are documented for CZ_DB_LOGS, consistent with its role as a terminal logging consumer rather than a master data source. Access is normally read-only for reporting and administrative purposes.