dm_oracle Process Spinning while Executing STEP_SEARCH (Doc ID 2280751.1)

Last updated on JUNE 29, 2017

Applies to:

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

Symptoms

On Oracle Communications Billing and Revenue Management (BRM) version 7.5 patchset 16, an issue exists with the Oracle Database Data Manager (dm_oracle) where it will spin consume 100% CPU if PCM_OP_SEARCH op_code is executed with wrong input flist.

The following error can be seen in the cm.pinlog:

...
1 PIN_FLD_ACCOUNT_OBJ POID [0] 0.0.0.1 /account 19783282 0
0 PIN_FLD_TEMPLATE STR [0] "select X from /event where ( 1.F1 = V1 or 1.F2 = V2 or 1.F3 = V3 or 1.F4 = V4 or 1.F5 = V5 or 1.F6 = V6 or 1.F7 = V7 ) and ( 1.F8 = V8 or 1.F9 = V9 or 1.F10 = V10 or 1.F11 = V11 or 1.F12 = V12 or 1.F13 = V13 or 1.F14 = V14 or 1.F15 = V15 or 1.F16 = V16 or 1.F17 = V17 or 1.F18 = V18 or 1.F19 = V19 or 1.F20 = V20 or 1.F21 = V21 or 1.F22 = V22 or 1.F23 = V23 or 1.F24 = V24 ) and 1.F25 = V25 "
0 PIN_FLD_FLAGS INT [0] 0
E Fri Dec 16 15:03:10 2016 xxxxx:7683 cm_child.c(132):5052 2:hostname:CustomerCenter:0:AWT-EventQueue-2:18:1481896870:0:BCvetic:::
CM output flist: opcode PCM_OP_STEP_NEXT
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] 0.0.0.1 /search -1 0
0 PIN_FLD_ERR_BUF ERR [0]
<location=PIN_ERRLOC_DM:4 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1 errno=PIN_ERR_BAD_ARG:4>

<facility=0 msg_id=0 version=0>
E Fri Dec 16 15:03:10 2016 xxxxx:7683 cm_utils.c(149):6340 2:hostname:CustomerCenter:0:AWT-EventQueue-2:18:1481896870:0:BCvetic:::
CM NAP->CM input flist: opcode=PCM_OP_STEP_NEXT, flags=0x20000000, errno=PIN_ERR_BAD_ARG:4
...

Steps to reproduce:

This issue only occurs when several users (30-40) are connected to same Connection Manager (cm)

  1. Connect 30 to 40 customer center users to same CM executing random operations
  2. Execute STEP_SEARCH op_code with invalid flag value for search which returns lots of records, so NEXT_STEP op_code will be executed
  3. After a while there will be BAD_ARG and TIMEOUT error in cm.pinlog
  4. dm_oracle process will be using 100% of CPU

Changes

 

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