Search Results okc_aqerrors_u1

Overview

APPS.OKC_QUE_OBJECTS_V is a dictionary-style reporting view in the Oracle E-Business Suite Contracts (OKC) module. It does not store contract data itself; instead, it queries the data dictionary view ALL_OBJECTS to enumerate database objects whose names match the pattern %OKC_AQ_% and that are owned by either the OKC or SYSTEM schema. In the context of Oracle EBS 12.1.1 and 12.2.2, this view exists to expose the Advanced Queuing (AQ) infrastructure that supports the OKC messaging and workflow queue mechanism, allowing administrators and developers to inspect which queue-related tables, indexes, and supporting objects are present in the database.

The view is defined over a synonym to ALL_OBJECTS, with a further dependency documented against the XML_SCHEMA_NAME_PRESENT package, reflecting the general EBS practice of resolving dictionary synonyms through APPS. Because the view derives its contents dynamically from the dictionary, it always reflects the current state of the OKC AQ objects rather than a snapshot, making it useful for both diagnostics and integration checks. The user search term okc_aqmsgstacks_u1 corresponds to a unique index on the OKC_AQMSGSTACKS queue table; the view explicitly filters that index and its table out of the result set.

Underlying Base Objects

The documented base objects for this view are:

• ALL_OBJECTS (SYNONYM) — the Oracle data dictionary view listing every object visible to the current user, supplying object identity, type, ownership, status, and timestamps.
• XML_SCHEMA_NAME_PRESENT (PACKAGE) — the EBS package referenced in the view's dependency chain, used in the broader OKC queuing stack.

The view's defining query selects from ALL_OBJECTS and applies three predicates: the object name must match the pattern %OKC_AQ_%; the owner must be 'OKC' or 'SYSTEM'; and the object name must not be one of OKC_AQERRORS, OKC_AQERRORS_U1, OKC_AQMSGSTACKS, or OKC_AQMSGSTACKS_U1. The exclusion list deliberately removes the AQ error and message-stack tables along with their unique indexes, which are internal AQ-managed artifacts, so the view reports only the remaining OKC AQ objects of interest.

Key Columns

• OBJECT_ID — the numeric identifier of the dictionary object, unique within the database.
• OBJECT_NAME — the name of the OKC AQ object, for example queue tables, their indexes, and related supporting objects.
• OBJECT_TYPE — the dictionary object type, such as TABLE, INDEX, QUEUE, or PACKAGE, indicating the role of each AQ component.
• CREATED — the timestamp when the object was created, useful for auditing the initial installation or patch application.
• LAST_DDL_TIME — the timestamp of the last DDL change, used to detect recent structural modifications.
• OWNER — the schema owning the object, restricted by the view to OKC or SYSTEM.
• STATUS — the validity status reported by the dictionary, typically VALID or INVALID.

Common Use Cases and Queries

The view is typically used to confirm that the OKC Advanced Queuing objects are installed, valid, and current after an upgrade, clone, or patch. A representative query lists all OKC AQ objects ordered by type and name:

• SELECT object_name, object_type, owner, status, last_ddl_time FROM apps.okc_que_objects_v ORDER BY object_type, object_name;
• SELECT COUNT(*) FROM apps.okc_que_objects_v WHERE status = 'INVALID'; — identifies invalid AQ components requiring recompilation or investigation.
• SELECT object_name, created, last_ddl_time FROM apps.okc_que_objects_v WHERE object_type = 'INDEX'; — enumerates the indexes backing the OKC AQ queue tables.
• SELECT object_name FROM apps.okc_que_objects_v WHERE object_name LIKE '%OKC_AQMSGSTACKS%'; — returns no rows, since that table and its U1 index are explicitly excluded.

Because the view draws on ALL_OBJECTS, results are constrained by the privileges of the querying session; the APPS synonym is normally used so that all documented OKC and SYSTEM objects are visible. Diagnostics often combine this view with queue-specific data dictionary views to confirm both structure and runtime configuration of the OKC messaging substrate.