Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.12
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.12.
| 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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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 |
|---|---|---|---|
36930104 |
3-37593944301 |
POL-15669 |
Application logs are not persisted in the database in rare scenarios. |
Description: |
Application logs are internally queued before writing to the database. In rare cases, these logs are not successfully written, causing the internal queue to grow significantly in size - several GBs in some instances. This led to a loop in the log persistence mechanism, impacting system performance. |
||
Resolution: |
The elements are not requeued to prevent an endless loop and to avoid increasing the queue file size. |
||
36976023 |
3-37787970011 |
POL-15729 |
NullPointerException is thrown when running sample calculation for policies having surcharge of type amount |
Description: |
NullPointerException is thrown on screen on running sample calculation for policies having surcharge of type amount and policy enrollment product ending before the PCP (yearly PCP) |
||
Resolution: |
The exception was handled and the surcharge was derived based on the policy enrollment product duration. |
||
37136061 |
3-38407256051 |
POL-15999 |
New nodes in the cluster remain unresponsive when added during ongoing application activities |
Description: |
Node startup fails due to a NullPointerException caused by premature invocation of ServiceLocator while loading ReferenceSheets objects |
||
Resolution: |
The NullPointerException was fixed by replacing ServiceLocator with required objects during node startup |
||
38735530 |
3-38629251051 |
POL-18127 |
Direct debit details on the policy bill receivers missing in JET UI |
Description: |
More section is not visible in Bill Receivers tab when only single value dynamic fields are present |
||
Resolution: |
More section is visible in Bill Receivers tab when only single value dynamic fields are present |
||
37801724 |
3-39289517481 |
POL-16937 |
Getting row lock contention when running sampleinvoice IP |
Description: |
sampleinvoice IP taking more than 60s to return the response. The Api call internally invokes a plsql procedure that puts record under lock for the current transaction. When sampleinvoice is triggered for same policy ID, response time of more than 60s is observed. |
||
Resolution: |
A NOWAIT clause was incorporated into the PL/SQL procedure to immediately terminate any concurrent process waiting for the lock to be released. This fix optimizes the response time of the sampleinvoice IP call |
||
37785790 |
3-33766349291 |
POL-16890 |
Registrations are not re-applied |
Description: |
Policy calculation periods are deleted based on look back date in order to (re-)apply registrations. This is to trigger recalculation. First the initial look back date is determined to select applicable registrations. Then existing registrations are unzipped (applied registration status is set to N(ew)). But then policy calculation periods are deleted based on the initial look back date, not the look back date that is based on the 'unzipped ' registrations. This is causing the registrations not to be re-applied. This bug is present apply registrations activity only, not the integration points. Scenario to reproduce: 1) Create Policy with a Policy Collection Setting starting on 01/01 and Span Reference Date 15/01; 2) Create a single enrollment and a premium of $10 a day; 3) Create (and apply) Registration accounting for the first period ($142) and a Pay Date of 01/01; 4) Calculate Premium with Calculation Input Date 14/01 5) Create (and apply) Registration accounting for the first period ($138) and a Pay Date of 15/01; 6) Create (and apply) Registration accounting for the first period ($142) and a Pay Date of 14/01; Expected: Look Back Date should be set to 01/01 and all registrations need to be re-applied. Instead: look back date is not updated. |
||
Resolution: |
After unzip of registrations, the look back date is recalculated first before policy calculation periods are deleted, so the registrations are re-applied. |
||
37749562 |
POL-16819 |
Activities are not purged when auto-purge job is enabled for Policies. |
|
Description: |
Following errors are being experienced in policies environment during the usage of Auto purge. Error starting at line : 25 in command - BEGIN ohi_auto_purge_pkg.purge_all; END; Error report - ORA-20000: Failed jobs detected, check the table user_scheduler_job_run_details for details ORA-06512: at "OHI_POLICIES_OWNER.OHI_PARALLEL_JOBS_PKG", line 114 Cause for the error - ORA-02292: integrity constraint (OHI_POLICIES_OWNER.FIN$ACTIVITY_BUCKET_FK1) violated - child record found ORA-06512: at "OHI_POLICIES_OWNER.OHI_ACT_PURGE_PKG", line 42 ORA-06512: at line 1 |
||
Resolution: |
Ordering the PL/SQL script to delete child records before parent records resolved the issue. |
||
37625690 |
3-39664837951,3-39711991321 |
POL-16671 |
Plan Objects Not Cleaned Up When OutOfMemoryProtector Triggers During Calculate Premium Activity |
Description: |
Necessary configurations for Calculate Premium activity are fetched once and stored in plan objects within the distributed Coherence cache. When OutOfMemoryProtector triggers, activity remains stuck in IP status and plan cache does not get cleared, overtime this degrades JVM performance. |
||
Resolution: |
Clearing plan cache when system reaches CRITICAL state reduces GC overhead, improving JVM performance. It also allows stuck activities to reach final state. |
||
38068158 |
POL-17314 |
Added custom content-Length header (X-Content-Length) to the data file response for validation during file downloads in OIG |
|
Description: |
Enhance the getFileContents API in DataFile to include a custom response header X-Content-Length, allowing the calling application to verify if the full content has been received. If there’s a mismatch or if the response header is missing (incase of partial response) , the application can retry the API to retrieve the complete content |
||
Resolution: |
To address issues of incomplete or failed data file downloads in Oracle Insurance Gateway (OIG), content length validation has been implemented. This validation is triggered when OIG detects partial data by comparing the actual content length with the expected value provided in the custom response header "X-Content-Length". This header is now included in the POL data file response to enable accurate validation. |
||
38776557 |
4-0001330419 |
POL-18178 |
Combobox Quick Search and smart search is not displayed properly |
Description: |
Combobox Quick Search and smart search is not displayed properly |
||
Resolution: |
Correct width is added for search box and it is displayed properly now |
||