My Oracle Support Banner

PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT Takes More Than 30s To Complete (Doc ID 1631640.1)

Last updated on SEPTEMBER 23, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

The PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT opcode is taking a long time to proceed and degrades the overall performance, sometimes taking up to 30 sec to complete.

This problem happens on the Billing and Revenue Management (BRM) software, version 7.5 PS4.

The following shows example traces from various log files :

The opcode stack trace :

cm_pcm_op_call_stack
  Seconds Type Opcode (flags, notes)
  0.000000000 Enter PCM_OP_BILL_GET_ITEM_EVENT_CHARGE_DISCOUNT (0x0)
  0.000313000 .Enter PCM_OP_SEARCH (0x10)
  8.365458000 .Exit PCM_OP_SEARCH (0x10) - from DM 0.0.0.1
  8.365467000 .Enter PCM_OP_STEP_SEARCH (0x0)
  48.356648000 .Exit PCM_OP_STEP_SEARCH (0x0) - from DM 0.0.0.1
  48.357187000 .Enter PCM_OP_STEP_END (0x0)
  48.358520000 .Exit PCM_OP_STEP_END (0x0) - from DM 0.0.0.1
  48.360873000 .Enter PCM_OP_BILL_POL_GET_EVENT_SPECIFIC_DETAILS (0x0)


The input flist is

0 PIN_FLD_POID POID [0] 0.0.0.1 /account 130088756 0
0 PIN_FLD_THRESHOLD INT [0] 400
0 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 130182888 14
0 PIN_FLD_BILLINFO_ID STR [0] "1-BSXNBZ"
0 PIN_FLD_SERVICE_TYPE STR [0] "/service/telco/prepaid"


The cm.pinlog showing the query taking a long time to complete

  s_flistp before event search
# number of field entries allocated 20, used 12
0 PIN_FLD_POID POID [0] 0.0.0.1 /search -1 0
0 PIN_FLD_FLAGS INT [0] 256
0 PIN_FLD_ARGS ARRAY [1] allocated 20, used 1
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 130088756 0
0 PIN_FLD_ARGS ARRAY [2] allocated 20, used 1
1 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service -1 0
0 PIN_FLD_ARGS ARRAY [3] allocated 20, used 1
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 130088756 0
0 PIN_FLD_ARGS ARRAY [4] allocated 20, used 1
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 130088756 0
0 PIN_FLD_ARGS ARRAY [5] allocated 20, used 1
1 PIN_FLD_BILLINFO_ID STR [0] "1-BSXNBZ"
0 PIN_FLD_ARGS ARRAY [6] allocated 20, used 1
1 PIN_FLD_POID POID [0] 0.0.0.1 /billinfo -1 0
0 PIN_FLD_ARGS ARRAY [7] allocated 20, used 1
1 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service -1 0
0 PIN_FLD_ARGS ARRAY [8] allocated 20, used 1
1 PIN_FLD_START_T TSTAMP [0] (0)
0 PIN_FLD_TEMPLATE STR [0] "select X from /event 1, /billinfo 2, /service 3 where 1.F1 = V1 and 1.F2.id in( select poid_id0 from service_t where poid_type = '/service/telco/prepaid' ) and 2.F3 = 1.F4 and 2.F5 = V5 and 2.F6.id in( select billinfo_obj_id0 from bal_grp_t ) and 1.F7.id in (select poid_id0 from service_t where service_t.bal_grp_obj_id0 in (select poid_id0 from bal_grp_t where billinfo_obj_id0 in (select poid_id0 from billinfo_t where bill_info_id = '1-BSXNBZ')))order by 1.F8 "
0 PIN_FLD_RESULTS ARRAY [1000] allocated 20, used 13
1 PIN_FLD_POID POID [0] NULL poid pointer
1 PIN_FLD_SERVICE_OBJ POID [0] NULL poid pointer
1 PIN_FLD_INVOICE_DATA STR [0] NULL str ptr
1 PIN_FLD_CREATED_T TSTAMP [0] (0)
1 PIN_FLD_START_T TSTAMP [0] (0)
1 PIN_FLD_UNIT ENUM [0] 0
1 PIN_FLD_NET_QUANTITY DECIMAL [0] NULL pin_decimal_t ptr
1 PIN_FLD_RUM_NAME STR [0] NULL str ptr
1 PIN_FLD_TIMEZONE_ID STR [0] NULL str ptr
1 PIN_FLD_BAL_IMPACTS ARRAY [*] allocated 20, used 4
2 PIN_FLD_RESOURCE_ID INT [0] 0
2 PIN_FLD_AMOUNT DECIMAL [0] NULL pin_decimal_t ptr
2 PIN_FLD_DISCOUNT DECIMAL [0] NULL pin_decimal_t ptr
2 PIN_FLD_IMPACT_TYPE ENUM [0] 0
1 PIN_FLD_RUM_MAP ARRAY [*] allocated 20, used 2
2 PIN_FLD_NET_QUANTITY DECIMAL [0] NULL pin_decimal_t ptr
2 PIN_FLD_RUM_NAME STR [0] NULL str ptr

 

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.