Pin_event_extract Failed with Dm_oracle Error: EVENT SQL STATEMENT EXCEEDED MAX ARGUMENTS ALLOWED (Doc ID 2146322.1)

Last updated on JULY 08, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information 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:
E Sun Oct 14 22:49:56 2018  hostname pin_event_extract:9891  pin_event_extract.cpp:3075 1:hostname:pin_event_extract:9891:1:14:1464874955:5
*** EVENT SQL STATEMENT EXCEEDED MAX ARGUMENTS ALLOWED ***
...
E Sun Oct 14 22:49:56 2018 hostname pin_event_extract:9891 pin_event_extract.cpp:1842 1:hostname:pin_event_extract:9891:1:17:1464874955:6
*** EVENT SELECT FAILED ***
<location=PIN_ERRLOC_DM:4 class=UNKNOWN:0 errno=PIN_ERR_STORAGE:43>

<facility=0 msg_id=0 version=0>

in cm.pinlog:
E Sun Oct 14 22:49:56 2018  hostname cm:9892  cm_child.c(107):4666 1:hostname:pin_event_extract:9891:1:17:1464874955:6
CM output flist: opcode PCM_OP_STEP_SEARCH
# number of field entries allocated 20, used 2
0 PIN_FLD_POID           POID [0] 0.0.0.1 /search 0 0
0 PIN_FLD_ERR_BUF         ERR [0]
<location=PIN_ERRLOC_DM:4 class=UNKNOWN:0 errno=PIN_ERR_STORAGE:43>
<facility=0 msg_id=0 version=0>

in dm_oracle.pinlog:
E Sun Oct 14 22:49:56 2018  hostname dm:9828  dm_back.c(26):1401 1:hostname:pin_event_extract:9891:1:17:1464874955:6
DMbe #2: process_op: op 17, err 43


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.

Cause

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