1 Summary of Customer-Reported Fixes
Learn about the customer-reported bugs that were fixed in the Oracle Communications Offline Mediation Controller 12.0 patch sets.
Topics in this document:
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 8
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 6
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 5
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 4
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 3
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 2
-
Customer-Reported Fixes in Offline Mediation Controller Patch Set 1
Customer-Reported Fixes in Offline Mediation Controller Patch Set 8
Table 1-1 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 8.
Table 1-1 Customer-Reported Fixes in Offline Mediation Controller Patch Set 8
Bug Number | Description |
---|---|
34534391 |
The ECE Distribution Cartridge (DC) node was not running when it joined the ECE cluster of an active-active deployment. This has been fixed. |
34174204 |
If a custom JAR already existed in an Offline Mediation Controller cloud native deployment, it was not allowed to copy the custom JAR file with the same name into the deployment during the Helm upgrade. Thus, this became an issue for replacing existing custom JAR files. This has been fixed. |
34510966 |
If custom logging was built with an earlier version of Log4j, it had stopped working after upgrading to an Offline Mediation Controller system that uses a later version of Log4j. This occurred because the Offline Mediation Controller base implementation overwrote the custom logging configurations with the default logging configurations. This has been fixed. |
Customer-Reported Fixes in Offline Mediation Controller Patch Set 6
Table 1-2 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 6.
Table 1-2 Customer-Reported Fixes in Offline Mediation Controller Patch Set 6
Bug Number | Description |
---|---|
33724250 |
An exception occurred while collecting CDR files through FTP. This has been fixed. |
33728839 |
An error occurred while collecting CDR files from a remote server. This has been fixed. |
Customer-Reported Fixes in Offline Mediation Controller Patch Set 5
Table 1-3 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 5.
Table 1-3 Customer-Reported Fixes in Offline Mediation Controller Patch Set 5
Bug Number | Description |
---|---|
31748677 |
There was a logging issue with the Duplicate Check Enhancement Processor that incorrectly indicated it was not considering the configured retention period correctly. This has been fixed. |
31938347 |
If the JDBC Distribution Cartridge encountered an exception such as a unique constraint violation, it was not processing any records unless the cartridge was restarted. This has been fixed. |
32704294 |
ECE Distribution Cartridge was not considering the time zone parameter during date formatting. This was causing the usage to be charged incorrectly to subscribers. This has been fixed. |
32946162 |
ECE Distribution Cartridge was not supporting Multiple Services Credit Control (MSCC) for sending the batch of requests as a single multi-request envelope to ECE server nodes. This has been fixed. The batch size is configurable in the ECE DC cartridge UI. Also, a new throttle parameter, maxOutstandingRequests, has been introduced to throttle the request submission to BRS. |
Customer-Reported Fixes in Offline Mediation Controller Patch Set 4
Table 1-4 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 4.
Table 1-4 Customer-Reported Fixes in Offline Mediation Controller Patch Set 4
Bug Number | Description |
---|---|
33219030 |
In Offline Mediation Controller cloud native deployments, importing and exporting the node chain was not working. This has been fixed. |
32964440 |
A high-usage suspension occurred due to bulk Short Message Service (SMS) records coming concurrently from two members that belonged to the same sharing group. Both members were trying to get a lock on the sharing group owner in parallel, which caused a suspension because one member could not get a lock within the retry limit. The ECE Distribution Cartridge (DC) node has been updated to support MSCC to send the batch of requests as a single, multiple request envelope to ECE. |
31748677 |
After the retention time of the duplicate check Enhancement Processor (EP) node had elapsed, duplicate records were reported when they should have been accepted as normal records. This has been fixed. |
31777480, 30181184 |
If a CDR was suspended due to an error and then recycled, the Recycle Processor threw an "XML is not well formed" error whenever a CDR contained any special characters such as ampersand (&). This has been fixed. |
31250379 |
The Aggregation Processor (AP) node would not flush aggregated CDRs on an absolute date and time. For example, it would not flush CDRs one day prior to the billing day of the month. This has been fixed by introducing a new Java hook named storeNARWithAbsoluteTimer for setting the absolute time for flushing records. For example: String TIME_FORMAT = "yyyy-MM-dd HH:mm:ss";String FlushTimeStr = "2021-10-16 08:31:00"; Long FlushTimeLong;FlushTimeLong = str2TimeInMilliSecs(FlushTimeStr, TIME_FORMAT); Java.storeNARWithAbsoluteTimer(out, tableIndex, FlushTimeLong); |
31545532 |
After updating the FTP password in the general.cfg file, exceptions were raised in the flow when switching between views in the GUI. This has been fixed. |
30301707, 31072533 |
In the JDBC Distribution Cartridge, the node was stopped when a unique constraint was violated. This has been fixed. |
31177917 |
A very high CPU utilization occurred due to repeated and unnecessary access to the Offline Mediation Controller wallet. This has been fixed. |
30966246 |
The Administration Client GUI was not functioning property for the Guest, Operator, and Designer user roles. The GUI was not returning any content and displaying a blank page. This has been fixed. |
30987426 |
When starting cartridges from NMShell, incorrect error messages were being logged. This has been fixed. |
31046134 |
The NMShell command for importing node chains was not retaining the original node IDs despite using the correct parameters with the command. This has been fixed. |
30625169 |
Running the Offline Mediation Controller Administration Client GUI as gui -f was throwing NullPointerException, causing the process to exit. This has been fixed. |
31348651 |
Offline Mediation Controller Cartridges were failing to move or write files when the output path was a network file system. This has been fixed by leveraging Java NIO. |
32235815 |
The subscriber tracing functionality was not working in the ECE DC node when multiple requests were batched with MSCC for the same subscriber. This has been fixed. |
Customer-Reported Fixes in Offline Mediation Controller Patch Set 3
Table 1-5 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 3.
Table 1-5 Customer-Reported Fixes in Offline Mediation Controller Patch Set 3
Bug Number | Description |
---|---|
29366752 |
In Aggregation Processor, there was no provision to access the session state and flush-related information. This has been fixed. A separate log file in the node directory that stores the flush information along with the timestamp has now been created. |
29740683 |
In Aggregation Processor, there was no provision to override default behavior of the flush timer with the rule file. This has been fixed. |
30051473 |
The ASN.1 Collection Cartridge was slow when processing a relatively large ASN.1 data file. This has been fixed. |
30301707 |
The JDBC Distribution Cartridge node was stopped when there was a unique constraint violation error. This has been fixed by inserting records one-by-one and tackling any errors separately. |
30370719 |
It was not possible to connect Administration Client remotely to an Administration Server. This has been fixed. |
30625169 |
Administration Client was failing because due to recently added widgets not being in the user privileges map. This has been fixed. |
Customer-Reported Fixes in Offline Mediation Controller Patch Set 2
Table 1-6 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 2.
Table 1-6 Customer-Reported Fixes in Offline Mediation Controller Patch Set 2
Bug Number | Description |
---|---|
28806854 29335774 |
When batch insertion mode was enabled in Java Database Connectivity (JDBC) Distribution Cartridge, the performance of the cartridge was affected. This has been fixed. |
28816188 |
In a Distribution Cartridge (DC) node, with multithreading configurations, once the configured maximum number of records were reached and the output file was closed for writing, it was observed that the data continued to be written into the closed file. This has been fixed. |
29023558 |
In a mediation chain, if any Node Programming Language (NPL) rule file or routing between cartridges was updated, then Local Data Manager (LDM) which transports data from the output directory for one node to the input directory of the other nodes stopped movement of files. This has been fixed. |
29540813 |
After submitting a recycle job from the Suspense Management Center, the recycle job was dequeued by the Recycle Cartridge and was handed over to the Recycle Enhancement Processor (EP) cartridge. Even if the Recycle EP has lost the connection to the database, it continued to process the recycle jobs, leaving the status of the jobs as recycling and required a manual intervention to move the status back to suspended. This has been fixed. |
29540828 |
If the customer data was lost in Oracle Communications Elastic Charging Engine (ECE), the Public User Identities (PUI) information was still intact. Any usage charging requests from ECE Distribution Cartridge (DC) node of Oracle Communications Offline Mediation Controller was always terminated in a delayed response from ECE, causing ECE to slowdown. This has been fixed. |
30117842 |
In case of a network issue, the Recycle Cartridge stopped working without automatic retries to connect with time out configurations. This has been fixed. |
Customer-Reported Fixes in Offline Mediation Controller Patch Set 1
Table 1-7 lists the customer-reported issues that were resolved in Offline Mediation Controller 12.0 Patch Set 1.
Table 1-7 Customer-Reported Fixes in Offline Mediation Controller Patch Set 1
Bug Number | Description |
---|---|
27938697 |
The Distribution Cartridge (DC) node was displaying the "error processing file" error intermittently. This has been fixed. |
28076189 |
The Enhancement Processor (EP) node did not support more than 20 threads. This has been fixed. |
28105656 |
Offline Mediation Controller was not mapping input record types to the suspended usage record type and hence it was not possible to distinguish suspended records. This has been fixed. |
28105679 |
The memory utilization was not calculated properly. As a result, the node manager reported a fatal memory error even when the threshold was not reached. This has been fixed. |
28105692 |
The performance of Offline Mediation Controller was affected when there were larger number of input files to be processed. A high CPU utilization from EP threads was also observed. This has been fixed. |
28311166 |
The Offline Mediation Controller Oracle Communications Elastic Charging Engine (ECE) Distribution Cartridge (DC) node and EP thread configurations were not supported through user interface. This has been fixed. |
28586528 |
If the same file was sent to Offline Mediation Controller Oracle CDR Format Collection Cartridge (CC) node again for processing, the already processed file was removed. This has been fixed. |