PurgeExpiredExecutedOrApprovedClearancesBatch Is Running Long
Last updated on JANUARY 09, 2018
Applies to:Oracle Retail Price Management - Version 15.0.1 and later
Information in this document applies to any platform.
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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms