My Oracle Support Banner

OTM Objects Reset to Marked For Purge = N When Running a Scheduled Purge (Doc ID 1488879.1)

Last updated on MAY 06, 2022

Applies to:

Oracle Freight Payment, Billing, and Claims - Version 6.2.0 to 6.2.7 [Release 6.2]
Information in this document applies to any platform.


When attempting to run and schedule a purge, the following error occurs.

 -- Error
 The objects that were set as Marked for Purge = Y are being changed to Marked For Purge = N and thus the respective objects are not being purged in OTM.

 -- Expected Behavior
That after setting the objects to Marked for Purge = Y and running the scheduled purge that the objects would be purged.

 -- What is working

 -- Steps
 The issue can be reproduced at will with the following steps.
1. Mark for Purge is scheduled for a defined Saved Query
2. After this completes, use SQL to view that shipments were in fact changed to "Marked for Purge = Y"
3. Schedule Purge in DBA Admin
4. Watch the Purge run in the log
5. Watch the shipments go from Marked for Purge = Y back to N in SQL

 -- Business Impact
 The issue has the following business impact:
 Due to this issue, users are seeing that after setting and scheduling the purge that the objects are never purged from OTM.


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.