SLC SLEE Fails to Start with CRITICAL Alarm: "The number of defined service keys are greater than MAXSERVICEKEYS or default value"
(Doc ID 2410857.1)
Last updated on MARCH 18, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), the Service Logic Execution Environment (SLEE) may fail to start (and thus the SLEE processes will also fail to start) with the following CRITICAL alarm:
Jun 13 16:10:22.299133 sleeStartup(22238) CRITICAL: sleeStartup: Cannot read configuration file
As a result, none of the SLEE processes start.
New installation of NCC or 3C and/or new additional services were added to the SLC.
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