Why getSpGroup Result is Not Accurate in Geo-redundancy Setup
Last updated on APRIL 28, 2016
Applies to:Oracle Communications Services Gatekeeper - Version 5.0.0 and later
Information in this document applies to any platform.
In geo-redundancy setup, getSpGroup provided in PRM interface returns different SLA information than the result of ServiceLevelAgreementMBean -> retrieveServiceProviderGroupSlaByType. Why?
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