My Oracle Support Banner

Release Of Oracle Communications BRM Elastic Charging Engine (ECE) Version 11.2 Patch Set 8 (Doc ID 2140695.1)

Last updated on OCTOBER 03, 2019

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.2.0.0.0 and later
Oracle Solaris on SPARC (64-bit)
Linux x86-64

Details

 

Oracle Communications Elastic Charging Engine 11.2 Patch Set 8 ( 11.2.0.8.0) is released on May 20, 2016.

This announcement lists the fixes and enhancements done in Elastic Charging Engine Patch Set 8.

Patch ID: <Patch 23226017>

 

Summary of fixes to customer-reported tickets delivered in this patchset: 

 

SR Number

Bug Number

Issues Fixed

3-10631518551

21032311

While querying the balance using the PCM_OP_BAL_GET_ECE_BALANCES opcode, Connection Manager failed with an error.

3-10776748801

21153560

Notification events included all the services associated with the account instead of only the services associated with those events. Also, the events were enriched with additional information than needed.

3-10779054351

21214212

For event-based credit-control requests (CCRs), even if the correct session ID is provided in the CCR message, the DIAMETER_UNKNOWN_SESSION_ID error was displayed.

3-11017886471

21415652

When a customer’s balance had multiple balance items/buckets, resources were not getting rolled over properly.

3-11232799941

21680388

It was not possible to retrieve the purchased product data in BRM due to the attributes order mismatch in the field list (flist) sent by ECE.

3-10690047251

21981736

22477650

22481014

After a telephone number of a subscriber was changed to a new number, if any usage request was received with the new number for a date earlier than the date the telephone number was changed, ECE processed the usage request instead of displaying an error.

If the ECE server was restarted after changing the telephone number, ECE was not processing the usage request with the old telephone number even if the request was for a date earlier than the date the telephone number was changed.

3-11246645231

22027115

When ECE was restarted, Customer Updater did not load the account data properly into ECE and this resulted in ECE rating the usage for an inactive account.

3-11427218101

22027234

Customer Updater did not start when a discount sharing group contains more than one discount.

3-11549224701

22047272

ECE was throwing an exception during reverse rating when alteration offers contained temporary balance elements.

3-11576186161

22097944

When an account had more than one discount sharing group, Diameter Gateway generated duplicate SNR messages when the limit defined in the policy counters was reached.

3-11588536681

22112089

Rated Event Formatter was getting into an infinite loop when it could not connect to the BRM database.

3-11517460641

22126233

The response from Diameter Gateway did not clearly indicate if the attribute-value pairs (AVPs) in the response are mandatory or optional.

3-11644256481

22137734

Accounts created using Oracle Communications Order and Service Management (OSM), Siebel CRM, or Oracle Application Integration Architecture (AIA) were not loaded into the ECE cache.

3-11653072151

22148415

The Advice of Charge (AoC) notification was generated even when there was no balance impact.

3-11660000581

22156338

The rating profile in a custom rule was not evaluated properly due to incorrect value type.

3-11712857391

22217631

The balance query was failing with the java.lang.NullPointerException error due to reservation data corruption.

3-11773952431

22274134

For events rated by using ECE, incorrect ITEM_POID values were getting stored in the EVENT_T table in the BRM database.

3-11777142911

22305041

When a diameter request fails, the response code was incorrectly set.

3-11804491101

22308055

The Customer Updater performance needed improvement.

3-1176289257

22313399

CDRs generated for SMS messages were loaded into BRM in an incorrect order.

3-11309421171

22320933

Diameter Gateway was creating Sy (Spending-Status-Notification-Request (SNR)) messages with incorrect spending status.

3-11067379991

22334213

When a usage was rated in parallel sessions, the discount was incorrectly calculated and applied.

3-11845621361

22345145

The threshold breach notification did not include information about the breach direction.

3-11861765688

22370623

When Rated Event Formatter was restarted, the Rated Event Formatter control files were generated in incorrect format. As a result, the call detail record (CDR) files generated before Rated Event Formatter was restarted were not loaded into BRM.

3-11867505071

22472773

When ECE was restarted, Customer Updater failed with an error and the ECE server was not moved to the usage processing state.

3-11939002131

22486731

The BRM Gateway performance needed improvement.

3-11935339311

22490998

The cancel request for an initiated session was failing in ECE with an error.

3-12029554671

22588147

If a released MSISDN was reused for an account, the public user identity for the MSISDN was incorrectly linked to the old account in the ECE cache. This resulted in errors when processing usages on the new account.

3-12063415381

22592762

The amount values in the bulk files generated by Rated Event Formatter were in incorrect format and subsequently lead to errors while retrieving the amount value from the BRM database.

3-12048269241

22594685

When the ACCOUNTING_OFF charging operation type was used, the CDRs were generated considering the active reservation instead of the consumed reservation.

3-12113191731

22671046

It was not possible to use generic selectors with the date criteria in ECE.

3-12152658211

22688860

Customer Updater was not returning a meaningful and descriptive message when it was failing to load data for an account.

3-11712870931

22687977

22625346

When accounts were created in bulk in BRM, Customer Updater did not load the data into ECE.

3-12152658232

22698123

ECE was suspending the dummy events triggered in BRM instead of ignoring them.

3-12152541221

22710295

Daily bundles were getting triggered multiple times.

3-12171362271

22720489

In some cases the rated events were not found in the ECE cache.

3-12115734731

22763558

When a charge offer with a generic selector was loaded into ECE, Pricing Updater failed with an error if the generic selector had regular expressions on two different fields.

3-12229567221

22821081

ECE was generating event POIDs incorrectly and the events were not partitioned properly.

3-12360949711

22938298

The AVP information was not loaded into the BRM database if the AVP information was present only in the Initiate or Update request and not in the Terminate request.

3-12426912261

23047462

23214607

It was not possible to access the original zone result by using the post-rating extension.

3-12467198861

23061457

23201565

Invoking the PCM_OP_BAL_GET_ECE_BALANCES opcode was resulting in a Signal 11 error.

3-12514667881

23102938

23201560

Customer Updater failed with an error when updating balances for some subscribers. As a result, the balances in ECE were not in synchronization with the balances in BRM.

3-12501916691

23104988

Rated Event Formatter was generating multiple Rated Event Formatter control files for the same storable class even if the same metadata was imported without any changes.

3-12529117121

23108940

The query for balances using the PCM_OP_BAL_GET_ECE_BALANCES opcode was failing with error.

3-12541792121

23128268

23202393

When a ModifySubBalValidity event was generated with a single SubBalAudit value, the event was unnecessarily moved to the suspense queue. This was leading to processing errors.

3-12557104791

23138823

23201555

While purchasing products for an account, the purchased product information was not properly updated in ECE. This resulted in incorrect usage charging.

3-12545233491

23139091

23201546

If you create a custom business event (for example, CustModify), which includes a preconfigured business event (for example, ProductModifyEvent), triggering the custom business event was not triggering the preconfigured business event.

3-12473441621

23172309

If the ReratingCompleted event included customer-level offers, Customer Updater failed with an error.

3-12645748471

23235945

The validity end date was not properly set for daily bundles.

 

 

Key Enhancements in ECE 11.2 Patch Set 8:

For more details about these enhancements, please refer to ECE 11.2 Patch Set 8 release notes.

 

Contacts

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
Details
Contacts
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.