Search Results retry_count

Overview

APPS.OKC_QUE_ERROR_CNT_V is a reporting view in Oracle E-Business Suite that surfaces error records captured from Advanced Queuing (AQ) activity associated with the Oracle Contracts (OKC) module. It is defined in the APPS schema and is shipped identically across EBS 12.1.1 and 12.2.2. The view provides a denormalized, readable projection of the OKC_AQERRORS repository, exposing queue name, source, message identifier, retry count, and queue content in a single result set.

Its principal role is diagnostic. When OKC enqueues or dequeues messages through database queues (for example during contracts integration, concurrent program output, or workflow callbacks), a message that fails processing is recorded with the number of delivery attempts already made. Rather than querying the underlying error table directly — which stores raw, unaliased columns — developers and DBAs use this view to obtain business-friendly column names such as BEGIN_DATE, QUEUE_NAME, and RETRY_COUNT. The view is therefore most often consulted when a user or support engineer searches for "retry_count," since RETRY_COUNT is the exact alias exposed here.

Underlying Base Objects

Per the documented metadata, the view is defined over a single object: the synonym OKC_AQERRORS, which resolves to the OKC schema's AQ error table in the APPS data dictionary. The view performs no joins; it is a straightforward projection that renames columns for consumption. Because OKC_AQERRORS is referenced through a synonym, the view remains valid regardless of the physical table's owning schema, provided APPS holds the necessary synonym and SELECT privilege.

The absence of joins is significant: there is no dependency on OKC_K_HEADERS_B, OKC_K_LINES_B, or any other contracts entity. All diagnostic information is self-contained within the error repository, which keeps the view lightweight and fast. In 12.2.2 the definition is unchanged from 12.1.1, so queries written against one release are portable to the other without modification.

Key Columns

• ID — Surrogate identifier of the error record; useful for ordering results and for pinpointing a specific failure.
• SOURCE_NAME — Name of the originating source or process that produced the queued message.
• BEGIN_DATE — Alias for the DATETIME column; the timestamp when the message or error was recorded.
• QUEUE_NAME — The AQ queue (Q_NAME) involved in the failed operation.
• MESSAGE_ID — The AQ message identifier (MSGID), enabling correlation back to the enqueued payload.
• RETRY_COUNT — The number of delivery or processing attempts recorded for the message; the column most frequently targeted by searches.
• QUEUE_CONTENT — The stored message payload (QUEUE_CONTENTS), retained for inspection and replay analysis.

Common Use Cases and Queries

The primary scenario is identifying messages that have exhausted or approached their retry threshold. A typical query lists the most-retried messages within a time window:

• SELECT queue_name, message_id, retry_count, begin_date FROM apps.okc_que_error_cnt_v WHERE retry_count > 0 ORDER BY retry_count DESC, begin_date DESC;
• SELECT COUNT(*), queue_name FROM apps.okc_que_error_cnt_v GROUP BY queue_name;
• SELECT * FROM apps.okc_que_error_cnt_v WHERE begin_date >= SYSDATE - 7;

These queries support operational monitoring, root-cause analysis of integration failures, and evidence gathering for Oracle Support Service Requests. Because the view is read-only and built on a single table, it can be queried freely during production diagnostics without risk to concurrent AQ processing.