check-SLEE.sh Date Shifts at Midnight UTC Regardless of Configured Timezone
Last updated on JUNE 05, 2018
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), the check-SLEE.sh is a handy wrapper script to the check binary which can output/write information regarding the Service Logic Execution Environment (SLEE) resources. More information on the check-SLEE.sh script can be found in Script to Monitor SLEE Resource Usage and SIGTRAN CAPS Rate Trends Over Time (Doc ID 1289704.1).
When using non-UTC timezones, a problem exists with the output where the date portion shifts when the portion is not midnight. For example:
20180516-17:59:01 199999 511555 100000[+0.00%] 0 (0*)
20180517-18:00:01 199999 511555 100000[+0.00%] 0 (0*)
20180517-18:01:01 173164 511565 86582[-13.4%] 0 (0*)
In the above example, the configured/desired timezone is UTC+6.
As a result, any upstream processing of the check-SLEE.sh output (check-Time_Dialogs_Events_Calls_CAPS.log) will have incorrect information.
System timezone changed to a non-UTC timezone.
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