PCM_OP_ZONEMAP_COMMIT_ZONEMAP Takes Abnormal High Time (Doc ID 1306144.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

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

Symptoms

PCM_OP_ZONEMAP_COMMIT_ZONEMAP is taking more than 30 seconds some times and it is impacting E2E order journey time when multiple orders are submitted at a time.

In order to support Mobile to Mobile free call in the same network, a BRM user is depending on zonemap tables to identify a mobile to mobile call as there is no numbering pattern to identify it. After every account creation, PCM_OP_ZONEMAP_COMMIT_ZONEMAP is called to update the zonemap tables with the respective MDN (phone number). The average number of accounts getting created is around 300 to 400 per day and may become more. The user found the opcode calls sometimes take too long and get time out . So some of the numbers getting missed in zonemap tables and mobile to mobile calls for those customers are getting charged.

The table gets updated are
ZONEMAP_DATA_RAW_T
ZONEMAP_T

Please advise how to resolve this issue.

For example, one of the opcode call stack shows
53.139928210 ....Enter PCM_OP_ZONEMAP_COMMIT_ZONEMAP (0x0)
53.179667683 .....Enter PCM_OP_TRANS_OPEN (0x10000)
53.179674577 .....Exit PCM_OP_TRANS_OPEN (0x10000)
53.179712367 .....Enter PCM_OP_STEP_SEARCH (0x0)
53.594078128 .....Exit PCM_OP_STEP_SEARCH (0x0) - from DM 0.0.0.1
53.597027952 .....Enter PCM_OP_STEP_NEXT (0x0)
54.286912307 .....Exit PCM_OP_STEP_NEXT (0x0) - from DM 0.0.0.1
54.290898257 .....Enter PCM_OP_STEP_NEXT (0x0)
56.357432439 .....Exit PCM_OP_STEP_NEXT (0x0) - from DM 0.0.0.1
56.362813148 .....Enter PCM_OP_STEP_NEXT (0x0)
57.080551341 .....Exit PCM_OP_STEP_NEXT (0x0) - from DM 0.0.0.1
57.084503437 .....Enter PCM_OP_STEP_END (0x0)
57.141408184 .....Exit PCM_OP_STEP_END (0x0) - from DM 0.0.0.1
57.141461697 .....Enter PCM_OP_SEARCH (0x0)
57.187673477 .....Exit PCM_OP_SEARCH (0x0) - from DM 0.0.0.1
57.191030983 .....Enter PCM_OP_ZONEMAP_POL_SET_ZONEMAP (0x0)
57.489269565 .....Exit PCM_OP_ZONEMAP_POL_SET_ZONEMAP (0x0)
57.561988818 .....Enter PCM_OP_WRITE_FLDS (0x20)
78.543446826 .....Exit PCM_OP_WRITE_FLDS (0x20) - from DM 0.0.0.1
78.572908646 ....Exit PCM_OP_ZONEMAP_COMMIT_ZONEMAP (0x0)

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