|
Topics: |
Patches are cumulative, and as such, include content from all prior cumulative patches. Installing the latest cumulative patch installs the newly resolved issues and all fixes from prior patches for version 3.15.
Certified Editions:
Certified DBs:
If you require this patch for a database environment not listed above, contact iWay Customer Support for assistance. You are advised to move to the latest available release of the product, or at a minimum, to the latest available patch for the product and your environment. This enables iWay to quickly provide support and issue resolutions, in addition to you benefitting from the latest updates in the product.
java -Dupgrade.dq –jar omnigen-patch-patch-3.15-cumulative.134.jar
The patch will also upgrade DQ Services to version 12.6.
In Postgres only, the OGC 360 Viewer is impacted by the number of remediation tickets in the system. This patch provides a performance improvement by creating a materialized view for the case_doc_xref table.
The performance improvement can be achieved in one of two ways:
If you do not already have a bundle deployed, after installing the patch, run Install/Replace bundle to reset the environment. The Remediation database objects will be re-created and the create-case-doc-xref-materialized-view.sql will be run.
If you already have a bundle deployed, follow the steps in the create-case-doc-xref-materialized-view.sql to alter the view and gain the performance benefits.
Note: You can download create-case-doc-xref-materialized-view.sql from the Information Builders Technical Support Center at:
|
Topics: |
The following are the key features in Omni-Gen Release 3.15 Cumulative Patch 2.
A new Runtime Configuration tab was added to the Omni Console to allow you to configure the polling interval for some services. This can be used in high volume environments during data loads to minimize the strain on the database.
The following are new feature enhancements to Ramp to Source functionality.
NATIVE_SQL Not Recognizing Errors in Ramp to Source
When using NATIVE_SQL, it is recommended to run the quality gate service and fix errors and warnings before processing the batch.
Use of a User-Defined Hash Function
To enhance performance, if the Database Hash Function is set on the default database, this feature allows a user-defined database function to be used to generate the hash keys, instead of the default.
This alternate hash function will be used in ramp to source processing with NATIVE_SQL, in the CODES_PROCESS workorder, which inserts codes/sets that were not preloaded, and in migration scripts that are generated on deploy.
Performance Improvements for Default Hash Function
To optimize performance, the default hash function is now defined as IMMUTABLE and STRICT.
The following table lists the issues that are resolved in Version 3.15 Cumulative Patch 2.
|
IRN Number |
Summary |
|---|---|
|
200707124 |
OHD 3.11 GP performance with missing Source Codes, and missing xrefs. |
|
200713064 |
Error in Remediation Portal in DEV. |
|
200714060 |
Omni Governance Console (OGC) | 360 Viewer slow response - Postgres. |
|
200814086 |
Unresponsive console processing, work orders, and measures. |
|
200820038 |
Reset subjects drops DQ tables for other subjects. |