SARM Server is Going Down With the Error: "Open Server Error # " When Using Asap_utils -d 109
(Doc ID 1911017.1)
Last updated on MARCH 04, 2019
Applies to:Oracle Communications ASAP - Version 7.0.2 and later
Oracle Solaris on SPARC (32-bit)
On ASAP 7.0.2 version, in the SARM
As part of performance improvement, customer has added 3 more SRP's to the ASAP instance, because of this, changes were made in the ASAP.cfg file.
Now to test and performance tune the environment, the customer is trying to use asap_utils -d 109 System Monitor, to gather the stats when WO's are getting pushed from all 6 SRP's to ASAP. However as they start the System Monitoring, SARM server is terminated and then starts again and no Monitoring is captured in $LOGDIR.
Below is the error seen:
SARMDEV2 Server: Fatal Thread Error:
Open Server Error #  Severity  State  Error Text [No free messages.]
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