Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.18

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

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

No enhancements.

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

35805237

3-33858160991

POL-13700

BP

Dynamic logic cache reloads every time on business cache invalidation even if there is no dynamic logic update

Description:

Dynamic logic cache uses a business process cache which is invalidated on any change in configuration entities (that implements ProcessCacheInvalidating) even though there is no change in dynamic logic itself . On invalidation of the cache , byte code is loaded again for all the dynamic logic which is CPU intensive and can slow down other processes running in parallel during the class loading .

Resolution:

The cache invalidation and reloading happens only on change in dynamic logic entity.

35859728

3-34177004331

POL-13778

BP

Desired row is not getting deleted in 'Parameter Domain' tab of Group Account Products page

Description:

While deleting the 1st parameter on the list it deletes as expected. While deleting any parameter other than the 1st one it jumps and deletes the one above the one we trying to delete.

Resolution:

Deleting any parameter, deletes the desired row as expected. Earlier wrong index was being used while deleting the row which is fixed now.

35655985

POL-13333

BP

Performance issue when updating the status of base financial objects in generate financial messages activity under high concurrency

Description:

High wait event "enq: TX - allocate ITL entry" occurs when updating the status of base financial objects to 'FM' in generate financial message activity under high concurrency and this causes the activity to run very slow

Resolution:

update base financial object at the end of parent activity instead of updating after every child activity. This should minimize the number of sessions opened for the update.

35855397

3-33964183741

POL-13774

BP

Activity Message is lost when generate financial message activity is recovered

Description:

Activity message (ACT-FL-DAFI-001) is lost when generate financial message activity is recovered

Resolution:

The activity message ACT-FL-DAFI-001 is removed when the recover process starts, but if the error persists during reprocess of the activity then the message is recreated.

Issues that were backported in previous Release / Patch

No backports.