Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.20

This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.20.

Version compatibility: Oracle Health Insurance Claims Adjudication 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-14132

Clearance of activities stuck in In Process stage from coherence submission caches using IP

Due to excessive load, the processing-pattern grid service stops processing activities, causing them to be stuck in the in process stage for a long time. Manually marking these activities to technical error (TE) and resubmitting them results in an exception as a reference to these activities already exist in coherence submission caches. Thus, the recovery of activities is only possible upon a full restart. The new integration point supports the clearance of coherence submission caches to facilitate the activity recovery process to avoid a complete restart.

4.23.1.0.8, 4.23.2.0.2

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

Ref Action Description

POL-14132

Added

clearsubmissioncaches IP

New IP to clear coherence submission caches.

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

36824302

3-35678279851

NXT-29766

WLS managed node doesn’t start within time and remains in starting status

Description:

It was observed in customer environment that one of the claims nodes never starts and remains in STARTING status forever. The node had to be shut down again and restarted to overcome the stated problem.

Resolution:

When the Auto wiring does not happen properly in the class ConfigurableTheadPoolProcessor, the thread count cannot be set during the initialization of the class. Now thread count is set after the class is initialized, ensuring the server does not get stuck in the starting state.

Issues that were backported in previous Release / Patch

No backports.