Release Notes for Oracle Insurance Gateway Patch 4.23.1.0.10

This document contains the release notes for Oracle Insurance Gateway Patch 4.23.1.0.10.

Version compatibility: Oracle Insurance Gateway 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

OIG-4336

Method to keep long running transaction alive with database

During the transformation process in OIG, a data file is created and several requests are sent to the Policies system to fetch additional information. These requests can take varying amounts of time to complete, depending on the size of the data and how quickly the other system responds. While waiting for these responses, the connection to the database is not actively used. Because of this inactivity, the system may automatically close the connection after a certain period of time. When the process tries to update the data file after the responses are received, it fails with a timeout error, as the original connection to the database is no longer valid.

Documentation Links:
Developer Guide - keepDbConnectionAlive

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 Summary

38210155

OIG-4515

The agent does not deliver more than 50 files at a time.

Description:

If there are more than 50 files, agent delivers only 50 files and marks their uploadSuccess as 'Y' in fileuploadresults table . Remaining files are marked 'N' in fileuploadresults. Exchange is also marked completed. This is due to the pagination issue of fileuploadresults.

Resolution:

Implemented code changes in the agent to resolve the pagination issue, allowing the agent to deliver more than 50 files at once.

37994165

OIG-4440

Performance degradation during OIG purge operations

Description:

The auto-purge job has been scheduled successfully. While the majority of purging tasks and batch data processing completed within a few hours, the OIG_EXCHANGE_LOG purge has been running for an extended period without completion.

Resolution:

The OIG purge operation is now completing within the expected duration after optimizing the purging logic by implementing a commit-size based design.

Issues that were backported in previous Release / Patch

No backports.