CM Failed To Start When Connecting DM With AF_UNIX Socket (Doc ID 605228.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.0.0.1 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 12-Feb-2010***
***Checked for relevance on 03-Oct-2011***
***Checked for relevance on 22-Nov-2013***


Symptoms

Problem:

Configuring CM and DM_ORACLE processes for communicating by AF_UNIX sockets, this causes the CM not to start.

Step to reproduce:

1. Configure pin.conf files of CM and DM_ORACLE processes as indicated in the documentation.

Example :
cm pin.conf file entry:
- cm dm_pointer 0.0.0.1 local /pinhome/pinxyz/opt/portal/7.3/sys/dm_oracle/dm_port

dm_oracle pin.conf entry:
- dm dm_port <PortNumber>
- dm dm_local_socket_name /pinhome/pinxyz/opt/portal/7.3/sys/dm_oracle/dm_port
(Refer to the BRM documentation for more details.)

2. Start DM_ORACLE process
3. Start CM process and check the cm.pinlog

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