DM_ORACLE Re-connection Issue

(Doc ID 1489870.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

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

Symptoms

On : 7.3.1.0.0 version, DM

When attempting to reconnect the following error occurs.

ERROR
-----------------------

In dm_oracle.pinlog

E Thu Feb 02 15:36:20 2012 su1568 dm:11624 dm_if_oracle.c(116):4228 1:su1568:cm_delayed_db2:14735:1:9:1328193380:1
DMbe TRANS_FIRST: #0 "start trans..." 0 bad, op 4, errcode -1
E Thu Feb 02 15:36:20 2012 su1568 dm:11624 dm_if_oracle.c(116):4236 1:su1568:cm_delayed_db2:14735:1:9:1328193380:1
ORACLE error: dm_if_process_op: OCITransStart: code 3113, op 0
=ORA-03113: end-of-file on communication channel
E Thu Feb 02 15:36:20 2012 su1568 dm:11624 dm_if_oracle.c(116):3733 1:su1568:cm_delayed_db2:14735:1:9:1328193380:1
bad probe of ORACLE connection "BRMCLI2_01_CLI", PINStmtExecute rc 3114 errmsg "ORA-03114: not connected to ORACLE


BUSINESS IMPACT
-----------------------
As per the BRM documentation, "If the BRM database is offline, any interrupted transactions are rolled back when the database is restarted. The DM automatically attempts to connect to the database until a connection is made." But in production environment, the DM_O fails to reconnect to DB once the connection goes down.

The cm and DM_O have to be manually restarted in order to re-connect.

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