Last updated on AUGUST 26, 2013
Applies to:Oracle Communications ASAP - Version 5.2.4 and later
Information in this document applies to any platform.
This relates to a non standard and unverified configuration that has been implemented. We are requesting that even if the product does not support multiple SRT/JSRPs, the product should not start to process work orders until all of the drivers have started up successfully.
When SARM is configured to start with a large number of drivers, if there are pending work orders it causes instability in the application. We have no idea how long it will take for the application to stabilize and to begin processing work orders.
There is no workaround. We have to wait until the application stabilizes.
We expect that SARM should start up and not begin processing work orders until all of the drivers have been spawned.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms