Release Notes for Oracle Health Insurance Authorizations Patch 4.23.1.0.1

This document contains the release notes for Oracle Health Insurance Authorizations Patch 4.23.1.0.1.

Version compatibility: Oracle Health Insurance Authorizations Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.1.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

NXT-28569

Migration of credentials from OPSS to ohistore

4.23.2 Release does not support opss anymore hence two new endpoints have been developed to export existing keystore/credentials. This functionality can be used while upgrading to 4.23.2 and moving away from opss/vault to ohistore.

Documentation Links:
Developer Guide - Credentials
Developer Guide - Keystores

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

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Post-Deploy phase

Note: This is only required while upgrading to 4.23.2 and migrating from opss/vault to ohistore.

  1. Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "true". This property will allow the end user to access the endpoint to export the secrets i.e. keystore and credentialstore.

  2. To disable exports of the keystore and Credentials, set this property "ohi.credential.migration.enabled" value to "false".

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

NXT-28569

Added

Export Credentials

Export existing credentials

NXT-28569

Added

Export Keystores

Export existing keystores

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 Summary

35795029

AUT-3348

Memory leakage with coherence processing pattern

Description:

DHL observed performance issues with activity processing; many of the activities got stuck during 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 the Coherence Processing Pattern, which triggered the memory protector, causing a halt on the system and the activities that were getting processed to be stuck forever.

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

Resolution:

Memory leakage was fixed in coherence.

35794343

AUT-3345

Issue with Diacritics search with special characters

Description:

While performing diacritic search with special character followed by A (stop list or Stop word). the search ended up with unknown result set. The list for various language is as mentioned below.

https://docs.oracle.com/en/database/oracle/oracle-database/19/ccref/oracle-text-supplied-stoplists.html#GUID-963AB8F0-6244-4D37-A1D9-4AAC2974BEA1

Resolution:

The issue seems to be with the behavior of Oracle text index with Stop list and Stop word functionality when these stop list words are used along with special characters then the same will not be indexed and leads to this issue, the same has been fixed by modifying the index metadata.

36250709

AUT-3625

Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release

Description:

Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release

Resolution:

The length of OHI_ID_ARRAY database type is updated to 19

35867557

AUT-3396

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:

Now, the cache invalidation and reloading happen only on the changes in the dynamic logic entity.

Issues that were backported in previous Release / Patch

No backports.