Error In Cm.pinlog Could Not Find Cache Entry: PIN_SEQUENCE_TYPE_PACKAGE_ID (Doc ID 1541291.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

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

Symptoms

On : BRM 7.4.0.0.0 version, CM

ACTUAL BEHAVIOR
---------------
When the secondary DM is not started completely and we start the Primary DM/CM chain, CM cannot cache all the data required from secondary DM. This should appear as a warning or as error in the CM logs while CM is started. So that it is easy to diagnose the problems which are caused by missing sequences in the CM cache.

cm.pinlog shows:

 

 

EXPECTED BEHAVIOR
-----------------------
Not able to load the complete Data should appear as a warning or as error in the CM logs while CM is started. So that it is easy to diagnose the problems which are caused by missing sequences in the CM cache.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start DM on secondary environment
2. Before all the processes for secondary DM starts, start the CM/DM chain for Primary server.
3. Primary server CM does not cache all the data from secondary DM.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:

BRM should be robust and not fall-over at unexpected moments just because a DMO was not available when a CM started.

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