My Oracle Support Banner

Problems In Collections UWQ Populate After IEX: Populate UWQ Program Is Ran In Full Truncate Mode (Doc ID 1591124.1)

Last updated on FEBRUARY 12, 2019

Applies to:

Oracle Advanced Collections - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Issues in Collections UWQ, after the IEX: Populate UWQ Program is ran in full truncate mode.

The Advanced Collections UWQ is not in sync with transactions, strategies and work items status.

After running the IEX: Populate UWQ in Truncate mode, you have to run the IEX: Populate UWQ twice going with from date 90 days back in order to get the UWQs to populate correctly.

The last log file errors with the following:
Exception in delete_rows_from_uwq_summ
SQLCODE: -54 SQLERRM: ORA-00054: resource busy and acquire with NOWAIT
specified or timeout expired
SQLERRM: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Delete or Truncate on table iex_dln_uwq_summary is not success. Ending the program

But the following returns no rows:

WORKAROUNDS
===========
Manually run the processes.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 1. Bug Summary
 2. Fixed Files
 3. Recommended Patches
 4. Solution Steps
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.