My Oracle Support Banner

dm_oracle Produces a Core Dump when Using PCM_OP_BULK_DELETE_OBJ to Delete More than 25 Distinct Events (Doc ID 1677141.1)

Last updated on JULY 03, 2018

Applies to:

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


The dm_oracle process is core dumping upon invoking PCM_OP_BULK_DELETE_OBJ opcode on /event objects where the count of distinct events (POIDs) to be deleted is > 20 events.


  1. Create an account and make sure it has more than 20 distinct events poids.
  2. Using testnap, try to remove all the event types for the above account with following opcode & flist

    nap(11986)> r << XXX 1
    0 PIN_FLD_POID POID [0] /event -1 0
    0 PIN_FLD_TEMPLATE STR [0] "delete X for /event where F1 = V1 "
    0 PIN_FLD_FLAGS INT [0] 256
    1 PIN_FLD_ACCOUNT_OBJ POID [0] /account 494842693 0

    nap(11986)> xop PCM_OP_BULK_DELETE_OBJ 0 1
This generates an error in the cm.pinlog

Op (PCM_OP_BULK_DELETE_OBJ) receive failed in pcm_op
<field num=0:0,0 recid=0 reserved=0 reserved2=257 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>

This also generates an error in the dm_oracle.pinlog

E Thu Nov 3 09:30:11 2011 dm:5735 dm_main.c(63):2737
DM(master) respawning backend child for slot 18
E Thu Nov 3 09:30:11 2011 dm:5735 dm_main.c(63):1108
DM(master) respawned backend child for slot 18, pid 5194

And forces dm_oracle to coredump, the dm_oracle.log shows :

DM(26565) got SIGV...
DM(26521) sigchld: back end 10, pid 26565, stat 0xb00


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

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