My Oracle Support Banner

dm_oracle Process Spinning while Executing STEP_SEARCH (Doc ID 2280751.1)

Last updated on DECEMBER 02, 2020

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:

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

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


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