Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.9
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.9.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.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. |
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 | BP | Summary |
---|---|---|---|---|
34750597 |
3-29584669481 |
POL-11534 |
BP |
OptimisticLockingException when updating lastlogintimestamp of the user |
Description: |
Updating lastLoginTimestamp is controlled by a system property ohi.ws.last.login.update.threshold i.e the lastLoginTimestamp is not updated if the user logs-in multiple times with in the same hour.But if there are concurrent requests next second after this hour, both the API/IP requests try to update the same user record, system throws 500 error in this case. This causes problem in updating the LASTLOGINTIMESTAMP |
|||
Resolution: |
Error thrown by the system is ignored in case there are concurrent requests to update the same user record. The LASTLOGINTIMESTAMP will be set according to the first request that updates the user record amongst all the incoming concurrent requests. |
|||
34944210 |
3-31663358871 |
POL-11858 |
BP |
Tier evaluation not working as expected |
Description: |
Correct tier is not picked up during the premium calculation when premium tier enrollment type is set to be exactly - 0 and its throwing an error. |
|||
Resolution: |
Correct tier will be picked up for exactly - 0 case as well from now on. |
|||
34916526 |
3-31593141171 |
POL-11828 |
BP |
System generates Person Covered Services for Policies in Edit status |
Description: |
When a person in enrolled on multiple Policy, the Person Covered Services will be generated for all the policy enrollments on all enrolled Policies regardless of the Policy status. That includes Policies in Edit and Canceled status. |
|||
Resolution: |
Person Covered Services are only generated for policies in Processing or Approved status. |