Pin_event_extract Is Not Considering The Parameter Event_start_time_stamp
(Doc ID 2570014.1)
Last updated on JANUARY 03, 2020
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.15.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------
One needs to search all events for re-rating based on event_t.start_t but after setting value in event_start_time_stamp parameter in pin_event_extract.cfg, it is taking value as event_t.end_t.
Parameter in pin_event_extract.cfg:
event_start_time_stamp 11/26/2018 21:25:00
From pin_event_extract log:
EXPECTED BEHAVIOR
--------------------
It should consider event_t.start_t timestamp as configured in pin_event_extract.cfg and get all events that matches with event_t.start_t
STEPS
------
The issue can be reproduced at will with the following steps:
1. Edit pin_event_extract.cfg and enable/set like below:
event_start_time_stamp 11/26/2018 21:25:00
event_category gsm
gsm /event/delayed/session/telco/gsm
2. Run "pin_event_extract -f pin_event_extract.cfg"
Billing and Revenue Management (BRM)
Structured Query Language (SQL)
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |