Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.11
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.11.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.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. |
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
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
37436369 |
3-38082342431 |
POL-16417 |
Improve the Activity recovery query when node crashes |
Description: |
When a node is crashed, the other nodes try to recover the activities from the crashed node. During this recovery the select query on activities was too costly resulting in SQLException "Socket read interrupted" - i.e connection timeout. |
||
Resolution: |
The SELECT query was optimized, and the index on the activity table was updated to prevent a full table scan. This significantly reduced the recovery cost and effectively resolved the connection timeout issue. |
||
37406105 |
3-39093009551 |
POL-16402 |
Data file deletion operation during extract run is expensive |
Description: |
The data-file deletion operation is a costly affair during extract execution. The query perform index fast full scan causing slowness |
||
Resolution: |
The select and delete query on dat_data_files was improved by joining with data file-set id |
||
37563826 |
3-36224017471 |
POL-16594 |
Floorplan conversion script fails when the payload size is large |
Description: |
Floorplan conversion script fails to convert set1, set2, set3 to sets array and results in error during upgrade. This is due to large payload size which was not handled by liquibase conversion script. |
||
Resolution: |
Liquibase script is modified to handle usecase where floorplan size is large and there is no error during conversion of region set1, set2, set3 to sets[] |
||
37647441 |
3-39093831091 |
POL-16716 |
GEN-TMVL-011 is thrown during Person Covered Service generation |
Description: |
When submitting a policy, Person Covered Services are generated if the dynamic logic with signature 'Person Covered Service' is configured. In that dynamic logic a user can configure the setPersonCoveredService method which regenerates Person Covered Services. This operation is sometimes throwing a GEN-TMVL-011 error, indicating a time overlap in Person Covered Services. This error is thrown when an existing Person Covered Service is first updated, then deleted and re-inserted. |
||
Resolution: |
Person Covered Service generation is not throwing a GEN-TMVL-011 error when an existing Person Covered Service is being updated, then deleted and re-inserted. |
||
37201760 |
POL-16137 |
Policy events for a policy are not all "cleared" when executing the policies invoice IP |
|
Description: |
Policy events of type 'R' and eventType 'I' were not getting cleared, on invoking invoice IP. The issue occurred because the deletion of policy events was dependent on a condition requiring the associated policy ID to be null. |
||
Resolution: |
The issue was resolved by modifying the condition to permit the policy ID to be either null or non-null. Additionally, the condition for the associated insurable entity ID was updated to target specific insurable entities linked to the corresponding policy. |