Release Notes for Oracle Insurance Gateway Patch 3.21.3.0.7

This document contains the release notes for Oracle Insurance Gateway Patch 3.21.3.0.7.

Version compatibility: Oracle Insurance Gateway Release 3.21.3.x is only compatible with other Oracle Health Insurance applications release version 3.21.3.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 Description Included in Patch

OIG-2477

JSON re-indexing package for OIG

A new Package OIG_TEXT_INDEX_MAINTENANCE_PKG has been introduced for creating the oracle text index OIG_EXCHANGE_IDX1 on OIG_EXCHANGE table in Oracle 19c format with Sync frequency option. This needs to be executed as explained in the Post-upgrade stage.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. 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 .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Stage post-upgrade

A new oig_text_index_maintenance_pkg has been provided as part of the patch. Post upgrade of the patch login as ohi_oig_owner and execute the below command to recreate the index.

begin
  oig_text_index_maintenance_pkg.create_index;
end;

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34048433

OIG-2522

BP

CMT does not load as2805 integrations properly

Description:

CMT doesn’t include integration type while exporting and importing

Resolution:

CMT will include integration type while exporting and importing. (patch version needs to be the same version or higher)

34066199

3-29171386311

OIG-2525

BP

Subflow creation when payload provided is very large

Description:

Subflow creation step fails when the payload is large

Resolution:

Subflow creation step won’t fail in creation step if the payload size is in limit of defined by CLOB datatype in Oracle 19c

Issues that were backported in previous Release / Patch

No backports.