Database upgrade is very slow when doing OSM upgrade from version 220.127.116.11.5 to 18.104.22.168.4
Last updated on AUGUST 03, 2016
Applies to:Oracle Communications Order and Service Management - Version 7.2.2 to 7.2.4 [Release 7.2]
Information in this document applies to any platform.
On : 22.214.171.124.4 version, Database(Active-Active)
Customer testing the OSM upgrade from version 126.96.36.199.5 to 188.8.131.52.4 and we notice that the database upgrade is taking days to finish (more than 48 hours). They are testing in a database replica from production with around 20 million orders.
v_upgrade_dop := '/*+ PARALLEL(' ||get_coord_upgrade_dop ||') */';
-- update the order_seq_id from om_coord_node_instance
execute immediate 'update '||v_upgrade_dop ||' om_order_flow_coordinator fc set order_seq_id = (select ' || v_upgrade_dop ||
' distinct order_seq_id from om_coord_node_instance cni where fc.coord_set_id=cni.coord_set_id) where fc.coord_set_id>0 and fc.order_seq_id is null';
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