My Oracle Support Banner

Purge Script Deleting In-progress Orders When Condition Set As v_not_running_orders (Doc ID 2614468.1)

Last updated on NOVEMBER 28, 2019

Applies to:

Oracle Communications Order and Service Management - Version 7.3.5.0.0 and later
Information in this document applies to any platform.

Symptoms

Customer ran the following purge order command:

begin
  om_part_maintain.purge_partitions(
  a_online => false,
  a_delete_before => trunc(sysdate) - 30,
  a_order_states=>om_new_purge_pkg.v_closed_or_cancelled_orders+om_new_purge_pkg.v_not_running_orders,
  a_drop_empty_ptns => true,
  a_purge_xchg_prg_tables => true,
  a_parallelism=> 16,
  a_order_id_ge=>73000001,
  a_stop_date=> sysdate + (1/24) + (30/60/24),
  a_order_id_lt=>76000001);
end;
/

and noticed that the purge script deleted in_progress orders as well. Customer states that as per Oracle documentation v_not_running_orders do not include v_in_progress_orders. But in the purge package v_not_running_orders includes v_in_progress_orders (128) as well.

om_new_purge_pkg:
v_not_running_orders constant integer := 252;--128+64+32+16+8+4, 11111100

OSM Documentation:
v_not_running_orders = v_failed_orders + v_wait_for_revision_orders + v_cancelled_orders + v_suspended_orders + v_not_started_orders

Changes

 

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