Resolved Cases

This section provides a reference for the resolved Hottrack cases. The following table lists all cases resolved since Omni-Gen version 3.1.1. In addition, all of the cases listed in this table are also resolved in Omni-Gen version 3.2 and higher.

IRN Number

Fixed In

Summary

170728066

3.2.0

Size of deployment bundle impacting deployment to Omni-Gen Server.

171122036

3.2.0

OG Performance - No change suppression.

171001001

3.1.1.1, 3.1.3, 3.2.0

Full Load of Store Domain Failing (only 1550 records).

170608015

3.2.0

Deadlocks while importing data into Omni.

170418041

3.2.0

How to access Omni Console functionalities from external interfaces?

170919073

3.2.0

In Omni-Gen 3.x, there is a missing index for instance tables, transaction_id.

170803003

3.2.0

NFR: Add function to clear Omni-Gen Bundler Console.

170619020

3.2.0

Requires steps to completely destroy a session.

170508023

3.2.0

OGC oDataDomain cannot start until Elasticsearch is started.

171005025

3.1.1.1

enq: TX - row lock contention while doing reprocess subject PERSON.

170905041

3.1.3

Ramp table SID column length should be increased in the product.

170905010

3.1.2

Omni-Gen 3.1.1 – documentation enhancement for updated controller swagger URL and examples.

170713049

3.1.2

NFR for an API that processes BATCH LOADs into Omni-Gen.

170418033

3.1.2

How to display number of instances reflected in OGC on the main OGC screen.

170731021

3.1.2

Omni-Gen 3.0.1 Vulnerability scan.

170505023

3.1.1

If same "Subject" references another subject twice in the "Master Reference" table Omni Crashes.

170505050

3.1.1

vulnerability scan - SSL/TLS Server supports TLSv1.0.

170407050

3.1.1

Omnigen: Qualys vulnerability scan: various security risks.

170323081

3.1.1

How to change the OmniConsole Password.

170731035

3.1.1

OmniGen 3.1.1 ports, https and encryption.

170505049

3.1.1

Vulnerability scan - PHP "proc_open ( )" Environment Parameter Safe Mode Restriction-Bypass (php is not omni component).

170309090

3.1.1

Java 1.8 Support for Omni Governance Console.

170710045

3.1.1

OMNI-GEN PERFORMANCE SLOW ON API UPDATES / INSERTS.

170505023

3.1.1

SiteOne - Master reference primary key constraint.

170731049

3.1.1

PERF: MSP Load Stuck in RamptoSource for 16 hours.

170629070

3.1.1

unique constraint (SVC_OMNIGEN_30.PK_OS_MASTER_REFERENCE) violated.

170410012

3.1.1

Omni-Gen process failed when processing 10 million records.

170322073

3.1.1

Swagger processing REST API not exposing MODE and TIMEOUT.

170308044

3.1.1

POC: CRLF or TAB in the data causes failures in processing / cleansing.

170622027

3.1.1

Omni-Gen os_work_order_item index needed.

170426102

3.1.1

Testing OmniGen 3.1 build 189 - No remediation service created and blank merge created.

170419082

3.1.1

PERF - Omnigen 3.0 Ramp to Source Running Slow.

170203015

3.1.1

Remediation receives all records in the matching cluster regardless of the change on the record.

170505051

3.1.1

Vulnerability scan: EMF Store Birthday attacks against TLS ciphers with 64bit block size.

170505046

3.1.1

Vulnerability scan Deployment Bundle Tool, Multiple Cross-Site Scripting Vulnerabilities Detected.

170615023

3.1.1

Omni Server Console Documentation is not showing field descriptions.

170421003

3.1.1

GC overhead limit exceeded during bulk load.

171019031

3.4.0

NFR: Omni-Gen configuration, verification, and tracing for Server and Controller.

170914082

3.4.0

WB 3.2 hybrid - 1mil row failure in publish_master.

170807006

3.4.0

Omni-Gen database maintenance.

170725027

3.4.0

Change Data Capture (CDC) is not adding columns with null values to the OID.

170829064

3.4.0

Omni-Gen CDC - Providing namespace on changed OID.

171107024

3.4.0

Omni-Gen - Additional details for running two instances of Omni-Gen on the same server.

170424024

3.4.0

PERF - Omni-Gen 3.0 - No indication remediation tickets are being sent to OGC.

171207047

3.4.0

OmniGen installation failure not reported when creating remediation tables that already exist.

171207041

3.4.0

Omni-Gen installation failure is not reported when JAVA_HOME tools.jar is not found.

180103055

3.4.0

Installing Omni-Gen as a service fails to start when Java is installed under the Program Files directory.

171024048

3.4.0

NFR: Ordering of system logs and add timestamp.

171113137

3.4.0

Custom actions in SCXML to iSM.

170711001

3.4.0

Encrypt passwords in omnigendata.

171017064

3.4.0

NFR: Omni-Gen scheduling and automation of work orders.

170905013

3.4.0

Omni-Gen 3.1.1 - exposing errors on the console - logging enhancement/configuration.

180110064

3.4.0, 3.1.2.2

NFR: Send emails to a distribution list when workloads fail.

170919071

3.4.0

Omni-Gen removed REPOS_SUBJECT_WGID and REPOS_SUBJECT_WPK indexes - remove from OmniRepo.

180117023

3.4.0

Omni-Gen 3.2 - Case sensitive SqlServer DB / SQLServerException: Invalid column name 'IDCASE'.

180226004

3.5.0

OmniDQPlugin jar not installed in DQS development directory.

180207043

