This page outlines known issues that have been fixed in releases after 9.0.0.0.

Audit Profile Unable to Load Database Profile with Oracle 19c

Create an Audit profile and select a Database profile using Oracle 19c, and it will load forever.

Failed to install new Execution Container with "Codeserver port is not defined" error prompt 

When the platform is installed with other web interface port instead of the default 9000 configured by the install.xml (mz.webserver.port), the new installation for execution container will fail upon running the mzsh topo register command. 

As a workaround, the user is required to manually update the MZ_PLATFORM port on $MZ_HOME/bin/mzsh file to the Platform and Execution Container.

Failed to startup new Execution Container installation after upgrading the platform from MZ8.x to MZ9.0

After upgrading the platform container from MZ 8.x to MZ 9.0, the new installation for Execution Container is completed. 

But the topo failed to register with an error prompt "Failed (config): Resolving startable picos from container default/exec1 * replace in parent not possible".

New installations with Oracle databases may fail with column mismatch

During the initial mz_user insertion, a column mismatch may break the new product installations with an Oracle database. 

If System Insight is enabled (property "mz.system.insight" is set) in MZ 8.x, upgrade fails

If System Insight is enabled in the MZ 8.x installation, that is, if the property “mz.system.insight” is set, then upgrade to MZ 9.0 will fail. The system will not start up since the System Insight packages are no longer available.

Upgrading from an 8.x Execution Container requires manual update on install.types property to "ec"

When upgrading an execution container from MZ 8.x, the user is required to manually update the install.types property to "ec", as well as updating other properties in the install.xml file according to the platform container setup.

GCP Storage Profile Uncheck Uses GCP Profile Radio Button Unchecked

When open a profile with Use GCP Profile checked has an incorrect setting of the disabled Input Option radio buttons, non is selected.

Debug output in the Workflow Monitor maybe come corrupt

If the load becomes too great on the debug window the output may become corrupt and un-readable. The running of the workflow is not affected.

Aggregation Session Inspector returns an internal error if the input file is corrupt

If the file is corrupt only an internal error is returned with no explanation.

Refresh button in the Database Agent doesn't function correctly

When clicking the refresh button the table name is not refreshed correctly.

"Database Type" Displays Blank when Switching Between Default/Adv Connection Setup

Switching between Default and Adv Connection Setup can result in there being no data in the fields.

Data Veracity Profile generate SQL pop up is small

The pop up for SQL generation is very small and difficult to use.

Accessibility Issues

The new web-native desktop aims to be fully accessible, but there are currently some outstanding issues regarding this. These include:

• In some interfaces, the keyboard navigation doesn't follow the ideal order or convention

• Keyboard navigation may not be able to get to sub-menu items of some table menu items that have several levels of sub menus

• Some minor elements are not read correctly by screen readers

• Page loading is not announced correctly

Code Editor Issues

The code editor in the new web-native desktop provides code completion and syntax highlighting there are some known issues:

• Quoted text not highlighted

Known differences between desktops

There are some known, minor issues with differences between the two desktops.

• No Default Setting for Commit Window Size in SQL Forwarder

• GCP Storage profile uncheck use GCP profile radio button unchecked

Legacy desktop issues

In the legacy desktop an exception can occur when first logging in to the platform. Re-trying the login fixes this and it doesn't recur

Logging issues

Warning about workflow packages in the platform log.

When importing configurations including the Open API profile the 'Custom Specification' checkbox becomes unchecked

This needs to be manually corrected to enable the workflows to run correctly.

Changes Made To Existing Saved Filters In Data Veracity Search & Repair Cannot Be Saved

If you have an existing saved filter for Data Veracity Search & Repair function, loading the saved filter and then making changes to its filter properties do not allow you the option to save and overwrite the saved filter.

Data Veracity Restricted Field Displayed Un-related Field When Enable Datatype

In Data Veracity Restricted Fields page, when we create New Restricted Fields, enable Datatype and select Map from the dropdown list, you would find that subsubUDR which is not related is displayed.

Data Veracity Repair Jobs Start Date and End Date Are Not Following Standard DateTime Format

Repair Jobs Start Datetime and End Datetime are currently not displaying format YYYY-MM-dd HH:mm:ss

Data Veracity Filter Datetime Format Are Not Following Standard Format

In the Data Veracity Search page, the result list displays format is yyyy-mm-dd hh:mm:ss

In the Data Veracity Filter page, when we construct a Filter query, and select any Datetime field, the displays format is dd/mm/yyyy.

