Restarting OSM Managed Server In Cluster Causing ORA-00001: Unique Constraint (Doc ID 1586990.1)

Last updated on AUGUST 06, 2015

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 and later
Information in this document applies to any platform.
*****currency check on 06-Aug-2015****

Symptoms

On : 7.2.0 version, BEA Server

After restarting a managed server in a cluster (2 managed servers), orders started failing to get created due to ORA-00001: unique constraint.

It is observed that before the restart, server 1 was taking order ID with even numbers, whereas server 2 was taking order ID with odd numbers. When server 2 was down due to restart, server 1 started taking both odd and even numbers. The moment server 2 started running after the restart, it also started taking both odd and even numbers, and the issue of unique constraint started to affect some orders and persisted even after a few hours.

The behavior was corrected only after forcing restart on both servers, which caused severe business disruption as no order can be processed during the downtime of all the managed servers in the cluster.

This happens in production environment and has been replicated in the testing environment as well.

ERROR
-----------------------

####<Sep 4, 2013 4:40:58 PM SGT> <Notice> <Stdout> <osm01pp> <osmserver1>
<ExecuteThread: '10' for queue: 'oms.ws.jms'> <<WLS Kernel>> <>
<12e1cf6385845ea2:7862dd9b:140529fca35:-8000-0000000000360140>
<1378284058064> <BEA-000000> <<04-Sep-2013 4:40:58,052 SGT PM> <ERROR>
<core.logSQLException> <ExecuteThread: '10' for queue: 'oms.ws.jms'> <SQL
Exception 1 : ORA-00001: unique constraint
(ORDERMGMT.XPKOM_ORDER_FLOW_COORDINATOR) violated
ORA-06512: at "ORDERMGMT.OM_WF_API", line 4204
ORA-06512: at "ORDERMGMT.OM_WF_API", line 4124
ORA-06512: at "ORDERMGMT.OM_HANDLER_PKG", line 1719
ORA-06512: at "ORDERMGMT.OM_HANDLER_PKG", line 1755
ORA-06512: at line 1
>
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique
constraint (ORDERMGMT.XPKOM_ORDER_FLOW_COORDINATOR) violated
ORA-06512: at "ORDERMGMT.OM_WF_API", line 4204
ORA-06512: at "ORDERMGMT.OM_WF_API", line 4124
ORA-06512: at "ORDERMGMT.OM_HANDLER_PKG", line 1719
ORA-06512: at "ORDERMGMT.OM_HANDLER_PKG", line 1755
ORA-06512: at line 1



.

Cause

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