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	4.24.1.0.4, 4.25.1.0.0

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

4.24.1.0.4, 4.25.1.0.0

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
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 .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

pre-upgrade: Application is still running.
pre-undeploy: Application is stopped, but not undeployed.
post-undeploy: Application is undeployed. Database is backed up.
post-upgrade: Released upgrade script run is complete.
post-deploy: New application is deployed, and is up and running.

Post-Upgrade Phase

Backfilling ROOT_EXCH_ID for Existing Data

Execute the following steps in the database while connected as the ohi_oig_owner user.

Identify affected records.

Run the following query to determine how many records require backfilling:
```
SELECT COUNT(*)
FROM ohi_oig_owner.oig_exchanges e
WHERE e.exst_id IS NOT NULL
  AND e.root_exch_id IS NULL;
```
If the count is 0, no further action is required. Otherwise, proceed with the following steps.

Backfill ROOT_EXCH_ID.

Execute the following update for the affected records:

UPDATE ohi_oig_owner.oig_exchanges child
   SET root_exch_id = (
       SELECT NVL(parent.root_exch_id, parent.id)
       FROM ohi_oig_owner.oig_exchange_steps step
       JOIN ohi_oig_owner.oig_exchanges parent
         ON parent.id = step.exch_id
       WHERE step.id = child.exst_id
   )
 WHERE child.exst_id IS NOT NULL
   AND child.root_exch_id IS NULL;

Commit the changes.
```
COMMIT;
```
Verify that backfilling is complete.

Rerun the query in Step 1. A count of 0 confirms that no records remain with a non-null EXST_ID and a null ROOT_EXCH_ID.