System Import Data Veracity Profile That Pointing To Oracle Database Sometimes Hang 

Before we create Data Veracity tables in the Oracle database, the system import Data Veracity profile might cause the import process to hang.

User Given Execute Only Permission On Data Veracity Profile Is Unable To Select Data Veracity Profile To Search

In the Data Veracity Search page, the user gets a "Data Veracity Profile not found" error when selecting a Data Veracity Profile that set permission Execute Group to the user's access group. 

Data Veracity Repair Jobs are Showing Platform Timezone

In Data Veracity Repair Jobs page, Start Date and End Date are still displaying according to Platform Timezone now instead of Client timezone.

Incorrect Validation Message When Select A Database Profile With Execute Permission

When user new Data Veracity Profile and select a Database Profile that user only given Execute permission, the validation message prompted Unable to retrieve Database Profile.

SAP Hana Use Supported Only With a Tested Version

Customers should only use the tested and verified version of SAP HANA 2.14.9. Use of other versions can result in an error when connecting the platform with the SAP service.

GCP PubSub Profile Throws Improper Validation Error Message

When selecting a GCP Profile in a new GCP PubSub Profile config, the program package name is prompted at the validation error message window. 

HTTP APL Functions Provide Default Keystore

HTTP APL functions provide a default keystore which is unusable, user needs to add the keystore manually with the property https.apl.keystore_location

Same Naming in Workflow Packages With Different Case Can Cause Platform Stability Issues

When workflow packages with the same names and different characters cases are handled by the platform, this can cause serious issues for the platform. It has been detected that this will cause exceptions to the log files from the resulting resources handling.

Applying SQL INSERT operation with Database Agent for Oracle Database

Performance of SQL INSERT operation may be slower using the JDBC 19c driver (ojdbc8.jar) than when using the JDBC 12.1.0.2 driver (ojdbc7.jar).

5G Profile Not Backward Compatible

Users may encounter validation errors during data import from version 8.x. This results in missing configurations in the 5G Profile and workflow, and users are required to reconfigure the 5G related settings.

Invalid SQL Forwarder Workflow Without "Commit Window Size" Setting

SQL Forwarder workflow without the "Commit Window Size" being set will encounter validation error during import.

Conditional Trace allows negative values 

The validation is failing such that negative values are allowed where they shouldn't be. Users should not input negative values.

Event Notification - StackOverflowError on events with big text contents

When using a regex expression in event notification if the regex is very broad and it attempts to match within a very large text event the thread will fail and a stack overflow error will be put in the system log. 

Invalid JMS Collector Workflow Without "Client ID" Set for Durable Subscription

JMS Collector workflow with Durable Subscription enabled but without a unique Client ID set, might encounter validation error during import.

Unable To Search Newly Added Records By 'update_user' In Data Veracity

When a new record is added to the Data Veracity table, the update_user column is set to null. The query operators such as "contains/doesn't contain" require at least an empty string("") value to be able to filter out the result.

Data Veracity View UDR Are Showing Platform Timezone

Date time in View UDR page that we launch from Data Veracity Search or Data Veracity Approve Delete are showing platform timezone instead of client timezone.

Data Veracity Exported MIM Values Showing Platform Timezone

Currently the exported MIM Values in CSV from Data Veracity are displaying platform timezone instead of client timezone.

Data Veracity Execute permission is unable to view records in Data Veracity Repair Rules and Data Veracity Restricted Fields

When users click on the Data Veracity Repair Rules, no response is available, while clicking on the Data Veracity Restricted Fields will prompt an error.

Platform installation does not prompt for new admin password when install.security was set to true

When doing new platform installation, the installation process doesn't prompt for new admin password although the install.security was set to true in the install.xml.

As a workaround, admin password can be changed from Access Controller when is required.

Filebase property issues (mz.userserver.filebased=true)

If mz.userserver.filebased=true, else if false then can ignore. When user upgrades from version 8.x to version 9.x, the access groups created in version 8.x are present but lack the execute/write permissions that were originally assigned.

To ensure a seamless upgrade process, it is imperative to export all the config prior to the upgrade and subsequently re-import it afterward. Failure to do so may result in the missing configuration data in the upgrade.

Aggregation session profile locked when exiting Explore Session using ESC key in Aggregation Session Inspector

In Aggregation Session Inspector, existing or closing the Explore Session using the ESC key on the keyboard will cause the profile locked exception when attempting any further actions such as Deleting a row. It is advised to close the dialog using the Cancel or OK button instead. Workaround for this issue is to restart platform. A fix is expected to be available in 9.0.3.0 release.