My Oracle Support Banner

PurgeExpiredExecutedOrApprovedClearancesBatch Is Running Long (Doc ID 2344934.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Retail Price Management - Version 15.0.1 and later
Information in this document applies to any platform.

Symptoms


The module RPM_PURGE_CLEARANCE_SQL.PURGE_EXPIRED_CLEARANCE of PurgeExpiredExecutedOrApprovedClearancesBatch is running long.
It has been noticed that insert statement can run for more than 4 hours

 

Steps to reproduce:
The issue can be reproduced at will with the following steps:

1. Run PurgeExpiredExecutedOrApprovedClearancesBatch

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
Cause
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.