Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.6
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.6.
| 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.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 | BP | Summary |
|---|---|---|---|---|
34485810 |
3-30287286671 |
POL-11140 |
BP |
Dynamics Fields in a FlexCode definition should be updated through CMT |
Description: |
The Field attribute in FlexCodeFieldUsage is not being updated using CMT import. It shows error with code GEN_RULE_023. |
|||
Resolution: |
It is now allowed to update Field in a FlexCode Definition with certain conditions. It is allowed upgrade the size of a field of same datatype, but not downgrade of size, or in case of Number field it does not allow downgrade on decimal size as well. The exception is covered by the BR COD-FCFU-017 |
|||
34570593 |
3-30511669821 |
POL-11307 |
BP |
Incorrect result amount on premium calculation result when span reference date of the collection setting is 29, 30 or 31st |
Description: |
When policy calculation periods are split and the collection setting has a span reference date of end of month (31 days), the premium amounts were double the amount of what was expected. This was for daily premiums with amount distribution evenly. |
|||
Resolution: |
The way the premium amount is distributed is improved. |
|||
34675578 |
3-30709310321 |
POL-11445 |
BP |
BP - Activity UNSEND_FIN_MSG_XML fails for message id having large invoices |
Description: |
UNSEND_FIN_MSG_XML failed when processing financial id having large invoices (around 200), this resulted in more than 1K FIN_MESSAGE_ID being passed in the IN clause of DELETE query causing ORA error "ORA-01795: maximum number of expressions in a list is 1000", which ultimately failed the activity. |
|||
Resolution: |
Changed the collection from List to Set to avoid duplicate Financial Messages ids in the IN clause |
|||
34682864 |
3-30682575471 |
POL-11453 |
BP |
BP: Aggregating financial messages at the end of GENERATE_FIN_MSG_XML fails with ORA-00600 error when the volume is high |
Description: |
Aggregating financial messages at the end of GENERATE_FIN_MSG_XML fails with ORA-00600 error when the volume (number/size of financial messages) is high |
|||
Resolution: |
An alternate XML aggregation logic has been implemented to fix ORA-00600 error |
|||
34683256 |
3-30011552221 |
POL-11455 |
BP |
Extract activity stays in 'in process' status sometimes waiting on AtomicSafeInitializer |
Description: |
While initializing ExtractGlobalPlan, sometime extract activity stays in 'In Process' status by waiting on AtomicSafeInitializer and never completes. As a result, if any new extract activities are submitted, it will be also in 'In process' status and if such submission continues, finally the activity processing thread pool is exhausted. |
|||
Resolution: |
Modified the way of initializing ExtractGlobalPlan. Now ExtractGlobalPlan is initialized immediately after it is created on each node. |
|||
34697657 |
3-30823746721 |
POL-11470 |
BP |
Extract activity with high volume may cause OutOfMemoryError |
Description: |
Extract activity with high volume (and if multiple extract activities are processed concurrently) may cause OutOfMemoryError. All the child activities are submitted at once to the coherence grid for processing, causing contention and memory issues in coherence. |
|||
Resolution: |
Processing of the child activities (PROCESS_EXTRACT_ITEMS) originated from the parent activity (SELECT_EXTRACT_ITEMS) is now throttled. Also, the memory footprint of running the activity PROCESS_EXTRACT_ITEMS is reduced. |
|||
34698290 |
3-29584669481 |
POL-11472 |
BP |
Target events are duplicated or missed when created persons through persons IP |
Description: |
When there is a bulk load of persons happening concurrently (through persons IP), it is seen that in target events there are duplicate or missing records. |
|||
Resolution: |
The query that fetches source events is now ordered by a deterministic field. |
|||