My Oracle Support Banner

CM Not Starting With 'Not enough space' Error (Doc ID 1110189.1)

Last updated on AUGUST 10, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.0 and later
Information in this document applies to any platform.

Goal

On all versions of Oracle Communications Billing and Revenue Management (BRM), when attempting to start BRM, the Connection Manager (CM) process would start and then stop immediately with the below error in the cm.pinlog:

E Fri May 7 01:40:43 2010 xxxx  cm:26287 cm_main.c(58):1797 1:xxxx:cm:26287:1:0:1273160443:0
    CMm cannot mmap data_file "/pin/pin01/var/portal/7.0/cm/cm.data.26287": Not enough space
E Fri May 7 01:47:29 2010 xxxx cm:27713 cm_main.c(58):1797 1:xxxx:cm:27713:1:0:1273160849:0
    CMm cannot mmap data_file "/pin/pin01/var/portal/7.0/cm/cm.data.27713": Not enough space

A similar error can be seen when attempting to start Data Manager (DM) Infranet Framework (IFW) Sync process in the dm_ifw_sync.pinlog as below:

E Fri May 7 22:12:41 2010 xxxx dm:19433 dm_main.c(23):2370 1:xxxx:dm:19433:1:0:1273234361:0
    DM master dm_die: "bad mmap(2)", errno 12
E Fri May 7 22:21:50 2010 xxxx dm:16401 dm_main.c(23):2370 1:xxxx:dm:16401:1:0:1273234910:0
    DM master dm_die: "bad mmap(2)", errno 12

Solution

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
Goal
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.