OSM Created Too Many Order Id Blocks In DB After Network Failover Testing.
Last updated on SEPTEMBER 22, 2016
Applies to:Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
On : 7.2.0 version, Database
OSM created So many Order id blocks in DB after network failover testing.
User installed Active-active weblogic cluster with two managed servers running on each node. Database is the active-active RAC and we have used order partitioning . They did network failover testing. After failover When orders were submitted, Instead of using the current order id blocks both nodes created new partitions and previous partitions were not fully consumed. After that order creation was successful only in one of the nodes, other node kept on creating new partition for each order and failed to create order also. Like that it created 10 partitions resulting in 100 percent usage of table space. Even after creating 10 partitions, that node was not able to create orders.
User restarted that managed server, after that it started working fine and started using latest order id Blocks.
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