After a record in the deleted state is update by a POST REST API request, the hub state indicator remains as -1.

When you use the Compare Floats cleanse function under the Logic Functions category to test BigDecimal values, the test fails with the following exception:

java.lang.ClassCastException: java.math.BigDecimal cannot be cast to java.lang.Double

When a record is updated through a Load batch job and the incoming state is deleted, the existing state of all the cross-reference records does not change to deleted.

After you upgrade, the metadata validation of the Operational Reference Store (ORS) fails with a null pointer exception.

Prevent possible SQL injection in the Support tool.

Even though the

cmx.server.datalayer.cleanse.working_files

property is set to

FALSE

, the temporary files (

*.dat

) created during cleanse jobs are not deleted. This results in excessive file system disk space usage.

The fuzzy search operations consider the

GETLISTLimit

property but ignore the

cmx.server.match.max_return_records_searcher

property to limit the number of records that are returned.

When you use a change list to import data and promote changes to hierarchies, the import and promote operations fail.

When filtered match rules are used for a base object, match jobs fail.

If a load balancer is used in a multi-node Multidomain MDM environment, the Hub Console fails to launch.

Fixed a security issue.

In an IBM DB2 environment, when you enable the Hierarchy Manager, the creation of the hierarchy entity objects fails with a DB2 error.

When you use the MdmKeyStore class, a file descriptor leak causes FileNotFoundException errors.

When the Exact Match column contains the pipe symbol, an error occurs when you view potential matches for the record in Data Director.

After the automation tool is finished running, the tool retains a write lock on the schema.

After unmerging merged records and recalculating the best version of the truth, the Last Update Date is not updated at the base object level.

After you use the Hub Console to run a batch group that contains load jobs, the logs do not identify the load jobs that were run. In the Control & Logs panel, the Job Name column of the logs contain information other than the load job names.

Forward matching records are created during the Automerge process, which can cause the process to run slowly.

When you promote changes in the Hub Console, the promote process is slower than expected.

After upgrading from version 10.1, the metadata validation of the ORS fails with the following error:

SIP-MV-18001 - Business Entity does not exist.

Matched table entries where rowid_object=rowid_object_matched are not deleted, which causes errors when an automerge job is attempted on the matched records.

When you use the createUsers script, you experience performance issues.

When you use the Data Encryption utility in the Resource Kit to encrypt a file with long text, the output file contains two lines of encrypted text instead of one.

When a message trigger is enabled for the Delete base object data event and the Delete XREF data event on child tables, during a soft delete batch load operation, messages are not generated.

When you have Auto and Manual match rules, if the data matches both types of rules, the Match table contains duplicate entries.

After the automation tool is finished running, the tool retains a write lock on the schema.

After you select a record as not a match in

Data Director

, when you run the Auto Match and Merge job with the

Accept All Unmatched Rows as Unique

option, the record that you marked as not a match has a consolidation indicator of 2 instead of 1.

For custom queries, after you run a Load job with the

Force Update

option and a Revalidate job, the validation rule does not execute correctly.

If you run a Multi Merge job on records where the trust has been downgraded for a field, and then you unmerge the resulting XREF record, the HIST table can contain a value for the field that is not present in the XREF record.

When you run CreateUsers.cmd with a user name in mixed case, the user is stored in mixed case instead of lowercase.

If a custom query contains many joins and filters, when you open the Packages tool, the Hub Console becomes unresponsive.

In an IBM DB2 database environment, if you modify a base object in the database, and then try to add a new column through the Hub Console, the following error occurs:

SIP-10313: Exception while executing change list: 
SIP-09089: Error in SQL update: DB2 SQL Error: 
SQLCODE=-20211, SQLSTATE=428FJ, SQLERRMC=null, 
DRIVER=3.69.24. DB2 SQL Error: SQLCODE=-20211, 
SQLSTATE=428FJ, SQLERRMC=null, DRIVER=3.69.24

After you set the password policy and enable the Restrict password reuse limit option, when you add a new user, the following error occurs:

After a match job, if you delete records that matched, the records are not deleted from the match table. When an Automerge job is run, the active records merge with the deleted records.

After you unmerge a record that has more than two cross-reference records associated with it, only one of the cross-reference records reflect the correct last updated date.

The Stage job rejects some records with the following error:

SIP-11083: Cannot load class.

The automation properties file in the Resource Kit does not contain the property to configure a user email address, which is required to create a user.

The titles of unmerge tasks that are created in

Data Director

are saved as {$title} in the aeb4ptask table of the ActiveVOS schema.

When you have multiple Operational Reference Stores, the post-load user exit processes fail on some of the Operational Reference Stores.

A user with read only access can claim tasks.

If you use an API call to return ActiveVOS tasks for a user, the call fails if you specify the createDateBefore or createDateAfter filters.

After adding a new role to a user, the Operational Reference Store is marked as invalid.