My Oracle Support Banner

CM Failover Uses Wrong Server Connection With Multi-DB (Doc ID 564561.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.0]
HP-UX PA-RISC (32-bit)
HP-UX Itanium
***Checked for relevance on 01-Apr-2010***
***Checked for relevance on 29-Nov-2011***
***Checked for relevance on 10-May-2013***
***Checked for relevance on 13-Oct-2014***


In 7.3 of BRM, in a prepaid high-availability+MultiDB configuration environment, when the CM tries to failover to the second entry of a secondary DB dm_pointer (for instance, the secondary TIMOS for database, it uses the second entry of the primary DB dm_pointer instead (i.e. the dm_pointer for database


The CM connects to the second dm_pointer entry for DB and starts normally.


D Wed Jan 2 17:43:57 2008 BRM01 cm_timos:29582 pcpst.c(68):14831:BRM01:cm_timos:29582:1:11:1199292236:1 "ip BRM01 41857 ip BRM01 41854" is HA configuration
D Wed Jan 2 17:43:57 2008 BRM01 cm_timos:29582 pcpst.c(68):3561:BRM01:cm_timos:29582:1:11:1199292236:1 connect to host=BRM01, port=41857 OK
W Wed Jan 2 17:43:57 2008 BRM01 cm_timos:29582 pcpst.c(68):33001:BRM01:cm_timos:29582:1:7:1199292237:2
received PIN_ERR_NOT_ACTIVE, closing socket
W Wed Jan 2 17:43:57 2008 BRM01 cm_timos:29582 pcpst.c(68):40841:BRM01:cm_timos:29582:1:7:1199292237:2
Server connection(ip BRM01 41807) ready to failover (no trans)


The issue can be reproduced with the following steps:

1. Install a multiDB + HA standard system with at least 2 schemas ( &
2. Startup the DMOs and all DMT (primary & secondary for & for
3. Configure a CM dm_pointer entry for db to try the secondary DMT first.


The CM cannot start.


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.