Release Notes for Oracle Insurance Gateway Patch 3.21.3.0.6
This document contains the release notes for Oracle Insurance Gateway Patch 3.21.3.0.6.
Version compatibility: Oracle Insurance Gateway Release 3.21.3.x is only compatible with other Oracle Health Insurance applications release version 3.21.3.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 | Description | Included in Patch |
---|---|---|---|
OIG-2477 |
JSON re-indexing package for OIG |
Oracle text index for OIG_EXCHANGE_IDX1 on OIG_EXCHANGE table needs to be created in Oracle 19c format with Sync frequency option. |
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 ofohi_install.cfg.template
and name itohi_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:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
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:
|
OIG-2477
Stage: Post upgrade
Action: login as ohi_oig_owner and execute the below command to recreate the index.
Begin
oig_text_index_maintenance_pkg.create_index;
end;
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
33766471 |
3-27896665871 |
OIG-2384 |
BP |
Integration Step is not matched on functional key during CMT import |
Description: |
CMT Import was failing due to integration step was being matched only on UUID. |
|||
Resolution: |
CMT Integration step would not fail now , as the matching will proceed to functional keys match, if UUID does not match. |
|||
33767371 |
3-27896665871 |
OIG-2386 |
BP |
Default commit size for Purge Operation improved |
Description: |
The commit-size of a Purge request can be supplied on the request. However it had a default commit-size of 1, which led to slow processing. |
|||
Resolution: |
Default commit-size changed to 5000. |
|||
33957024 |
OIG-2473 |
BP |
Integration code if contains the name eclipse then the endpoint /eclipse replace that with empty string leading to no integration in OIG |
|
Description: |
The mapping of integration code for the eclipse endpoint in the agent was not proper in case the integration code starts with the term "eclipse", which leads to integration not found error. |
|||
Resolution: |
The mapping of eclipse endpoint in agent has been modified to handle the scenario in case the integration code starts with eclipse. |