ASAP Losing Work Orders (Doc ID 884456.1)

Last updated on JANUARY 18, 2012

Applies to:

Oracle Communications ASAP - Version: 5.2.2 to 5.2.2 - Release: 5.2 to 5.2
Information in this document applies to any platform.

Symptoms

ASAP lost WOs when SARM went down and restarted.


a) Send 1,000 work orders
b) While work orders are being processed in Weblogic, restart SARM several times. (for the first time start SARM immediately, for the second time, start SARM after 30 sec)
c) After no message left in the message queue, check SARM database for number of work orders committed. Some WOs get lost.

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