My Oracle Support Banner

UCM Batch Process Reprocesses Records And Goes Into Infinite Loop When Using Custom Values For UCM Type Code Field (UCM_TYPE_CD) Column Or Using Only A Custom Field In The UCM Search Spec Expression (Doc ID 2768485.1)

Last updated on APRIL 15, 2021

Applies to:

Siebel Universal Customer Master - Version 15.0 [IP2015] and later
Information in this document applies to any platform.


UCM Batch Process reprocesses records repeatedly and goes into an infinite loop, causing some previously successfully processed records to then fail on the reprocessing attempt.

The behaviour occurs as follows:

1. Start a UCMBatchProcess task with UCM Search Spec set to:            [Account.UCM Type Code]='Queued-Upsert1'

2. The task starts, there are no errors.

3. However, when checking the data afterwards, it has not been processed. The status remains as 'Queued-Upsert1' instead of insert or update.

4. Start UCMBatchProcess task again with same search spec expression, the same record is getting picked up again for processing and this time it fails with a user key violation error.

5. Additionally, when a new UCMBatchProcess task is started again with the same UCM Search Spec, the same record gets picked up again and it goes into an infinite cycle of reprocessing the same record and having errors against it.


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

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