Results for “html_alive_status”

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

Overview

CZ_TERMINATE_MSGS is a Configurator (CZ) module table in the Oracle E-Business Suite, owned by the CZ schema. Its documented description identifies it as a store for "XML terminate messages," meaning it holds the message payloads persisted when a Configurator runtime session, configuration model, or related UI component is terminated. In EBS 12.1.1 and 12.2.2 the Configurator is the engine behind Oracle Configurator and its integration with order capture and quoting; termination messages form part of the diagnostic and lifecycle signalling that the runtime performs when a configuration session ends, whether cleanly or because a user action, timeout, or application/applet failure forces a shutdown.

The table is small by Configurator standards (five documented columns) and is classified heuristically as standalone from its foreign-key structure. In Data Vault terms this suggests modeling it as its own hub, with the message identifier acting as the business key, rather than as a satellite attached to a parent Configurator entity. No inbound or outbound FK relationships are documented in the ETRM 12.2.2 schema extract.

Key Information Stored

The documented physical schema contains five columns on the composite primary key CZ_TERMINATE_MSGS_PK:

• MSG_ID — the message identifier. It is the leading column of the composite primary key and of the unique index CZ_TERMINATE_MSGS_PK, making it the principal business-key candidate. It groups together the individual message fragments belonging to one termination event.
• SEQ_NBR — the sequence number that, combined with MSG_ID, forms the surrogate/business composite key. It orders message lines or fragments so that a multi-part termination message can be reassembled in the intended sequence.
• MSG_TEXT — the XML terminate message content itself; the payload that carries the termination detail emitted by the Configurator.
• HTML_ALIVE_STATUS — status flag capturing the liveliness/availability state of the HTML (browser-side) Configurator client at the point of termination.
• APPLET_ALIVE_STATUS — the equivalent status flag for the Java applet client, reflecting the older applet-based Configurator UI still relevant in 12.1.1 deployments.

The two ALIVE_STATUS columns allow support and development staff to distinguish which client technology was active and whether it was still responsive when the termination message was written.

Common Use Cases and Queries

The table is primarily a diagnostic resource. Typical scenarios include troubleshooting Configurator sessions that terminate unexpectedly, confirming whether an HTML or applet client was still alive at the time of termination, and auditing the volume of termination events over a period.

• Retrieve all fragments for a single termination event, ordered by sequence: SELECT MSG_ID, SEQ_NBR, MSG_TEXT FROM CZ.CZ_TERMINATE_MSGS WHERE MSG_ID = :msg_id ORDER BY SEQ_NBR;
• Count termination events and split them by client technology: SELECT HTML_ALIVE_STATUS, APPLET_ALIVE_STATUS, COUNT(DISTINCT MSG_ID) FROM CZ.CZ_TERMINATE_MSGS GROUP BY HTML_ALIVE_STATUS, APPLET_ALIVE_STATUS;
• Search message bodies for specific error or model tokens: SELECT MSG_ID, SEQ_NBR FROM CZ.CZ_TERMINATE_MSGS WHERE UPPER(MSG_TEXT) LIKE '%MODEL%';
• Detect the most recent terminations, joining MSG_ID to any Configurator session or log table that shares the identifier.

Related Objects

ETRM documents CZ_TERMINATE_MSGS_PK as the only unique index and reports no foreign-key relationships, so the table is effectively independent within the CZ schema. The most significant associated objects are therefore the Configurator runtime tables and APIs that share the MSG_ID identifier space rather than strict parent/child constraints. Practically, these include the CZ session/runtime tables and the Configurator server-side APIs invoked during session teardown, along with the CZ_* message and log tables that record parallel runtime diagnostics. Because no documented join columns exist beyond the local CZ_TERMINATE_MSGS_PK, any correlation with these objects must be confirmed against the actual MSG_ID values populated by the Configurator runtime; the MSG_ID and SEQ_NBR pair should be treated as the authoritative join key for intra-table retrieval.