My Oracle Support Banner

Records Are Kept In N Status (with Threads Assigned) In RPM_DC_CLEARANCE After Executing RPM_CLR_DATA_CONVERSION_PROCESS_ADHOC - RMS01.RPM_FRB_UK1 violated@2RPM_CLEARANCE_DATA_CONV_SQL.PUSH_BACK (Doc ID 3068759.1)

Last updated on JANUARY 30, 2025

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version NA and later
Information in this document applies to any platform.

Goal

As part of the conversion process, converting clearances using the RPM_CLR_DATA_CONVERSION_PROCESS_ADHOC standalone process in POM, however a lot of records are having threads assigned to them (4148344 of a total of 4358407), but they're kept in 'N' status in RPM_DC_CLEARANCE table and not imported to RPM_CLEARANCE table.

Logs show: RMS01.RPM_FRB_UK1 violated@2RPM_CLEARANCE_DATA_CONV_SQL.PUSH_BACK, however at this stage, the records should already be processed and added to the RPM_CLEARANCE table
 

Solution

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
Goal
Solution
References


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