Wrong partition used in OSM after upgrade in table OM_ORDER_ID_BLOCK
(Doc ID 2740543.1)
Last updated on DECEMBER 30, 2020
Applies to:Oracle Communications Order and Service Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Database
After OSM upgrade wrong partition was used for OSM work orders provisioning.
OSM upgrade marks the last order-id-block as ACTIVE, and marks USED to all other order-id-blocks in OM_ORDER_ID_BLOCK table. This issue is specific to
scenario where upgrade happens from old release (731 or before) of OSM which didn't have STATUS column in table OM_ORDER_ID_BLOCK. As a consequence, post
upgrade new orders get created in very last partitions while skipping all lower partitions.
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