SLEE "check -q" Event Queue Output Fields Vary Due to SLEE Process Handle Name
(Doc ID 2464084.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.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), when running the Service Logic Execution Environment (SLEE) check binary to see the SLEE event processing related information (per process), if the SLEE process' handle name is too long (≥16 characters), then it is concatenated with the next field in the output which throws the number of fields/field number off by 1 for the rest of the line.
For example, if the SLEE process handle name is less than 16 characters, the name and whether it is an Application of Interface are 2 separate fields:
and the SLEE queue size is the 6th field (Events column).
However if the SLEE process handle name is 16 or more characters, these 2 fields are concatenated:
2018/10/16-14:55:01 : acsStatsLocalSLEEI ACTIVE 0 none 15822
2018/10/16-14:55:01 : cap3GprsControlAgent.shA ACTIVE 0 none 0
and the SLEE queue size is now the 5th field.
As a result, if this output is being parsed and formatted for another medium, it is far more difficult and error prone.
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