Pin_event_extract Failed with Dm_oracle Error: EVENT SQL STATEMENT EXCEEDED MAX ARGUMENTS ALLOWED
(Doc ID 2146322.1)
Last updated on MARCH 24, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.3.1.0.0 version, Rerating/Rebilling
The user routinely rerates batch usage for customers, and extracts usage for rerating using pin_event_extract. Pin_event_extract can handle only a limited number of accounts to rerate at any one time. This causes problems when the number of accounts to rerate is large.
This seems to be a bug in pin_event_extract, even if there is an underlying restriction in dm_oracle on the number of argument entries in a search template. The program should be able to read the input file and create a series of searches that 1) don't violate the dm_oracle constraints and 2) allow an input file of arbitrary size.
ERROR
-----------------------
in event_extract.pinlog:
STEPS
-----------------------
A sample scenario would be a file of say 70 or so /item entries in pin_event_extract.cfg. A file this large cannot be processed by pin_event_extract; it must be broken up into multiple runs.
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 |