Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.25

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.25.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.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.

Enhancements

ID	Summary	Patch
POL-12778	Extracts: Decouple bucket size from fetch size When an extract is executed, the system creates a Global Activity. This activity spawns Child Activities that each fetch a certain amount of entities and stores them in a Data File. The number of fetched entities per child activity is determined by a system property, ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS. All those fetched entities are stored in the same Data File. Therefore, the fetch size equals the Data File size. When all the entities are meant to be gathered in a single Data File the system property will be set to a high value, which can cause memory issues when the same number of entities and subresources is fetched in memory. With this enhancement, we decouple the fetch size from the data file size. To decouple both values, each child activity will fetch the entities in smaller chunks which are executed sequentially and therefore reducing the memory usage. The number of entities to be gathered in a single Data File can be configured with the ohi.extract.datafilesize property, which has a default of 500. The size of a chunk can be determined with the ohi.processing.chunksize.SELECT_EXTRACT_ITEMS property, which has a default of 100. The value of this property represents the number of entities fetched at the same time in a single chunk. A low value of this property (e.g. 1 to 10) will reduce concurrent memory usage, though it will increase the duration of the Extract as the number of entities fetched at a given time is low as well.	4.23.2.0.1

Summary

Patch

POL-12778

Extracts: Decouple bucket size from fetch size

When an extract is executed, the system creates a Global Activity. This activity spawns Child Activities that each fetch a certain amount of entities and stores them in a Data File. The number of fetched entities per child activity is determined by a system property, ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS. All those fetched entities are stored in the same Data File. Therefore, the fetch size equals the Data File size. When all the entities are meant to be gathered in a single Data File the system property will be set to a high value, which can cause memory issues when the same number of entities and subresources is fetched in memory. With this enhancement, we decouple the fetch size from the data file size.

To decouple both values, each child activity will fetch the entities in smaller chunks which are executed sequentially and therefore reducing the memory usage. The number of entities to be gathered in a single Data File can be configured with the ohi.extract.datafilesize property, which has a default of 500. The size of a chunk can be determined with the ohi.processing.chunksize.SELECT_EXTRACT_ITEMS property, which has a default of 100. The value of this property represents the number of entities fetched at the same time in a single chunk. A low value of this property (e.g. 1 to 10) will reduce concurrent memory usage, though it will increase the duration of the Extract as the number of entities fetched at a given time is low as well.

4.23.2.0.1

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 of ohi_install.cfg.template and name it ohi_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:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. 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

Configuration Properties

Ref	Action	Description
POL-12778	Added	ohi.processing.chunksize.SELECT_EXTRACT_ITEMS This property controls how many items the system exports in one chunk. Once a single chunk is extracted, the memory gets cleared and the system will continu with the next chunk. The default value for this property is 100. If the value of ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS is currently set to a lower value than 100, we recommend to use that value for this property as well.
POL-12778	Added	ohi.processing.chunksize.SELECT_EXTRACT_ITEMS.{0} This property controls how many items the system exports in one chunk per entity. Once a single chunk is extracted, the memory gets cleared. The placeholder should be replaced with the entity name, to be similar as the resourceName attribute in the Extract definition.
POL-12778	Added	ohi.extract.datafilesize This property controls how many entities are gathered in a single Data File. Therefore, this property has a similar function to the removed ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS property. The default value of this property is 500. We suggest a value between 1 and 1000, depending on the desired number of datafiles to be generated.
POL-12778	Added	ohi.extract.datafilesize.{0} This property controls how many items are gathered in a single Data File of a specific entity.
POL-12778	Removed	ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS This property was formerly used to determine the number of entities fetched within a single child activity and therefore also determines the number of entities to be created in a data file. Now that those sizes as decoupled, this property does not serve any function anymore. Therefore, this property can be removed from the configuration (e.g. properties file)

Ref

Action

Description

POL-12778

Added

ohi.processing.chunksize.SELECT_EXTRACT_ITEMS

This property controls how many items the system exports in one chunk. Once a single chunk is extracted, the memory gets cleared and the system will continu with the next chunk. The default value for this property is 100. If the value of ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS is currently set to a lower value than 100, we recommend to use that value for this property as well.

POL-12778

Added

ohi.processing.chunksize.SELECT_EXTRACT_ITEMS.{0}

This property controls how many items the system exports in one chunk per entity. Once a single chunk is extracted, the memory gets cleared. The placeholder should be replaced with the entity name, to be similar as the resourceName attribute in the Extract definition.

POL-12778

Added

ohi.extract.datafilesize

This property controls how many entities are gathered in a single Data File. Therefore, this property has a similar function to the removed ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS property. The default value of this property is 500. We suggest a value between 1 and 1000, depending on the desired number of datafiles to be generated.

POL-12778

Added

ohi.extract.datafilesize.{0}

This property controls how many items are gathered in a single Data File of a specific entity.

POL-12778

Removed

ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS

This property was formerly used to determine the number of entities fetched within a single child activity and therefore also determines the number of entities to be created in a data file. Now that those sizes as decoupled, this property does not serve any function anymore. Therefore, this property can be removed from the configuration (e.g. properties file)