Last updated on APRIL 04, 2017
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 to 7.2.2 [Release 7.2]
Information in this document applies to any platform.
This KM note applies to OSM 184.108.40.206, 220.127.116.11 , 18.104.22.168 and 22.214.171.124
***Checked for relevance on 16-JUL-2015***
Beginning with 126.96.36.199 you can use the om_part_maintain.purge_partitions procedure to purge partitions. This procedure allows you to retain orders that do not satisfy the purge criteria and optionally consolidate retained orders into a single partition while dropping empty purged partitions. This is done by specifying an order ID range that spans multiple partitions and supplying a_drop_empty_ptns=true (the default). In this case, in the releases affected by this bug, purge_partitions erroneously deletes some rows from om_order_flow_coordinator and om_coord_node_instance tables that should be retained while consolidating partitions. The missing rows give rise to these exceptions during task processing:
You will see several instances of this exception in the OSM log file for each affected task because of repeated transaction rollbacks and JMS message redelivery. After each of those JMS messages reaches the redelivery limit configured for its queue it is redirected to the configured error queue. As a result, the order gets stuck.
This issue is not present in 7.0.1 and 7.0.3 because these releases do not have the ability to consolidate purged partitions. This issue is also not present in 7.2.x in the following cases:
• You purge entire partitions
• You retain orders but you purge only one partition at a time
• You retain orders and you purge multiple partitions but you don’t drop empty partitions during the purge (a_drop_empty_ptns=false).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms