Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.16

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.16.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID Summary Patch

POL-13651

Purging Capabilities for Integration Connector Technical Tables

This enhancement introduces the ability to purge integration connector technical tables.

Documentation Links:
Administration Guide

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

35682954

3-33791960901

POL-13391

BP

Invoice lines are not properly categorized for groups with multiple billing accounts

Description:

When a single policy switches group account over time, some invoices will be generated categorized with the wrong group account. This scenario will occur when premium is calculated over a period that the policy is enrolled on multiple different group accounts.

Resolution:

Invoice lines will be properly categorized with the group account that is referred to by the billing account, based on time validity.

35466613

3-31898869071,3-34086310341

POL-12934

BP

Policy with ended collection setting and with unpaid period should not be recalculated by Calculate Premium activity daily.

Description:

If Policy’s Collection Setting is end dated and unpaid periods exist, these periods are getting recalculated in every day’s premium calculation activity.

Resolution:

Calculation takes place only on the days it should according to the specification.

35772882

POL-13597

BP

Flex code fields with search criteria not loading correct LOV values

Description:

Flexcodes LOV doesn’t load correct results when searching with criteria. Query constructed had a missing parenthesis to group 'and' and 'or' conditions

Resolution:

Search query is constructed properly for flexcode lov and expected results are shown

35793933

POL-13660

BP

Internal storage of collection methods could lead to memory leaks in premium calculation.

Description:

Collection method objects were not properly cached.

Resolution:

Changed caching of collection methods. And the response of collection settings of generic API will no longer show the attribute "collectionMethodId".

35771680

3-34053143361,3-34160159341

POL-13584

BP

Memory leakage with coherence processing pattern

Description:

DHL observed performance issues with activity processing, many of the activities got stuck while processing due to OOM.

A severe GC contention was seen on most of the nodes, as the G1 object occupied most of the memory this was due to memory leakage by Coherence Processing Pattern, which triggered the memory protector causing a halt on the system and the activities that were getting processed were then stuck forever.

Cause for OOM: The object DefaultTaskIdentifier was not cleaned up after the activities were complete.

Resolution:

Memory leakage was fixed in coherence.

Issues that were backported in previous Release / Patch

No backports.