Results for “okc_aqerrors_v”

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

Overview

OKC_AQERRORS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC – Contracts Core product family. It presents a flattened, read-only projection over the OKC_AQERRORS table, which stores error records generated by Oracle Advanced Queuing (AQ) operations performed on behalf of the Contracts application. In EBS 12.1.1 and 12.2.2 the object is documented as VALID, and its ETRM metadata confirms that it is a simple view whose sole referenced base object is OKC_AQERRORS (accessed through a synonym).

The view plays a diagnostic role in Contracts integration flows. When inbound or outbound messages fail during enqueue or dequeue processing, the underlying table captures the failure, and OKC_AQERRORS_V exposes that information through a stable, query-friendly interface. This allows support personnel, DBAs, and developers to investigate message failures without depending on the physical table layout, which may change between releases or patches.

Underlying Base Objects

The ETRM documentation identifies a single referenced object: the OKC_AQERRORS table, reached via a synonym. The view text confirms this relationship directly, selecting from the OKC_AQERRORS table (aliased AQEB) and applying no joins, filters, grouping, or aggregation. Consequently, the view is a straightforward one-to-one projection: each row in the view corresponds to exactly one row in OKC_AQERRORS, and no rows are added, removed, or duplicated.

The view does not introduce calculated columns, DECODE logic, or outer joins. Its value is therefore primarily one of encapsulation and naming consistency rather than transformation. Because the view is owned by APPS and references the table through a synonym, the underlying storage can be relocated or renamed without invalidating dependent reporting queries, provided the synonym remains intact.

Key Columns

• ROW_ID – The ROWID of the underlying OKC_AQERRORS row, exposing a unique physical row identifier.
• ID – The primary key of the error record in OKC_AQERRORS.
• SOURCE_NAME – Identifies the source of the message or process that generated the error.
• DATETIME – The timestamp associated with the error event, useful for chronological analysis.
• Q_NAME – The name of the Advanced Queuing queue involved in the failed operation.
• MSGID – The message identifier of the AQ message that encountered the error.
• RETRY_COUNT – The number of retry attempts recorded for the message, indicating persistent versus transient failures.
• QUEUE_CONTENTS – The payload or message content captured at the time of failure.
• CREATED_BY, CREATION_DATE – Standard EBS audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns recording the most recent update context.

Common Use Cases and Queries

A typical query retrieves recent errors for a specific queue or message:

SELECT id, source_name, datetime, q_name, msgid, retry_count
FROM   apps.okc_aqerrors_v
WHERE  q_name = :queue_name
ORDER  BY datetime DESC;

Support analysts frequently inspect the full payload of a failed message, for example:

SELECT msgid, retry_count, queue_contents
FROM   apps.okc_aqerrors_v
WHERE  msgid = :message_id;

Audit-oriented queries use the standard audit columns to trace record creation and modification:

SELECT id, created_by, creation_date, last_updated_by, last_update_date
FROM   apps.okc_aqerrors_v
WHERE  creation_date >= SYSDATE - 7;

Because the view is defined with a simple SELECT and no joins, such queries perform effectively against the base table. These patterns support error triage, retry analysis, and queue troubleshooting within Contracts Core integration processing.