Fixed a security issue.

By default, a Put or Cleanse Put call applies BVT calculations to all fields in a record instead of the fields specified in the SIF request.

After all the jobs in a batch group complete, the batch group status remains as

processing

.

After you delete a XREF record, the HMRG table is not correctly updated, which causes an Unmerge Failure.

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

After you unmerge a parent record, the foreign key column in a parent-child relationship table is updated to point to the ROWID_XREF for the child record instead of the ROWID_OBJECT for the child record. The issue occurs when a child record has multiple cross-reference records that point to the ROWID_XREF of the parent record.

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

In an IBM DB2 environment, when you run an external match, the match fails with a DB2 error.

When a long

auth_payload

value is generated and a line feed is included, an error occurs when you use the

auth_payload

value in a custom login provider.

When you run a stage job with delta detection enabled on specific staging table columns, all the records might not be written to the RAW table. Records with null values in the columns that are mapped to the PKEY_SRC_OBJECT staging table column are skipped.

In an IBM DB2 environment, when you drop base object columns, the performance is poor.

In an IBM DB2 environment, when you drop base object columns, the performance is poor.

In the Hub Console, when you use the Enterprise Manager or the Repository Manager, a null pointer exception is generated when fetching roles.

The Parse Float data conversion cleanse function fails to convert numeric string data to the float data type.

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

When you configure the MDM Hub column properties, if you save the column configuration of a non-nullable column without specifying a default value, the MDM Hub does not generate a validation error.

In the infrastructure version of WebLogic 12.2.1.3.0, deployment of the

siperian-mrm.ear

file fails with the following error:

weblogic.management.DeploymentException: java.lang.IncompatibleClassChangeError: Implementing class

When a load process inserts records into a relationship base object, the parent records might not be marked dirty. The issue occurs where the parent base object has match columns based on the child base object. The load process does not insert the ROWID_OBJECT value of the record into the dirty table associated with the base object.

In smart search, if you use a multiple word search term, records that are missing one word are omitted from the search results.

In the Hub Console login page, when an incorrect user name or password is entered, the following unclear error message appears:

SIP-09070: SIP-18017: Error occurred during user authentication, error was {0}
java.lang.NullPointerException

In an IBM DB2 environment, when you drop more than three base object columns, the transaction might time out.

When you update multiple cross-reference records associated with one base object, only one cross-reference record is passed to the post load user exit.

When you use invalid user credentials to log in to the Hub Console or to authenticate with SIF, a null pointer exception occurs.

When you initialize the server cache with localhost, you are not warned that using localhost causes cache-related performance issues in clustered appserver environments.

Null values are not written to the base object record even when the following conditions are met:

The
Allow Null Update
property is enabled for a staging table column.
A null value is the most trusted value in the staging table column.

When you install ActiveVOS during the Hub Server installation in console mode, incorrect prompts appear when you select the Service connection type.

The MDM Hub does not store the match score from ssaName3 in the MTCH table.