Search Results okc_que_objects_v




Overview
Explore in AI Chat

Overview

OKC_QUE_OBJECTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC – Contracts Core product. Its purpose is diagnostic rather than functional: it exposes a filtered inventory of Advanced Queuing (AQ) database objects that belong to the Contracts Core messaging infrastructure. The view selects from ALL_OBJECTS and restricts the result set to objects whose name matches the pattern '%OKC_AQ_%' and whose owner is either OKC or SYSTEM.

In Oracle EBS 12.1.1 and 12.2.2, Contracts Core relies on AQ queues, queue tables, and supporting objects to support asynchronous processing such as contract-related events and workflow-driven notifications. OKC_QUE_OBJECTS_V provides administrators and technical consultants with a consolidated list of those objects, their owner, type, status, and DDL timestamps. Because the definition filters out internal AQ error and message-stack tables (OKC_AQERRORS, OKC_AQERRORS_U1, OKC_AQMSGSTACKS, OKC_AQMSGSTACKS_U1), the view presents the higher-level queue entities without the noise of AQ bookkeeping tables. In reporting and integration contexts, it is typically used to verify that the expected queue infrastructure has been deployed, to confirm object validity after patching or cloning, and to reconcile object ownership between the OKC and SYSTEM schemas.

Underlying Base Objects

The view is defined over two documented dependencies. The primary source is the ALL_OBJECTS data dictionary view (accessed through the APPS synonym ALL_OBJECTS), which supplies object identity, naming, type, creation and modification timestamps, owner, and status. The second documented dependency is the XML_SCHEMA_NAME_PRESENT package, referenced during resolution of the view definition. No OKC application tables are joined directly; all rows are derived from dictionary metadata.

Because ALL_OBJECTS reflects the current state of the data dictionary at query time, the output of OKC_QUE_OBJECTS_V is inherently dynamic. It changes as AQ objects are created, altered, invalidated, or dropped by patching, upgrades, or administrative actions. The view is not indexed and performs a full scan of ALL_OBJECTS with LIKE and NOT IN predicates, so it is best suited to ad hoc diagnostics rather than high-volume, repeated queries.

Key Columns

  • OBJECT_ID – The numeric dictionary identifier of the AQ object.
  • OBJECT_NAME – The name of the queue or supporting AQ object; constrained by the definition to names containing 'OKC_AQ_'.
  • OBJECT_TYPE – The dictionary object type, for example QUEUE, TABLE, or INDEX.
  • CREATED_DATE – The creation timestamp of the object, mapped from CREATED.
  • LAST_MODIFIED_DATE – The most recent DDL timestamp, mapped from LAST_DDL_TIME.
  • OWNER – The schema owning the object; restricted to OKC or SYSTEM.
  • STATUS – The dictionary validity status (VALID or INVALID).

Common Use Cases and Queries

A typical use is confirming that Contracts Core AQ objects exist and are valid following an upgrade to 12.2.2 or after a clone. The following query lists all objects returned by the view:

  • SELECT object_name, object_type, owner, status, created_date, last_modified_date FROM apps.okc_que_objects_v ORDER BY object_name;
  • SELECT object_name, owner, status FROM apps.okc_que_objects_v WHERE status = 'INVALID';
  • SELECT owner, object_type, COUNT(*) FROM apps.okc_que_objects_v GROUP BY owner, object_type;

These queries support reconciliation of OKC-versus-SYSTEM ownership, identification of invalidated objects requiring recompilation, and baseline documentation of the queue footprint during implementation or audit activities.