3.5.0

Dev environment Omni-Gen Server will not start.

180209015

3.5.0

NFR Omni-Gen: IVP for verifying the communication between controller and server.

180226024

3.5.0

Migration/Upgrade support.

170502034

3.5.0

Omni-Gen 3.1 - OGC install does not update the DATABASECHANGELOG table.

180212014

3.5.0

Omni-Gen Remediation Step: RemediationSender fails under work orders and tickets aren't created.

180307069

3.5.0, 3.2.1

Huge update query consuming resources for each transaction.

180321075

3.5.0, 3.1.4

NFR Omni-Gen: Make the work_order_scheduler threads configurable.

171017064

3.5.0, 3.4.0

NFR Omni-Gen: Scheduling and automation of work orders.

180316063

3.5.0

Change SQL used to inactivate masters without instances.

180314065

3.5.0, 3.2.1

CDC records still sending with Polling interval set to 600,000.

171214034

3.5.0

CRASH subject batch failed at rampToSource processing due to checkForMissingCodes failed.

180118033

3.5.0

CDC does not seem to be moving things to Boomi.

170831061

3.5.0

Deploy bundle error in Omni 3.1.1.

180104006

3.5.0

Omni-Gen Workbench: UI inconsistent right-click behavior.

180115049

3.5.0

Omni-Gen Workbench data is removed after a new subject is deployed.

180601016

3.6

WorkBench/DDP : Insufficient validation on reserved columnnames.

180510009

3.6, 3.1.4

Error moving data from Ramp to Source (String or binary data would be truncated).

180320029

3.6

NFR OmniGen - ability to verify database connections and reconnect from console.

171205073

3.6

Update to the master tables or reasoning why last_source_modified_date column is always null.

190202005

3.8, 3.5

CLONE: OutOfMemory on FILL_RELOAD_QUEUE in PostgreSQL.

181220040

3.8

Update bundle fails with the inability to unzip to artifacts.

180913038

3.8, 3.5

Omni-Gen version 3.5: Update transaction_id takes more than 16 hours for 40 million records.

181226030

3.8, 3.6.3

OGC caching entitlements instead of getting them from a fresh query.

181120071

3.8

OGC cannot configure HTTPS: The context.xml file is overwritten to default upon restart.

181015043

3.8, 3.2.2

Large number of remediation tickets causes out-of-memory issues in AutoClose phase.

181028003

3.8, 3.6.3

Accessing external databases from DQ Cleansing plan in Omni-Gen.

180621023

3.8

Omni-Gen upgrade from version 3.1.1 to 3.5: Deploy failure recovery.

180829043

3.8, 3.5

Not loading SOURCE_CODE_METADATA data into source and instance tables.

180820079

3.8

Error when creating deployment bundles.

180819007

3.8, 3.4.5

Omni-Gen: Non-trimmed SIDs cause mastering errors and failed work orders.

180920040

3.8

Omni-Gen version 3.5: Workbench rule fails with pop up menu to contact the administrator.

180718024

3.8, 3.6.3, 3.5

Omni-Gen version 3.5: Check for Source Code fails with java exceptions.

180206030

3.8

Omni-HealthData version 3.1.3: Structure of the DQ bundle to be used for updating the bundle.

180705101

3.8

Omni-Gen version 3.5: Turning off counts in OGC viewer until the master table is selected.

180612021

3.8

Increasing the column display width of fields to view full information on the screen.

180803012

3.8

Omni-Gen: Configuration for UTF-8 in SQL Server.

180412069

3.8

NFR Omni-Gen: Recognizing cleansing/mastering errors in a load and flagging.

180208028

3.8

In the Deployment Bundle Console, deleting a bundle deletes all DQ projects in the SVN and source models in the EMF Store.

171113137

3.8

Custom actions in SCXML to iSM.

170615112

3.8

List of Omni error messages and their meanings.

180223006

3.12

Display Model Fieldname short/long descriptions in the web (OGC, WB, DQM) consoles

190329091

3.12

OG Swagger API UI and documentation issues

190701096

3.12

Omni-Gen Server: out of memory during the fill reload queue processing step

190206153

3.12

Omni Governance Console slow

190410056

3.12

Vulnerability scan causes connection reset and Java out of memory

190807065

3.12

Column names ending in Code not processing properly through Omni-Gen

190805054

3.12

In our TEST and PROD Omni-Gen, the Cleansing status is unknown

190812098

3.12

Support for mssql-jdbc-7.2.1.jre8.jar

190927095

3.12

YL request to set the timezone on their prod Omni-Gen Server to be Eastern time from UTC

191021119

3.12

Cloud: Debugging Omni-Gen DQ services and generating a diagnostic zip

181030077

3.12

Email alerts for work orders

180819007

3.12

Non-trimmed SIDs cause mastering errors and failed work orders

190107107

3.12

Create a feature that removes inactive records

190205017

3.12

Greenplum bundle fails: ERROR: PRIMARY KEY and DISTRIBUTED RANDOMLY are incompatible

190307030

3.12

Security scan causes Java heap

181113055

3.12

Frequent connection getting closed failing the work orders

190312138

3.14

Omni Governance Console: Temporary DB outage requires OGC restart

191212068

3.14

Omni Governance Console: When DB connection is lost, there is no automatic reconnect

191220031

3.14

Omni-Gen Server: Provide information on why jobs are waiting

191231035

3.14

Omni Governance Console: administration formatting settings for views not working

200103076

3.14

Omni-Gen Server Console: After stopping a DQ service the ON button is no longer displayed and the service cannot be restarted