Informatica®

Multidomain MDM
10.3 HotFix 2
Release Notes
December 2019
© Copyright Informatica LLC 2001, 2020

Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Dropped Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Before You Install or Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Microsoft SQL Server 2017 Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
IBM Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Oracle Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
JBoss Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
HP-UX, Linux, and Solaris Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
After You Install or Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Multidomain MDM Hosted on Amazon Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.3 HotFix 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.3 HotFix 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
10.3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Fixed Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Closed Enhancement Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Known Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

®
Read the Informatica Multidomain MDM Release Notes to learn about known and fixed limitations,
enhancements, and support changes. The Multidomain MDM Release Notes also include information
about installation and upgrade issues and workarounds.

2020-11-10 1
Introduction
Multidomain MDM 10.3 HotFix 2 is the latest release in the version 10.x code line.
This release includes the following items:
• New features as described in the Multidomain MDM Release Guide.
• All fixed issues, features, and changed behaviors that were released in version 10.3 through 10.3
HotFix 2.
• All fixed issues, features, and changed behaviors that were released in versions 10.2 through 10.2
HotFix 4.
• All fixed issues, features, and changed behaviors that were released in versions 10.1 through 10.1
HotFix 6.
This release does not include the following items:
• Some fixed issues, features, and changed behaviors that were released in 10.1 HotFix 6.
• Some fixed issues, features, and changed behaviors that were released in 10.2 HotFix 4.
• Some fixed issues, features, and changed behaviors that were released as Emergency Bug Fixes
(EBFs) on any version.
The issues that were not integrated into this release are documented as known limitations. See “Known
Limitations” on page 38.

Important: All future HotFix or Emergency Bug Fix releases require that at least version 10.3 is installed.

Installation and Upgrade

Multidomain MDM has some known limitations related to installing and upgrading the product and has
dropped support for some application server versions. Before you begin, review these issues.

Dropped Support
Effective in version 10.3 HotFix 1, support is dropped for the following application server versions:
Red Hat JBoss Enterprise Application Platform versions earlier than 7.1
The end of maintenance support by Red Hat for JBoss EAP 6.x is June 2019. Informatica
recommends that you upgrade to JBoss EAP 7.1 and Multidomain MDM 10.3 HotFix 2 for continued
support, bug fixes, and security patches from Red Hat.
IBM WebSphere versions earlier than 9.0 Fix Pack 10
Multidomain MDM 10.3 HotFix 1 does not support WebSphere versions earlier than 9.0 Fix Pack 10.
You must deploy Multidomain MDM on IBM WebSphere Application Server Version 9.0 Fix Pack 10.

2 2020-11-10
Before You Install or Upgrade
Some known limitations can affect your install or upgrade experience. To avoid potential issues, ensure
that you review the following issues and complete any workarounds before you upgrade. Then review the
environment-specific installation and upgrade issues.

Install Java Development Kit

If you use Oracle Java runtime environment (JRE), install JRE 1.8, update 144 or later on the machines
on which you want to launch the Hub Console. JRE 1.8, update 144 or later is required for the Batch
Viewer in the Hub Console.
If you use Red Hat OpenJDK 8, install the IcedTea-Web Java Web Start implementation on the client
machines on which you want to launch the Hub Console. Red Hat OpenJDK 8 does not automatically
install a Java Web Start implementation, which is required to launch the Hub Console.
Tip: When you use IcedTea-Web Java Web Start, the time taken for the Hub Console to launch increases
over time. To improve performance, periodically clear the cache by running the following command:
javaws -Xclearcache.
(MDM-18910, MDM-24133)

Java Virtual Machine Options for all Environments

To configure a Java Virtual Machine (JVM), set the Java options by using the JAVA_OPTIONS
environment variable. After you add or edit any Java options, restart the JVM.
The following table describes the Java options settings applicable for all environments:

Java Options Description

-De360.connection.channel=http Required to launch the Entity 360 application. This Java option
specifies the connection protocol that the Entity 360 application
uses to connect to the MDM Hub Server. Set to true.

-De360.mdm.host=devazimdpapp2.ksdevx.net. Required to ensure the security certificates match the registered

fully qualified domain name (FQDN).
Set to the following value: devazimdpapp2.ksdevx.net.

(MDM-26317)

Update Subject Area Names Before You Upgrade

Verify that no subject area name begins with a number. If any subject area name begins with a number,
change the name so that it begins with an alphabetic character. If a subject area name begins with a
number, the business entity configuration generated by the MDM Hub causes Repository Manager

2020-11-10 3
validation errors. If you do not generate a business entity configuration, you can continue to use subject
area names that begin with a number. (HORA-51906)

Hub Server Installation in Non-English Environments

When you install the MDM Hub in a language other than English with JDK 1.8 or later, you need to enter
the language code.
1. To launch the installer, open a command prompt, navigate to the Hub Server installation directory,
and enter the following command:
hub_install.exe -l <language code>
Where <language code> is your preferred language. Use the language code for one of the following
languages:

Language Language Code

Brazilian Portuguese pt_BR

French fr

German de

Japanese ja

Korean ko

Russian ru

Simplified Chinese zh_CN

Spanish es

(MDM-14224)

Hub Server Installation Without Prerequisites Validation

When you run the Hub Server installer without the prerequisites validation, the database password
prompt requires a dummy value.
1. To start the Hub Server installer without the prerequisites validation, run the following command:
hub_install.bin -DSIPERIAN_INSTALL_PREREQ_VALIDATION=false
2. When prompted for the database password, enter a dummy value.
The installation continues. If you do not specify a dummy value, the installation fails. (MDM-10975)

Upgrade Installation for Entity 360 View

When you upgrade Hub Server, the entity360view.ear sometimes fails to install due to a timed out
error.
Workaround: You can run the installation components patchInstallSetup or postInstallSetup again.
Alternatively, run the following command from the <MDM Hub installation directory>/hub/
server/bin folder:

4 2020-11-10
./sip_ant.sh -Dentity360view.ear.dodeploy=true deploy.entity360view-ear
(HORA-52008)

Apple Single Sign-On is Not Supported

Informatica Data Director does not work with Apple SSO in this version of Informatica MDM Multidomain
Edition. (MDM-6906)

Microsoft SQL Server 2017 Environments

If you install or upgrade Multidomain MDM in an environment that uses Microsoft SQL Server 2017, you
must download Microsoft JDBC Driver 7.2 from the Microsoft website. Informatica does not bundle the
JDBC driver for Microsoft SQL Server 2017 with the Multidomain MDM installer.
1. Before you install or upgrade, download and extract Microsoft JDBC Driver 7.2 from the Microsoft
website.
2. Copy the driver files to the Binn directory of the machine on which Microsoft SQL Server is installed.
3. After you install or upgrade the Hub Server, copy mssql-jdbc-7.2.2.jre8.jar to the <MDM Hub
installation directory>/hub/server/lib directory.
4. Restart the application server.

IBM Environments
The following issues affect Multidomain MDM when installed with IBM AIX, IBM Db2, or IBM WebSphere.

Installing MDM Multidomain Edition in a JBoss Environment on the IBM AIX Operating
System
There are multiple issues with Red Hat JBoss EAP 7.1 running on the IBM AIX operating system,
because Red Hat does not support the configuration. To see the JBoss EAP 7.1 configurations
supported by Red Hat, visit https://access.redhat.com/articles/2026253.
The following known issues are logged for Multidomain MDM in a JBoss and AIX environment:
• MDM-16939. When the posinstallSetup script is run as part of Hub Server installation or after the
installation, uiwebapp-ear.ear does not deploy. Contact Informatica Global Customer Support for the
workaround.
• MDM-23460. When you use the ActiveVOS workflow, task approvals fail. No known workaround.
• MDM-23416. When you create records, an error is generated: SIP-09051: XML parsing problem for
input source (unknown systemId). Premature end of file.
No known workaround.
Informatica will try to address these issues in future releases, but cannot guarantee that all issues will
be resolved. You are strongly recommended to avoid this combination of application server and
operating system for your Multidomain MDM environment.

2020-11-10 5
Hub Server Upgrade from Version 10.1 HotFix 2 in IBM AIX Environments
When you upgrade the Hub Server from version 10.1 HotFix 2 on IBM AIX environments, the
entity360view.ear file fails to deploy.
Workaround: Manually run the patchInstallSetup.sh script. For more information about running the script,
see the Multidomain MDM Upgrade Guide.
(MDM-14777)

Embedded ActiveVOS Upgrade in IBM DB2 Environments

In IBM DB2 environments, before you upgrade, add the ActiveVOS database connection properties to the
build.properties file in <MDM Hub installation directory>/hub/server/bin.
The following sample shows the ActiveVOS database connection properties with sample entries:
activevos.db.type=db2
activevos.db.server=localhost
activevos.db.port=50000
activevos.db.user=AVOS
activevos.db.dbname=INFA102
activevos.db.schemaname=AVOS
activevos.db.jdbc.url=jdbc:db2://localhost:50000/INFA102
activevos.b4p.url=http://localhost:9080/active-bpel/services/AeB4PTaskClient-
taskOperations
(MDM-13104)

Enable Match Population On IBM DB2

After you install the Process Server in an IBM DB2 environment, you must enable the match population
to use for the match rules. To enable match populations, contact Informatica Global Customer Support.
(HORA-52288)

Upgrade in WebSphere IBM DB2 Environments Running Java 8

After you upgrade the MDM Hub in WebSphere IBM DB2 environments running Java 8, the Hub Console
does not launch.
Workaround: Use Java 7 on the client machines.
(MDM-12036)

ActiveVOS Installation in WebSphere Cluster Environments

When you install embedded ActiveVOS in a WebSphere cluster environment, you cannot connect to the
MDM identity service provider in the ActiveVOS Console.
Workaround: Perform the following steps after you install the Hub Server, embedded ActiveVOS, and the
Process Server:
1. In the ActiveVOS install.properties file set install.web.application to false.

6 2020-11-10
2. In the deployer.xml file in the ActiveVOS installation directory, comment out the following code:
<!-- <target name="deploy.resources"
depends="deploy.timer.manager,deploy.work.manager"/>
<target name="deploy.timer.manager">
<echo message="$
{basedir}"/>

<run.wsadmin script="${basedir}
/scripts/timermanager.jacl"/>
</target>
<target name="deploy.work.manager">
<run.wsadmin script="$
{basedir}/scripts/workmanager.jacl"/>

<run.wsadmin script="${basedir}
/scripts/systemworkmanager.jacl"/>
</target>
<target name="deploy.jaas">
<run.wsadmin script="$
{basedir}/scripts/jaaslogin.jacl"/>

</target>

<target name="deploy.apps">

<run.wsadmin script="${basedir}
/scripts/installapp.jacl"/>
</target> -->
3. In the <MDM installation directory>/hub/server/bin directory, run the following commands:
sip_ant.bat deploy_mdm_identity_resolution
sip_ant.bat deploy_avos_server
4. Deploy the ActiveVOS EAR files. For information about deploying EAR files, see the Multidomain
MDM Installation Guide.
(MDM-13269)

Process Server Installation and Upgrade

If you install or upgrade the MDM Multidomain Edition for IBM DB2 on WebSphere in a Linux
environment, the postInstallSetup script might fail with the javax.management.MBeanException error.
Perform the following tasks when the postInstallSetup script fails:
u Stop and start WebSphere.
The Process Server starts up.

2020-11-10 7
(MDM-10850)

Oracle Environments
The following issues affect Multidomain MDM when installed with Oracle database or Oracle WebLogic.

Disable WebLogic Server Authentication

The MDM Hub uses HTTP basic authentication for which you must disable WebLogic Server
authentication. To disable WebLogic Server authentication, edit the config.xml file.
1. Navigate to the following WebLogic directory:
<WebLogic installation directory>/user_projects/domains/<user domain>/config
2. Open the config.xml file in a text editor.
3. Add the following element within the <security-configuration> element:
<enforce-valid-basic-auth-credentials>
false
</enforce-valid-basic-auth-credentials>

Hub Server Installation in Console Mode in Oracle Environments

When you install the Hub Server in console mode in an Oracle environment, the pre-installation summary
has missing details. If you choose not to install Informatica Platform, a blank appears instead of the
word "No" under the Install Informatica Platform heading of the summary. (HORA-51944)

Upgrade from Version 9.5.1 in Oracle Environments

When you upgrade the Hub Server from version 9.5.1 in an Oracle environment, the upgrade completes
successfully, but the following error appears in the log:
19:26:22,012 INFO ImporterRole:44 - ddl: CREATE ROLE PROXY_ROLE ORA-01031: privileges
insufficient
You can safely ignore this error. (HORA-51980)

Hub Server Upgrade from Version 9.7.1 in Oracle and JBoss Environments
When you upgrade from version 9.7.1, the upgrade fails during the creation of a data source for
ActiveVOS.
Workaround: Open the <JBoss installation directory>/standalone/configuration/standalone-
full.xml file and enter comments around the lines of code that specify the ActiveVOS data source and
JDBC driver. (MDM-8616)

Oracle WebLogic 12.2.1.3 or later

When you use Oracle WebLogic version 12.2.1.3 with Multidomain MDM version 10.3, the following
additional steps are required to address some known limitations.
Apply a patch to WebLogic 12.2.1.3 or later
Ensure that your WebLogic 12.2.1.3 environment includes the following patch:
p26923558_122130_Generic.zip (MDM-18967)

8 2020-11-10
Configure the Java Virtual Machines for WebLogic 12.2.1.3 or later
To configure a Java Virtual Machine (JVM), set the Java options by using the JAVA_OPTIONS environment
variable.
You can set the Java options in the following file:
On UNIX. <WebLogic domain>/bin/setDomainEnv.sh
On Windows. <WebLogic domain>\bin\setDomainEnv.cmd
The following table describes the Java options:

Java Options Description

-Djavax.wsdl.factory.WSDLFactory Required to invoke a service WSDL that might have a default

namespace prefix.
Set to the following value:
com.ibm.wsdl.factory.WSDLFactoryImpl

-DANTLR_USE_DIRECT_CLASS_LOADING Required to launch the WebLogic Server on which the MDM Hub is
deployed. Set to true.

Update the Hub Server build properties

Edit the Hub Server build.properties file to set the following property:
weblogic.version=10.x
(MDM-22366)
Deploy the Resource Kit .ear files
If you install the Resource Kit, the .ear files are not deployed automatically. You need to edit the
classpath in the sip_ant script, run the post installation script, and deploy the .ear files from the
WebLogic Administration Console.
Note: The following example procedure refers to .sh files and uses the syntax for a UNIX system.
1. If the post installation fails, navigate to the following directory:
<MDM Hub installation directory>/hub/server/resourcekit/bin
2. Open the sip_ant.sh file.
3. Find the following text and delete $WLS_CLASSPATH :
$JAVA_HOME/jre/bin/java \
$USER_INSTALL_PROP \
-Xmx512m -classpath \
$SIP_HOME/deploy/lib/ant.jar:$SIP_HOME/deploy/lib/ant-launcher.jar:$SIP_HOME/
deploy/lib/ant-nodeps.jar:$WLS_CLASSPATH
\
org.apache.tools.ant.Main \
$PARAM
4. Save the file.
5. Run ./postinstall.sh -Dweblogic.password=<password>.
The process saves the generated .ear files in the following location: <MDM Hub installation
directory>/hub/serverresourcekit/bin/deploy/deployed_ears.

2020-11-10 9
6. Open the WebLogic Administration Console and deploy the generated .ear files.
(MDM-22847)

Hub Server Post-Installation Task on WebLogic Clusters

If you install the Hub Server on a WebLogic cluster environment with deployments only on Managed
Servers, manually create datasources after the installation. (MDM-10636)

Run the PostInstallSetup Script in Non-English Oracle and JBoss Environments

When you install in a locale other than English in an Oracle and JBoss environment, the
postInstallSetup script does not run during the installation process.
Workaround: Run the postInstallSetup script after the installation to deploy the EAR files. For more
information, see the Multidomain MDM Installation Guide. (MDM-8731)

JBoss Environments
The following issues affect Multidomain MDM when installed with JBoss and any database environment.

Hub Server Installation in JBoss Environments

When you deploy the Hub Server EAR files in a JBoss environment, the deployment might fail with the
exception concurrent.RejectedExecutionException.
Workaround: Increase the length of the task queue in the standalone-full.xml file. The following
sample shows the queue-length count parameter to modify:
<long-running-threads>
<core-threads count="50"/>
<queue-length count="300"/>
<max-threads count="50"/>
<keepalive-time time="10" unit="seconds"/>
</long-running-threads>
(MDM-13340)

Registering an Operational Reference Store on JBoss Clusters

In a JBoss cluster environment, to be able to register Operational Reference Stores, configure the
<datasources> definition in the standalone-full.xml file.
1. Open the standalone-full.xml file, which is in the following directory:
<JBoss Installation Directory>/standalone/configuration
2. Configure the <datasources> definition and save the changes.
(MDM-10952)

10 2020-11-10
Deploying the Data Director Applications on JBoss EAP 7.1
After you install or upgrade the MDM Hub in the JBoss EAP 7.1 environment, the deployment status of
applications might appear as failed in the Data Director Configuration Manager.
Use the Repository Manager tool in the Hub Console to ensure that all the Operational Reference Stores
are validated. After the validation, use the Data Director Configuration Manager to redeploy the
applications.
(MDM-24559, MDM-24415)

HP-UX, Linux, and Solaris Environments

The following issues affect Multidomain MDM when installed on the HP-UX, Linux, or Solaris operating
systems.

Informatica Platform support in Solaris and HP-UX Environments

You cannot use MDM Multidomain Edition with Informatica platform in Solaris and HP-UX environments.
(MDM-14971)

Hub Server Installation on HP-UX

When you install the Hub Server in an HP-UX environment, the postInstallSetup script fails.
Workaround: After the installation fails, run the postinstallsetup script manually. Alternatively, when
prompted to run the postinstallsetup script during the installation process, choose to run the
postInstallSetup script later. Later, run the postinstallsetup script manually. (MDM-11092)

Resource Kit Installation in Silent Mode

A silent installation of the Resource Kit fails in a Linux environment.
Workaround: Install the Resource Kit in graphical mode or console mode. (MDM-10803)

After You Install or Upgrade

Some known limitations can affect your install or upgrade experience. To avoid potential issues, ensure
that you review the following issues and complete any workarounds after you upgrade.

Upgrading the Operational Reference Store

When you upgrade the Operational Reference Store, the upgrade is successful but the following error
appears in the sip_ant log:
[exec] CREATE SEQUENCE "C_REPOS_ZDT_EVENT_SEQ" MINVALUE 1 MAXVALUE 99999999999999
INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER CYCLE
[exec] *
[exec] ERROR at line 1:
[exec] ORA-00955: name is already used by an existing object
[exec]
Workaround: You can safely ignore the error.
(MDM-14070)

2020-11-10 11
Change List Promotion
To promote a change list to an empty Operational Reference Store, the match column length that the
MDM Hub adds to the external match input table must not exceed 4000. The match column length is the
sum of the lengths of all base object columns that are sources of the match column and the number of
source columns.
The change list promotion fails with the following error if the total length of the match column is greater
than 4000:
ORA-00910: specified length too long for its datatype
(HORA-52116)

Updating a Localized Schema

If the pre-upgrade schema includes localized lookup tables, you might see validation errors after you
upgrade.
For lookup tables that were localized in version 10.2.x, the metatdata validation process generates the
following types of errors:
SIP-MV-22000 The name attribute for DB bundle [<lookup table name>.dbBundleMapping]
is not defined in the configuration
Workaround:
1. Download the dbBundleConfig.xml file from the C_REPOS_CO_CS_CONFIG repository table.
2. In the dbBundleConfig.xml file, and copy the name=<lookup table name> parameter from the
bundle element to the mapping element.
For example, the following snippet shows the edited mapping elements:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dbBundleConfiguration xmlns="http://www.example.com/mdm/db-bundle-configuration">
<bundle name="LUCountry" hubObject="C_LU_COUNTRY_LCL">
<mapping name="LUCountry" keyColumn="COUNTRY_CD" countryColumn="COUNTRY_CODE"
languageColumn="LANGUAGE_CODE" valueColumn="LOCALIZED_STRING"/>
</bundle>
<bundle name="LUState" hubObject="C_LU_STATE_LCL">
<mapping name="LUState" keyColumn="STATE_CD" countryColumn="COUNTRY_CODE"
languageColumn="LANGUAGE_CODE" valueColumn="LOCALIZED_STRING"/>
</bundle>
<bundle name="LUCountry.LUState" hubObject="C_LU_STATE_LCL">
<mapping name="LUCountry.LUState" keyColumn="STATE_CD"
countryColumn="COUNTRY_CODE" languageColumn="LANGUAGE_CODE"
valueColumn="LOCALIZED_STRING"/>
</bundle>
</dbBundleConfiguration>
3. Upload the edited dbBundleConfig.xml file to the C_REPOS_CO_CS_CONFIG repository table.
4. Run the metadata validation.

12 2020-11-10
(MDM-21752)

Multidomain MDM Hosted on Amazon Web Services

If Informatica Cloud Hosting Services manages your instance of Multidomain MDM on Amazon Web
Services (AWS), ensure that you review the following issue.

ActiveVOS MultiTenant Mode (MDM Multidomain Edition on Amazon Web Services)

When Informatica Cloud Hosting Services manages your instance of MDM Multidomain Edition on AWS,
the URLs include a customer identifier. ActiveVOS multitenant feature has a limitation with respect to
the URL change.
Workaround: Use the BE ActiveVOS worfklow adapter and add users to the TenantGroup role.
(MDM-15600)

10.3 HotFix 2
Fixed Limitations
MDM Hub Fixed Limitations
The following table describes fixed limitations:

Reference Description
Number

MDM-29387, When you enable SSL in an Oracle environment, the load job fails and the following error
MDM-28629 message appears:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=localhost)
(PORT=2484))(CONNECT_DATA=(SERVICE_NAME=orcl)))

MDM-29045 When a display package used by the Hierarchy Manager has aliases, the Hierarchy Manager fails
to create relationships and the following errors appear:
IP-10322: Error getting Entities and Relationships for:
HmDataObjectsRequests: Entities=PackageDataObjectMap: ,
Relationships=PackageDataObjectMap: 1 objects from PKG_RL_<BASE OBJECT>
package.
SIP-14150: Data access failure in searchQuery.
SIP-14147: Repository exception when running API request SEARCH QUERY
REQUEST.
java.lang.NullPointerException

MDM-28009 After you upgrade in WebSphere environments, access to WSDL URL, such as http://<host
name>:<port>/cmx/request/wsdl, fails intermittently.

MDM-27697 When you un-merge merged records, the Last Update Date does not update at the base object
level.

2020-11-10 13
 Reference Description
Number

MDM-27022 When a load process inserts records into a child table, the load job fails due to an incorrect SQL
formation and the child records are not marked as dirty.

MDM-26369 In the MDM Hub Console, parent records matched to child records fail to load into the child table
due to an incorrect SQL query formation.

MDM-25548 The expired MDM certificate is replaced with a new certificate.

MDM-25255 When you attempt to unmerge records with the UnMerge SOAP API, the lookup table acquires a
lock.

MDM-24439 When you run a match job for two addresses with different values using the SSA-NAME3 library
files, the records are matched.

MDM-24361 When you run a load job to update multiple records, the job forms large data clusters and each
PKEY record consumes excessive heap memory and time.

MDM-19685 When a load job updates a base object column with a null value, the job does not update the
LAST_UPDATE_DATE column.

MDM-11652 When you run the read database function to call an Oracle sequence, duplicate values are
generated instead of unique values.

Data Director Fixed Limitations

The following table describes the fixed limitations:

Reference Description
Number

MDM-29211 When you create a query that is based on a grandchild subject area, an error occurs.

MDM-28921 When you try to open a record in the Matches view, the following error appears:
SIP-10226: Error in building query to run MATCH.

MDM-28883 When you search for records that you want to add to as merge candidates, the performance of the
search operation is poor.

MDM-28335 In Match Settings, when you select an exact match and a fuzzy match and perform a search on
the records, the following error message appears:
SIP-10226: Error in building query to run MATCH verb. -99: Exception
During GetMatch :java.lang.NullPointerException

MDM-28308 Users can view unassigned Operational Reference Store (ORS) databases applications.

MDM-27215 When you import queries, some queries might fail to import.

MDM-26989 If you mark a field as read-only in a business entity, and attempt to edit the record in Data
Director, the read-only field is not visible.

14 2020-11-10
 Reference Description
Number

MDM-26714 When you create a child record by an external business entity service call, the Data Director Form
view creates a record with null values.

MDM-26528 In a Microsoft Excel file, if you edit the font of a cell data and import the file into Data Director,
the cell data displays a null value.

MDM-26432 When you merge multiple records, the following incorrect error message appears:
No duplicates found
You should see the following error message:
Merged sucessfully

MDM-25662 When you attempt to view cross reference records outside the specified effective date, the
records display an incorrect value in the XREF view.

MDM-24818 In the Hierarchy Manager, when only one relationship is configured with custom columns and
default values, the default values of the custom columns do not appear.

MDM-24225 When you change the effective date of records, the getOneHop API call cannot retrieve the
relationship records between the parent and child tables and displays an error.

MDM-24020 If you cancel an update task for business entities, the task does not delete data in the base object
and cross reference tables.

MDM-24018 When you approve a code value task for a future date, the following error message appears:
SIP-14377: Cannot generate the preview for the best version of the truth.
No best version of the truth is available.

MDM-24003 When you create a task approval workflow for a future date, you cannot open the task notification
that indicates that the task is approved.

MDM-22030 When you create a task and enter comments, you can only view the first task comment. Any
subsequent comments added to the task do not appear.

MDM-20603 When you run a merge task, the merge action fails and the following error message appears:
SIP-50225: The Interaction ID of a pending merge record does not match
the Interaction ID which was specified in the request.

MDM-18356 Cross-reference records created as a result of an update in Data Director do not unmerge or point
to an incorrect ROWID_OBJECT after an unmerge.

MDM-9830 In the XREF view, when you update a child record field for which trust is enabled, and the record
has a one-to-one relationship with the parent, the following exception occurs:
java.lang.ClassCastException:
com.siperian.dsapp.mde.domain.common.LogicalOne2OneChild cannot be cast
to com.siperian.dsapp.mde.domain.common.PrimaryObject

2020-11-10 15
Data Director with Business Entities (E360) Fixed Limitations
The entity views are based on business entities.
The following table describes fixed limitations:

Reference Description
Number

MDM-29693 When a search query is based on an integer field, the query does not return results.

MDM-29033 If you log in through single sign-on (SSO) and export query results, a null pointer exception is
generated.

MDM-28555 In a record view, values that you select from dependent lookup fields do not persist.

MDM-28182 When you delete a value in a required field and save the record with a null value, the record does
not display an error message.

MDM-28063 When Data Director is configured with a State Management Override System (SMOS) and you set
the end date of a relationship in the Hierarchy Manager, the cross-reference records for all the
periods are soft-deleted.

MDM-28045 When you select a child record of a merge candidate that has one-to-many child relationship, the
SIP:50022 error is generated during the generation of the merge preview.

MDM-27971 After a record is successfully approved in Data Director, the record state does not change from
pending to active in the database. The ActiveVOS workflow fails to promote the record to the
active state.

MDM-27743 If you mark a field as read-only in a business entity, a Cleanse transformation on that field fails.

MDM-26054 When field filters are configured for business entities, performance of the associated tasks is
poor.

MDM-27383 When you perform a search in E360 to view only active records, you can see active and pending
records

MDM-27742 If you publish a custom layout, the read-only field appears as an editable field.

MDM-27039 In Data Director, when you update an existing record, the Save button is disabled.

MDM-26918 When you include special characters in a query search, the search does not return any records.

MDM-26671 You cannot update an existing column in a child record if the columns are at the business entity
root level.

MDM-26528 In an Excel sheet, if you edit data in a cell and import the Excel file to Data Director, the cell data is
treated as null and does not display.

MDM-26317 When you update a business entity, the following error message appears:
com.informatica.tools.mdm.service.entity360view.componentconfig.
ComponentConfigService: Either there is no configuration for component
present
or XML is malformed

MDM-26528 The Smart Search filter does not apply when you search for records.

16 2020-11-10
 Reference Description
Number

MDM-26153 In the Matching Records view, you do not have the option to select all records.

MDM-26008 When you claim and reject an approval task, the delete pending service in ActiveVOS fails and the
record is marked as dirty. This issue occurs when you set the STRIP_INCOMPLETE_IND field value
to 0 in the C_REPOS_TABLE.

MDM-25950 In Data Director, the business entity label displays a random date instead of the label name. This
issue occurs when you enter a numerical value in a field that is defined with the data type as
VARCHAR.

MDM-25850 If a column is null and you want to populate the column with a unique value using the cleanse
function, the column does not populate.

MDM-25425 When you access Data Director using the HTTPS protocol, in the web debugger, the following
response header tag does not appear for all URLs:
-Dstricttransportsecurity.flag

MDM-25412 When you create a new record and select a custom date range in the Creation Date field, the
following error displays: The data must be in the valid format.

MDM-25257 Child records do not display in the History view. This issue occurs when you view parent-child
records with one to many relationships.

MDM-25303 In the Task Manager, when you attempt to filter the creation date, incorrect date numbers display.

MDM-25261 In Data Director, when the search results contain cross reference records, child entities do not
display.

MDM-25260 When you search for cross-reference records, the Matching Records view does not display child
entities.

MDM-25259 Labels configured for business entities in the Provisioning Tool do not display in Data Director.

MDM-25219 In the Matching Records view, child records do not merge with parent records and display the
following error:
SIP-50218: Unable to run the merge process on the child. The merge process
must run successfully on the parent before it can merge the child. In the
merge request, add the parent records with rowids.

MDM-25099 In the Task Manager, if you create a new task, it does not appear as the latest created task under
All Tasks.

MDM-24952 The Cross-reference Records view displays incorrect child entity label names.

MDM-24827 Multiple functions in Data Director fail in a WebLogic 12.2.1.3 cluster environment.

MDM-24753 In a hosted MDM environment, when you perform a query search and click the next page in the
search results, a 404 error occurs.

2020-11-10 17
 Reference Description
Number

MDM-24532 In Data Director, when you approve a task, the records edited by the user highlight at the record
level and not the field level.

MDM-24518 When you unmerge a record with a large number of cross-reference records associated with it, the
unmerge process fails.

Provisioning Tool Fixed Limitations

The following table describes fixed limitations:

Reference Number Description

MDM-24297 If you make any change in the Provisioning tool, the elastic search index is automatically
deleted.

Search Fixed Limitations

Formerly called Smart Search, you can power the full-text search function with Elasticsearch or Solr.
The following table describes fixed limitations:

Reference Description
Number

MDM-29248 After you update searchable lookup values of records, the values in the index are not
refreshed.

MDM-28832 After you update searchable lookup values of records, search for records based on the updated
lookup values fails. The log file contains the following error:
SIP-52015: Failed to index the document. Invalid column index

MDM-28599 In Data Director, If you login to a new session, the search value from the previous login session
does not appear in the drop down list.

MDM-28522 In a Microsoft SQL Server environment, when part of a base object column name uses the
reserved word FROM, such as in FROM_ENTITY, the Initially Index Smart Search Data job fails.

MDM-26301 When you perform a manual merge, the search results display duplicate record entries.

MDM-24606 When you use the Elasticsearch engine to search for certain records using keywords, the
search results display the records in an incorrect order.

MDM-24297 If you make any change in the Provisioning tool, the Elasticsearch index is automatically
deleted.

18 2020-11-10
API Services Fixed Limitations
The following table describes fixed limitations:

Reference Description
Number

MDM-26786 When you use the GetOneHop SIF API without the EffectiveDate parameter, the following error
message appears:
SIP-14105: Unexpected error occurred while processing request:
GetOneHopRequest

MDM-23038 When you delete an existing XREF root record using the executeBatchDelete SIF API, a new XREF
root record is created. However, the record does not update in the C_REPOS_MQ_DATA_CHANGE
table.

MDM-21087 An ExecuteBatchUnmerge SIF API call with EXPLODE_NODE_IND set to 1 fails to unmerge a base
object correctly. After the unmerge, the foreign keys of the child base object point to an
incorrect ROWID_OBJECT value of the parent base object.

MDM-19478 When you run the Update Relationship REST API to update a child record of a Hierarchy Manager
relationship, if the source key is new, the API creates a new record instead of updating the
record.

Closed Enhancement Requests

MDM Hub Closed Enhancement Requests
The following table describes closed enhancement requests:

Reference Description
Number

MDM-26214 Data encryption and decryption support added for match operations.

MDM-27167 When you run a match job query on a large volume of data, the query runs successfully.
Previously, the query was unresponsive after scanning the T$MMA_BO_PARTY table.

MDM-26984 When you click the MDM Hub Console URL to login, the X-Frame-Options CMX header is not
set.

2020-11-10 19
Known Limitations
Data Director Known Limitations
The following table describes known limitations:

Reference Description
Number

MDM-30175 When you use multiple tabs to create records and click the Apply button, the records do not
save.

MDM-30318 When you open a large number of cross-reference records, the following error message appears:
com.siperian.common.db.SipSQLException: ORA-01795: maximum number of
expressions in a list is 1000

7 1090598158 prepareStatement( SELECT * FROM C_BO_PRTY_LCTN_XREF WHERE

ROWID_XREF in

Business Process Management Known Limitations

The following table describes known limitations.

Reference Number Description

MDM-26897 When you install ActiveVOS, the admin user password is stored in plain text in the
ActiveVos installation properties file.

API Services Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-30165 When you restore deleted records using the POST Update API, the BVT calculation does not
trigger, and restored record values are incorrect.

MDM-30316 When you create a custom query and use the SearchQuery SIF API to search for records, you
receive an incorrect API response.

20 2020-11-10
10.3 HotFix 1
Fixed Limitations
MDM Hub Fixed Limitations
The following table describes fixed limitations:

Reference Description
Number

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

MDM-24396 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

MDM-24262 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.

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

MDM-24053 Prevent possible SQL injection in the Support tool.

MDM-23895 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.

MDM-23858 The fuzzy search operations consider the GETLISTLimit property but ignore the
MDM-9293 cmx.server.match.max_return_records_searcher property to limit the number of
records that are returned.

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

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

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

MDM-23317 Fixed a security issue.

MDM-18807

MDM-23316 When you run an external match on IBM DB2, the process creates a temporary table on the
MDM-16183 schema and generates the following error:
SIP-16107: SQL Exception. Error was: DB2 SQL Error: SQLCODE=-552,
SQLSTATE=42502, SQLERRMC=PMDMWAS;IMPLICIT CREATE SCHEMA, DRIVER=3.69.49
CREATE TABLE SESSION.T$MA_6061757004406685149088310 AS

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

2020-11-10 21
 Reference Description
Number

MDM-23295 When you use the MdmKeyStore class, a file descriptor leak causes FileNotFoundException
MDM-20337 errors.

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

MDM-23271 After the automation tool is finished running, the tool retains a write lock on the schema.
MDM-17191

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

MDM-23100 After you use the Hub Console to run a batch group that contains load jobs, the logs do not
MDM-6419 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.

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

MDM-23073 When you promote changes in the Hub Console, the promote process is slower than expected.
MDM-19485

MDM-23056 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.

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

MDM-22964 When you use the createUsers script, you experience performance issues.
MDM-17673

MDM-22846 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.

MDM-22255 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.
Unable to reproduce this known limitation in this release.

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

MDM-21644 After the automation tool is finished running, the tool retains a write lock on the schema.
MDM-17191

MDM-21437 After you select a record as not a match in Data Director, when you run the Auto Match and
MDM-15955 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.

22 2020-11-10
 Reference Description
Number

MDM-21436 For custom queries, after you run a Load job with the Force Update option and a Revalidate job,
MDM-15987 the validation rule does not execute correctly.

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

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

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

MDM-21008 In an IBM DB2 database environment, if you modify a base object in the database, and then try to
MDM-16451 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

MDM-20892 After you set the password policy and enable the Restrict password reuse limit option, when you
MDM-19837 add a new user, the following error occurs:
SIP-10318: Cannot manage password history due to data access error.
Unable to reproduce this known limitation in this release.

MDM-20062 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.

MDM-19652 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.

MDM-19610 The Stage job rejects some records with the following error:
MDM-17362 SIP-11083: Cannot load class.

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

MDM-18455 The titles of unmerge tasks that are created in Data Director are saved as {$title} in the
MDM-17622 aeb4ptask table of the ActiveVOS schema.

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

MDM-17438 A user with read only access can claim tasks.

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

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

2020-11-10 23
Data Director Fixed Limitations
The following table describes fixed limitations:

Reference Description
Number

MDM-24693 In multi-node clustered environments, logging in to a Data Director application might fail
because of session management replication issues.

MDM-24460 You cannot log in to Data Director using Okta single sign-on.

MDM-24114 When you launch a Data Director application in Chrome, if the field values of a record are
MDM-24033 long, the values overlap adjacent fields.

MDM-24011 If your user password contains spaces, you cannot log in to Data Director.

MDM-23346 An LDAP user that is not registered in the MDM Hub cannot log in to Data Director.

MDM-23115 If the first name and last name of a user registered in the Hub Console is in Japanese, the
user cannot log in to Data Director.

MDM-21672 In a hosted MDM environment, when you log out of Data Director, clear the browser cache,
MDM-21974 and then refresh the tab where you logged out, a 404 error occurs.
MDM-21826

MDM-21390 If you change your password and then run a newly claimed unmerge task, the unmerge
MDM-16226 process does not run on the records, but an interface message says that the unmerge is
successful.

MDM-21388 In the task inbox on the Home page, you cannot filter tasks by the creation date.
MDM-15945

MDM-19053 If you use Apache HTTP Server, Data Director applications take a long time to load.
MDM-16775

MDM-18712 The export of search results fails.

MDM-17065

Data Director with Business Entities (E360) Fixed Limitations

The entity views are based on business entities. To use these views, upgrade Data Director applications
from subject areas to business entities.

24 2020-11-10
The following table describes fixed limitations:

Reference Description
Number

MDM-24394 When a cleanse transformation is used with a business entity view to business entity
transformation, the following issues occur:
- After you create records, the records fail to appear in the business entity view.
- You cannot open records from query results.

MDM-24283 The record views that are configured for specific user roles cannot be accessed by LDAP users
with the same roles.

MDM-24205 When a child record with a one-to-many relationship in the parent business entity has a one-to-
one relationship in a business entity view, the record does not appear in the Business Entity
view. The same record appears in a Record Preview page that you open from the Search
Results page.

MDM-23927 The Related Records component that lists related records does not honor the direction of the
relationship between records. The issue occurs only with record view layouts that use the
Related Records (View Mode) component. To fix the issue, the component and it's properties
were updated in the Provisioning tool. For more information, see the Release Guide and the
Provisioning Tool Guide for the release.

MDM-23776 After tasks are added, the task count in the Task Manager does not refresh automatically.

MDM-23763 In the Business Entity view, the vertical scroll bar for the quick scroll panel does not align
correctly.

MDM-23762 When you create a record and click Save multiple times, the Task Comment and Attachments
dialog box appears for each click.

MDM-23708 In the Matching Records view, when you identify duplicate records that you want to merge with
the target record, the following error might be generated:
java.math.BigDecimal cannot be cast to java.lang.String

MDM-23677 When you open a merge task, the performance is slower than expected.
MDM-23676

MDM-23542 When you attach a file to a task, if the file name contains non-Latin characters, the file name is
modified and the file cannot be downloaded.

MDM-23530 The documents attached to a record in the Business Entity view are not visible when tasks
related to the record are opened in the Task Manager.

MDM-23500 When external calls are configured with localized messages for the Data Director application,
the localized messages do not appear.

MDM-23456 In the basic Matching Records view, columns such as Merge Preview might not be aligned
correctly.

MDM-23455 When you use a search query to find records, the query results do not include the values of
dependent lookup fields.

MDM-23417 When you customize the search results using the Customize Search Columns dialog box, tool
tips for the Add all and Remove all icons do not disappear after the click.

2020-11-10 25
 Reference Description
Number

MDM-23369 In the task inbox, the Creation Date filter works only for a specific date.

MDM-23350 In the localized applications, the Overdue option of the task inbox Due Date filter does not
appear in the localized language.

MDM-23408 If a cleanse transformation is used with a view to business entity transformation, updates to
records might generate a validation error.

MDM-23333 When you edit and save a record that contains Unicode characters, the Unicode characters are
corrupted.

MDM-23322 In the Business Entity view, long names are not formatted correctly as the label for the record.
MDM-23072
MDM-22479
MDM-16936
MDM-17169

MDM-23318 Multibyte localization data does not appear correctly as field labels.
MDM-18622

MDM-23310 When you make a Cleanse SIF request, the Informatica Data Quality cleanse function does not
MDM-20887 return values.

MDM-23282 In the Related Records component, the record count is incorrect.

MDM-20677

MDM-23261 The search and queries results do not show lookup values when the foreign key is set to
ROWID_OBJECT.

MDM-23260 In the Hierarchy view, when you click Add to Canvas, the dialog box that opens is small and not
user-friendly for viewing the search results.

MDM-23259 In the Task Manager, when you claim a task from the task panel, the panel does not
automatically change to My Open Tasks.

MDM-23245 When the search results contain records with integer and date fields, sorting on these fields is
incorrect. Instead of numeric or date sorting, string sorting is applied.

MDM-23244 When the search results page has a vertical scroll bar, you must scroll to the right to use the
Show preview and Open in a new window icons.

MDM-23222 With Internet Explorer, when you create a new record, the icons for the child entity are not
MDM-23034 visible. This issue can not be reproduced in this release.

MDM-23217 When you use the Form view to add or edit a child record, the data is not cleansed and
standardized.

MDM-23216 The Cross-reference Records view has redundant blank spaces and a horizontal scroll bar.
MDM-23211

MDM-23215 In the Business Entity view, when you select an item on the quick scroll pane, all the items
scroll off the screen.

26 2020-11-10
 Reference Description
Number

MDM-23214 Even though a default image is configured for the image field of a view, the default image does
MDM-22941 not appear when an image is not attached.

MDM-23212 In the child record sections of the Business Entity view, the filter icon appears even though the
sections have no records.

MDM-23201 The task inbox has unnecessary horizontal scrolling.

MDM-23184 When you configure an application so that only some business entities are visible, all business
MDM-16753 entities appear in the Search box in the application header.

MDM-23177 Fixed a security issue.

MDM-20889

MDM-23156 When multiple levels of dependent lookup fields exist, the second and later levels of the lookup
fields display all the items instead of displaying the items associated with the selected lookup
field.

MDM-23143 When lookup fields are configured as searchable, with ROWID_OBJECT as the display field,
when you select the fields, the Search Results page does not appear.

MDM-23134 When smart search is enabled and the search results views are configured for an application,
search results are not displayed for the Related Records component. The issue occurs only with
the Related Records (View Mode) component.

MDM-22966 In the Matching Records view, after you click Merge, the button is not disabled. You can click
Merge again and a new merge process is initiated.

MDM-22947 When the Home page displays the list of available tasks in the task inbox, you need to
horizontally scroll through the task inbox to view all the details of a task.

MDM-22940 The review panel of the Task Manager has multiple vertical scroll bars.

MDM-22928 The History view has extra space around the page.

MDM-22833 In the advanced Matching Records view, when you open a calendar, the calendar might hide the
date field associated with it.

MDM-22776 When the language of the user interface is French, the Compare button in the Similar Records
component is misaligned.

MDM-22772 In the Task Manager, the Search box for tasks does not display the complete field input hint.

MDM-22759 When the user interface is set to some localized languages and you set a query as the default
query, the bad layout error is generated.

MDM-22757 In some of the localized languages of the user interface, when you try to view the history of a
record in the Hierarchy view, the layout of the user interface is messed up.

MDM-22753 In the localized versions of the application, some user interface elements of the task inbox are
not localized.

2020-11-10 27
 Reference Description
Number

MDM-22738 In the Cross-reference Records view, users that do not have the privileges to view the cross-
reference records of specific business entities, can view the associated child records in the
navigation tree.

MDM-22329 The dependent lookup fields of child records do not display correct values in the value list.

MDM-21229 Verbose error message could potentially leak information.

MDM-20057 In the History view, the record events that you select are not highlighted.

MDM-18817 The Cross Reference page and the Merge Preview page have pagination issues.
MDM-17865

MDM-18597 When a user role does not include the create and read privileges for a business entity, users
MDM-17509 with this role can still view the tasks associated with the business entity.

MDM-18009 If there are many comments associated with a task, the following error might occur:
MDM-16713 Comments cannot exceed more than 3968 characters.

MDM-16846 In the Business Entity view, child record fields are not aligned.

MDM-15299 If you do not enable validation for a record though a validation check can be performed, the
validation status is not set to null.

MDM-15172 In the Business Entity view, the first record of each child node is highlighted.

MDM-15077 When character data is entered in a numeric field, the following misleading error message
appears:
Enter a Valid Pattern.

MDM-4710 In the Business Entity view, when you add data to a business entity and then click Apply, the
Hub Server does not clean and correctly format the data.
Workaround: For your data to appear in the correct format in Business Entity view, click the
Save button.

Data Director with Subject Areas Fixed Limitations

The legacy views are based on subject areas.
The following table describes fixed limitations:

Reference Description
Number

MDM-24491 When you approve tasks, you cannot attach files that have file names with special characters,
such as %.

MDM-24443 The promotion of a change list with the Data Director configuration fails.

28 2020-11-10
 Reference Description
Number

MDM-24403 You cannot delete a child subject area record and send it for approval.
MDM-23973

MDM-24349 When you open tasks, the following error might be generated:
MDM-24062 java.math.BigDecimal cannot be cast to java.lang.String

MDM-24333 When a record is opened in the Effective Periods View, tool tips for the timeline events do not
show the configured timeline granularity.

MDM-24263 When you create and save a basic query at the subject area group level and include
relationship base object columns, an error occurs.

MDM-24150 When you create a record or a query, the dependent lookup fields do not show correct values.

MDM-24142 After records are merged, the UPDATED_BY column of the base object and the cross-reference
record is null.

MDM-24111 When you customize the query results to view specific fields, the customization is not
preserved when you navigate away from the results page.

MDM-24083 After you upgrade, the business entity schema generation might fail in the following scenarios:
MDM-23219 - If a subject area has duplicate default values and different roles configured, the business
entity schema generation fails with the following error:
MDM-23218 ERROR||Validation failed for some objects in the object tree|The
bddApplication name must be set.
- If subject areas have default values set to null or empty strings, the business entity schema
generation fails with a null pointer exception.

MDM-24048 When you view the history of a record, the history of child records does not appear.

MDM-23983 When you open a record in the XREF view and click the Details tab to view child record data, an
error occurs.

MDM-23918 Even though the timeline granularity is set to seconds, you cannot open a record that is
MDM-23590 effective up to a specific time in seconds, because the Open for Effective Date dialog box
does not allow you to specify time in seconds.

MDM-23916 The task inbox does not display the task details icons beside the tasks.

MDM-23798 The Hierarchy view takes a long time to display the history of records that have many
relationships.

MDM-23653 When you export the results of a query, the values of lookup columns that are not marked as
lookups in a timeline enabled base object are not exported.

MDM-23640 When a timeline enabled base object has lookup columns that are not marked as lookups, the
Cross-reference Records view generates the following error:
SIP-10228: No record found for the specified RecordKey.

MDM-23639 When a timeline enabled base object has lookup columns that are not marked as lookups, in
the History view, you cannot view the cross-reference change details and the base object
change details for events. An error occurs.

2020-11-10 29
 Reference Description
Number

MDM-23617 When subject areas and lookup tables have the same names, the business entity schemas are
MDM-23586 not generated correctly. The issue occurs even though the names have different character
cases.

MDM-23610 When the number 0 is stored in the DB2 database with a scale of 3, such as 0.000, the scale is
not preserved in the record views. The value appears as 0.

MDM-23580 When a timeline enabled base object has lookup columns that are not marked as lookups, a
search for records based on lookups generates the following error:
SIP-14150: Data access failure in searchQuery. ORA-00918: column
ambiguously defined.

MDM-23495 When you use a profile to export search results for a specific effective period, the exported
data is not for the same effective period.

MDM-23494 When you apply data masking on a column, the data is still visible on the History tab for base
object change details and XREF change details.

MDM-23487 You cannot send a task for approval because the business entity schema is generated
incorrectly.

MDM-23440 When the Subject Areas option is the only option in the New window, the Subject Areas option
is not selected by default.

MDM-23343 The Expand and Collapse icons appear incorrectly for the logical subject area groups.

MDM-23325 The values of a dependent lookup with a subtype qualifier does not filter correctly.

MDM-23319 When you use data security filters without state management, you cannot open records.
MDM-17374

MDM-23315 When you add a hyperlink that contains the @ character, Data Director parses the text
MDM-18399 incorrectly and saves an incorrect hyperlink.

MDM-23314 Fixed a security issue.

MDM-19479

MDM-23313 When you run a query that is case insensitive and then try to sort the records, an error occurs.
MDM-20112

MDM-23311 Task actions are disabled for users with uppercase user names.
MDM-20663

MDM-23309 When a package contains a join to a second package, a query on the first package fails.
MDM-20388

MDM-23303 You can edit a child record and a grandchild record at the same time. If you apply the edit to
MDM-21428 the grandchild record, but cancel the edit for the child record, a NullPointerException is
generated.
MDM-5335
Unable to reproduce this known limitation in this release.

30 2020-11-10
 Reference Description
Number

MDM-23296 When you add values to dependent lookups that have no values and send the changes for
MDM-17378 approval, the approval task cannot be opened.
MDM-21361

MDM-23220 Child records do not display in the History view. The following error is logged in the
cmxserver.log:
SIP-14159 "Data access error when trying to process SEARCH QUERY
REQUEST"

MDM-23155 You cannot import queries from versions prior to 10.3.

MDM-23919

MDM-23153 When a package contains a join to a second package, any query on the first package fails.
MDM-20388

MDM-23152 Generating a business entity schema takes a long time.

MDM-23140 When HAProxy is used with Multidomain MDM, a search for records in Data Director fails and
the Data Director Configuration Manager does not launch. The 502 bad Gateway error
occurs.

MDM-23117 If a subject area has security filters that include colons (:) in the definition, the business entity
configuration generated by the MDM Hub causes the Operational Reference Store (ORS)
metadata validation to fail.
The following error is generated:
SIP-MV-13042 Object name contains special
characters.
After the fix, the colons in the security filter are replaced with underscores. For example, the
security filter URN:LSID:gsk.com/rd:list.DEX:582 is changed to
fv_URN_LSID_gsk_com_rd_list_DEX_582.

MDM-23080 The getChangedChildren API returns incorrect results at the grandchild level.
MDM-17575

MDM-23077 Logical subject area groups with 2 levels do not work.

MDM-22990 After upgrading from version 10.1, when you use the Data Director Configuration Manager to
generate the business entity schema, misleading warnings and information messages appear.

MDM-22169 When you validate applications in the Data Director Configuration Manager, if the validation
messages run into multiple lines, the complete message is not visible.

MDM-23074 Saved query columns use the package attribute for the column instead of the subject area
MDM-20106 attribute, which causes errors during search.

MDM-23068 When you create a merge task and select a record to merge, the lower RowId Object value
MDM-15988 incorrectly appears in the Merge Preview.

MDM-22880 After you open a task, you cannot see updated data.
MDM-19581

2020-11-10 31
 Reference Description
Number

MDM-22855 In the Hierarchy Manager, when you manage a relationship and try to enter a value in the cust
MDM-20359 col field, the value reverts back to the default value.
MDM-23071

MDM-22781 When you use the Hierarchy Manager to create an entity, the entity does not display in the
MDM-18144 canvas.

MDM-21793 When you create a record, potential matches do not appear.

MDM-21085

MDM-21427 You can edit a child record and a grandchild record at the same time. If you apply the edit to
MDM-17061 the grandchild record, but cancel the edit for the child record, a NullPointerException is
generated.

MDM-21421 In an Oracle database environment, when you open the event details from the History view, the
MDM-18126 following error occurs:
ORA-01722: invalid number

MDM-20729 In the task inbox, you cannot filter tasks by the creation date.

MDM-19980 In the XREF view, the search runs with administrator privileges instead of the logged in user
MDM-20524 privileges.

MDM-19956 Merge task actions are disabled for users with uppercase user names.

MDM-19608 In all the data views, white space is not preserved in the data fields.
MDM-17267

MDM-19421 If you exceed the maximum length of a text field, no validation error is displayed.
MDM-18325 Unable to reproduce this known limitation in this release.

MDM-18854 In the History view, when you try to view an event detail, an error might occur.
MDM-16419

MDM-18680 In applications with multiple subject areas, tasks assigned to a user do not appear in the task
MDM-15764 inbox.
Unable to reproduce this known limitation in this release.

MDM-18632 When you run a search query with a specified effective date, the search results display
MDM-16464 incorrect values for records from a child subject area.
MDM-16240

MDM-18483 Users cannot open the tasks that are created by the secondary workflow engine.
MDM-16552

MDM-18442 When lookup columns from a child table are included in an advanced search query, the search
MDM-16527 result does not contain the values of the lookup field from the child table.
Unable to reproduce this known limitation in this release.

32 2020-11-10
 Reference Description
Number

MDM-18260 After you create a record, you cannot edit or save the record.
MDM-17386

MDM-18163 You cannot use a custom profile or multithreading to export search results.
MDM-17508 Unable to reproduce this known limitation in this release.

Provisioning Tool Fixed Limitations

The following table describes fixed limitations:

Reference Description
Number

MDM-24323 If you modify any configuration using the Provisioning tool, the Elasticsearch indexes are
deleted.

MDM-23927 The Related Records component that lists related records does not honor the direction of the
relationship between records. The issue occurs only with record view layouts that use the
Related Records (View Mode) component, which is configured using the Provisioning tool. To
fix the issue new configuration properties have been introduced in the Provisioning tool.

MDM-22754 In the localized versions of the Provisioning tool, some user interface elements are not
localized.

MDM-22329 Field filters are not valid on dependent lookup fields.

MDM-20752 You cannot change the default calendar format used in the History view.

Search Fixed Limitations

Formerly called Smart Search, you can power the full-text search function with either Elasticsearch or
Solr.
Search with Elasticsearch
The following table describes fixed limitations:

Reference Description
Number

MDM-24323 If you modify any configuration using the Provisioning tool, the Elasticsearch indexes are
MDM-24297 deleted.

MDM-24312 When you run the Initially Index Smart Search Data job, the Elasticsearch indexes are deleted.

MDM-24135 After applying a filter, the filter count for referenced columns is not updated.
MDM-24087

2020-11-10 33
 Reference Description
Number

MDM-23976 When a parent business entity is also a one-to-one child of another business entity and both
MDM-23931 have some searchable fields in common, the Initially Index Smart Search Data job fails.

MDM-23835 When you use accented characters in the search string, records are not found.

MDM-23533 When a base object has a large number of root records, indexing lookup tables might
generate an out of memory error.

MDM-23227 After you change the base object class code, search results display duplicate record entries.

MDM-23189 When more than 50 searchable fields are configured for a business entity, indexing fails.

MDM-23188 When you perform a search, the MDM Hub ignores common words such as "and", "an", and
"is". These are stop words, which are not filtered out by the suggester.

MDM-23182 If you make changes to a lookup for a record, reindexing for the record fails.
MDM-18540

MDM-23093 When records contain dependent lookups, the load update process takes longer than
expected to index the records.

MDM-22963 Duplicate records appear in the search results even after the duplicate records are merged.

Search with Solr

The following table describes fixed limitations:

Reference Number Description

MDM-23293 When you have two process servers in a node with Smart search enabled, search fails with
MDM-22230 errors.

MDM-23185 A smart search query that includes AND or OR in the search string fails.
MDM-16751

MDM-19005 When search is enabled, if you search for a record after merging some records, duplicate
MDM-17370 records might appear in the search results page.

API Services Fixed Limitations

The following table describes fixed limitations:

Reference Description
Number

MDM-24593 When a root record is updated by a business entity services call, field values from a child record
with a low trust score can be the surviving record value.

MDM-24497 When a parent record that has multiple child record levels is unmerged, the records at the
grandchild level are assigned an incorrect foreign key.

34 2020-11-10
 Reference Description
Number

MDM-24474 In a WebSphere environment, the ReadBE business entity service generates the following error:
SIP-50101: You do not have the required privileges to view the business
entity SupplierProductServices. To request additional role privileges,
contact your MDM administrator.

MDM-24473 In an IBM DB2 environment, the GetLookupValues SIF API generates the following error:
SIP-14129: The unique ID is not valid. The UID format must be "<table
name>|<column name>".
SIP-10323: There is no column with the name <Lookup column name>.

MDM-24426 The Search Record REST API returns deleted child records.

MDM-24405 A call to the Tokenize API fails with the following error: SIP-16011: Failed to gather
MDM-21634 metadata

MDM-23827 Even though a POST request to the WriteBE business entity service updates a single child record
MDM-23771 or a parent record field, the lastUpdateDate value for the parent record and all the child records
of a business entity are updated.

MDM-23500 When external calls are configured, validation messages do not appear in the localized
languages.

MDM-23076 Multithreaded SearchMatch API requests fail with errors.

MDM-17834

MDM-23067 When you use the registerCustomTableObject SIF API to register custom jobs on staging tables,
MDM-16108 you cannot add or remove the jobs in the batch group.

MDM-22938 The defaultPageSize and recordsToReturn parameters do not work for the Search Record
REST API.

MDM-22885 When you use the Delete SIF API to delete a child record, the deleted child record incorrectly
MDM-16249 matches in a match job.

MDM-21398 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.

MDM-21229 Verbose error message could potentially leak information.

MDM-23547 A second level dependent lookup ignores the parent dependency and returns all values.
MDM-23156
MDM-22878

MDM-23052 After JVMs are restarted, servers are incorrectly marked as fully started even though some
MDM-19071 modules did not complete initialization.

2020-11-10 35
 Reference Description
Number

MDM-19768 Occasionally, when you run SIF commands on cross-reference records, the following error
MDM-19186 occurs:
SIP-40609: Cannot edit the record.
The PERIOD_REFERENCE_TIME that you specified is not within the effective
period for the record you are editing.

MDM-19587 After the executeBatchUnmerge SIF API runs, the relationship between C_B_PARTY and
MDM-17086 C_B_PARTY_ALT_ID is not set correctly.

MDM-18915 When an exact match rule includes columns from child records, the Find Duplicates operation
MDM-16881 returns child records that do not match.

MDM-18436 The Delete Business Entity REST API cannot delete child records in a business entity. The REST
MDM-16422 API fails with a null pointer exception.
MDM-24032

MDM-18166 If you use the depth parameter when you implement pagination, a REST API request does not
MDM-16683 return any results.

MDM-17744 REST calls fail when the global identifier (GBID) contains the hyphen (-) character.
MDM-14690

MDM-16921 The search REST API performance is poor when you retrieve multiple business entity records with
depth > 2. To fix this issue, the cmx.server.enrichcopager.thread_pool and
cmx.server.enrichcopager.min_rec_for_multithreading properties are introduced.

Closed Enhancement Requests

MDM Hub Closed Enhancement Requests (10.3 HF1)
The following table describes closed enhancement requests:

Reference Description
Number

MDM-23396 Oracle Database 18c is supported for Multidomain MDM 10.3 HotFix 1.

MDM-23203 Informatica ActiveVOS 9.2.4.5 is supported for Multidomain MDM 10.3 HotFix 1.

MDM-22997 You must deploy Multidomain MDM on IBM WebSphere Application Server Version 9.0 Fix Pack
10. Multidomain MDM 10.3 HotFix 1 does not support WebSphere versions earlier than 9.0 Fix
Pack 10.

MDM-22899 You must deploy Multidomain MDM on Red Hat JBoss Enterprise Application Platform (EAP)
7.1.
Note: The end of maintenance support by Red Hat for JBoss EAP 6.x is June 2019. You are
recommended to upgrade to JBoss EAP 7.1 and Multidomain MDM 10.3 HotFix 1 for continued
support, bug fixes, and security patches from Red Hat. Multidomain MDM 10.3 HotFix 1 does
not support JBoss EAP versions earlier than 7.1.

36 2020-11-10
 Reference Description
Number

MDM-22798 You can run Multidomain MDM 10.3 HotFix 1 on Red Hat OpenJDK 8 in a JBoss application
server environment.

MDM-22840 When a cross-reference record is restored, the MDM Hub can trigger a message to be placed in
MDM-12129 the JMS message queues.
To set up message triggers for an event that restores a cross-reference record, use the Schema
Manager. In the Events section of the Message Triggers page, select Restore, which is the new
event included in the section.

MDM-21658 In the Resource Kit, the AssignUsersToDatabase script was updated to support uppercase
MDM-16901 characters in user names.

Provisioning Tool Closed Enhancement Requests (10.3 HF1)

Enter a short description of the concept here (required).
The following table describes closed enhancement requests:

Reference Description
Number

MDM-23946 You can copy a business entity or a business entity view and save it with a unique name. The
copy inherits the entire model from the original business entity or business entity view. In the
copy, you can add, edit, and remove fields from the model as required.

MDM-22815 You can use the Application Editor in the Provisioning tool to configure the default date format
used by the Data Director application. Also, you can configure the display format as Date or
Datetime for specific date fields in the business entity and reference entity model. The
configured date formats appear in all the record views.

MDM-22146 Enhanced the performance of the Provisioning tool by improving the response time.

MDM-21855 You can customize the messages that appear when tasks are triggered in Data Director. You
can also localize the messages.

2020-11-10 37
Data Director Closed Enhancement Requests (10.3 HF1)
The following table describes closed enhancement requests:

Reference Description
Number

MDM-18259 The getChangedChildren method that was added to the Save Handler user exit in
MDM-16206 versions 10.1 HF5 and 10.2 HF2 is available in this release.

MDM-16761 The deleteMovedRelInExplorerView preference that was added in version 10.1 HotFix 5
MDM-15751 is available in this release.

Known Limitations
MDM Hub Known Limitations
The following table describes known limitations:

Reference Description
Number

MDM-24156 If you use SAML based authentication, users cannot search for records in Data Director and
access the Hub Console.
Workaround: To use SAML based authentication, create the users in the MDM Hub as
externally authenticated users.

Data Director Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-24518 When you unmerge a record that has a large number of cross-reference records associated with
it, the unmerge process fails.

MDM-24431 When you merge records, Data Director overrides the incorrect value with the value that you
enter in the Merge Preview column even when state management is not enabled for the base
object associated with the business entity.
Workaround: If you want to override values, ensure that state management is enabled for the
base object with which the business entity is associated.

MDM-24385 When the Elasticsearch search engine is used, if the search string contains accented characters,
records are not found.
Workaround: Avoid using accented characters in the search string.

MDM-24156 If you use SAML based authentication, users cannot search for records in Data Director and
access the Hub Console.
Workaround: To use SAML based authentication, create the users in the MDM Hub as externally
authenticated users.

38 2020-11-10
 Reference Description
Number

MDM-24316 When you upgrade from version 10.2 or earlier, non-administrative users cannot log in to an
application. The issue occurs when the application that is created in the Provisioning tool has
the same name as the Data Director application that was upgraded.

MDM-23745 When you sort on a column that contains a lookup list with more than 40 values, the sort fails.

10.3
Fixed Limitations
MDM Hub Fixed Limitations (10.3)
The following table describes fixed limitations:

Reference Description
Number

MDM-21652 Fixed a security issue.

MDM-21398 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.

MDM-21394 After all the jobs in a batch group complete, the batch group status remains as processing.
MDM-17424

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

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

MDM-20068 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.

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

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

MDM-19684 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.

MDM-19681 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.

2020-11-10 39
 Reference Description
Number

MDM-19658 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.

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

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

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

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

MDM-19644 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.

MDM-19174 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.

MDM-19051 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

MDM-18948 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.

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

MDM-18372 In the Hub Console login page, when an incorrect user name or password is entered, the
MDM-18435 following unclear error message appears:
SIP-09070: SIP-18017: Error occurred during user authentication, error
was {0}
java.lang.NullPointerException

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

MDM-18327 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.

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

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

40 2020-11-10
 Reference Description
Number

MDM-16433 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.

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

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

Data Director Fixed Limitations (10.3)

The following table describes fixed limitations:

Reference Description
Number

MDM-21160 After you open a task, you cannot see updated data.

MDM-20965 When a package contains a join to a second package, a query on the first package fails.

MDM-20888 Fixed a security issue.

MDM-20752 You cannot change the default calendar format used in the History view.

MDM-20664 Task actions are disabled for users with uppercase user names.

MDM-20162 A business entity is not generated successfully from a subject area group.

MDM-19984 In the Query panel, the first tab appears in English instead of the selected UI language.

MDM-19851 When you add a hyperlink that contains the @ character, Data Director parses the text incorrectly
and saves an incorrect hyperlink.

MDM-19849 In the Data view, when you use the Find Duplicates option, the performance is slower than
expected.

MDM-19845 A search package returns incorrect child records for a selected effective period.
The issue occurs under the following circumstances:
- The search package that is configured for a subject area is a display package that joins parent
and child base objects.
- The parent and child base objects that the search package joins have timeline enabled.

MDM-19816 When you sort the search results and then export the sorted records, the exported CSV file
contains duplicate records.
If there is more than one table included in the search, you must include the local table name as a
prefix to your sort column and specify the sort order (DESC|ASC). For example, where the local
table name is BO and you want to sort by the column LNAME in descending order, use the
following format:
<urn:sortCriteria>BO.LNAME DESC</urn:sortCriteria>

MDM-19657 If you configure an additional workspace tab, the title of the tab might not display correctly.

2020-11-10 41
 Reference Description
Number

MDM-19785 In environments with single sign-on authentication, users with a backslash (\) character in the
user name cannot log in to Data Director.

MDM-19656 When case insensitive query search is enabled, the performance of the search query is poor.

MDM-19655 When you open the Provisioning tool in Microsoft Internet Explorer, you cannot publish your
changes.

MDM-19647 If you log in through single sign-on (SSO), you cannot access the Task Manager.

MDM-19641 The History view displays incorrect data for a timeline-enabled base object record.

MDM-19640 When a subject area has multiple grandchild subject areas with the same name, the business
entity schema that you generate fails with the SIP-MV-17006 and SIP-MV-17005 metadata
validation errors.

MDM-19642 The merge preview creates too many cleanse requests for inline cleanse functions, which causes
performance issues.

MDM-19636 The Hub Server properties http-only and cookie-secure do not work.

MDM-19368 When you log in, the dashboard displays a long title of all the subject areas that have tasks for
the current user.
Fix: To display a preferred default title, set the cmx.server.override_orstitle property to a
preferred title in the cmxserver.properties file.

MDM-19176 A record with associated lookup fields does not open in the Cross-reference Records view.

MDM-19086 A business entity-to-business entity view transformation fails in a scenario with the following
business entity view configurations:
- The business entity view child node has a one-to-many relationship with the parent node.
- The parent node is not a business entity view root node and has a one-to-one relationship with
its parent.

MDM-19049 If you create a searchable lookup without a rowid_object column to define the relationship, the
business entity schema does not generate the corresponding column for the Data Director
application.

MDM-19021 When ActiveVOS is the workflow engine, if you try to filter many tasks that have the same due
date, the filter fails.

MDM-18947 On the Export dialog box, the subject area name is not localized.

MDM-18822 When you open a data import result file in Microsoft Excel, multibyte characters are garbled.

MDM-18816 When you sort on a column that contains a lookup list with more than 40 values, the sort fails.

MDM-18794 When a REST API request for a record includes effective dates, a null pointer exception error
might occur.

MDM-18679 When you run the Merge task, the performance of the merge task is slower than expected.

MDM-18635 In Data Director applications with business entities, the Close icon is not visible in the user
interface tabs.

42 2020-11-10
 Reference Description
Number

MDM-18564 Lookup fields do not appear in the Matching Records view, and lookup fields list incorrect values
in the History view and the Cross-reference Records view.

MDM-18522 If a subject area child has a one-to-one relationship with grandchild records, you cannot export
all search results.

MDM-18497 If you make a Get API call to retrieve data in child records for effective dates that do not contain
data, the request returns an error.

MDM-18434 When a lookup column with an alias is included in an advanced search query, the search result
does not contain the value of the lookup field.

MDM-18415 If you do not have update privileges on a foreign key column in a parent base object, a Put
request fails to update a column in a child base object.

MDM-18408 The Find Duplicates process returns some incorrect matches at the child record level.

MDM-18406 In the Data view, when you run a search query with a search condition that exceeds the length of
the specified column, the query fails with the following error:
SIP-14150: Data access failure in searchQuery.

MDM-18263 In the Hierarchy view, when a user without administrative privileges clicks More Details for a
record, all the data that an administrative user can review might not appear. This issue occurs
when sub-packages are used in the query package.

MDM-18212 If you try to approve a task with a child or grandchild that is not part of the subject area that the
task is based on, the approval process fails with optimistic lock failure.

MDM-18211 When the page size for user preference is set to 0, search results do not appear.

MDM-18197 You cannot resize the Search page.

MDM-18175 A custom screen does not show up in Data Director.

MDM-18069 When the French locale is set up for the MDM Hub machines, JVMs, and the database, some
number formats are not saved correctly. The following error might occur:
java.lang.NumberFormatException

MDM-18067 When you update a record in the History view, long display names do not display correctly.

MDM-17965 When you update a record and then cancel the change, a null pointer exception might occur.

MDM-17783 When you create an unmerge task in Informatica Data Director, the unmerge operation fails with
the following error:
com.informatica.mdm.api.unmerge.Unmerge: SIP-10228: No record found for
the specified RecordKey

MDM-17763 The Similar Records component is empty even though similar records exist.

MDM-17756 When you use ActiveVOS for workflow management, all task operations run slower than
expected.

2020-11-10 43
 Reference Description
Number

MDM-17675 In the Matching Records view, the page navigation component is missing.

MDM-17203 When you perform a task action, such as Approve or Reject, you are required to add a comment.

MDM-17128 If you change the language using the Change Language option, the Log Out option does not
appear in the selected language.

MDM-17038 Options in the New window do not display alphabetically.

MDM-17037 If there are many business entity types in the list for the Search box, some business entity types
might not appear.

MDM-16931 In Internet Explorer, when you view records in the Business Entity view, the Edit and Delete icons
do not appear for business entity reference fields.

MDM-16440 When you open the Task Details dialog box, add comments, and then reassign the task, your
comments are not saved.

MDM-16146 When you perform a search, an error message appears over the search results. This issue occurs
when a Data Director application uses LDAP to authenticate users.

MDM-13701 In the task inbox, the check boxes that appear beside tasks suggest that you can perform bulk
task actions.

Provisioning Tool Fixed Limitations (10.3)

The following table describes fixed limitations:

Reference Description
Number

MDM-21116 When you convert subject areas to business entities, the generator cannot handle keywords as
field names.

MDM-20895 When you configure a business entity with an external call, users cannot successfully create a
record based on that business entity in Data Director.

MDM-19679 When you generate business entities from a subject area configuration, an error might occur in
the following scenario:
- Many-to-many relationships exist between business entities.
- A relationship has a "From" node that is not a root node.

MDM-14443 An XML-to-Business-Entity transformation cannot map data from multiple XML nodes to a
single object.

44 2020-11-10
SIF API Fixed Limitations (10.3)
The following table describes fixed limitations:

Reference Description
Number

MDM-20884 Fixed a security issue.

MDM-19678 A Promote API call updates all fields in a record instead of updating only the fields in a pending
cross-reference record specified in the SIF request.
To specify that the MDM Hub only applies BVT calculation to fields that are part of the SIF
request, set the cmx.server.selective.bvt.enabled property to true in the
cmxserver.properties file.

MDM-19677 An ExecuteBatchAutoMatchandMerge API call does not return an error message even though
errors are logged in the Hub Server log.

MDM-19653 In a JBoss environment, when you use the Services Integration Framework (SIF) to run the MDM
Hub operations, an out of memory error might occur.

MDM-19639 A CleansePut API call does not update a child foreign key with the correct cross-reference
record.

MDM-19635 A SIF API call that runs a multimerge batch job fails with the following error: SIP-23038:
Internal error. The SQL statement generated the SQL error ORA-12899:
value too large for column

MDM-18539 If you make an API call for versioning-enabled base objects that use XREF and base object
tables, the request fails and generates an error.

MDM-18238 A Cleanse function call fails with an error.

MDM-18165 In a PromotePendingXrefs API call, when the ROWID_XREF value is used as the record identifier,
the child subject area records are not promoted.

MDM-18154 When you use the CleansePut API call to add records, you cannot find the records using search.

Closed Enhancement Requests

MDM Hub Closed Enhancement Requests (10.3)
The following table describes closed enhancement requests:

Reference Number Description

MDM-17859 Added support for the Oracle WebLogic T3S protocol. For information about setting up the
protocol, see the Multidomain MDM Security Guide.

MDM-16652 You can view match scores in the External Match Output table.

2020-11-10 45
Data Director Closed Enhancement Requests (10.3)
The following table describes closed enhancement requests:

Reference Description
Number

MDM-19515 In the views for subject areas, values are displayed in a fixed-width font and white space is
preserved.

MDM-18280 To help you prioritize tasks, the task inbox in the Home page contains the following columns:
- Create date. Displays the date on which a task was created.
- Owner. Displays the current owner of a task.

MDM-16819 In the Provisioning tool, you can make comments and attachments mandatory for a Data
Director application.

Known Limitations
MDM Hub Known Limitations
The following table describes known limitations:

Reference Number Description

MDM-22756 If you run the Support Tool with the HTTPS protocol,
when you navigate from the Match Analysis Tool to the
CSM tab, an error occurs.

MDM-22777 After you customize search results to display lookup

columns, and you run a search with no values on a
package that contains the lookup columns, the lookup
columns do not appear in the search results.

MDM-22691 After you run a match job that matches a parent record
with a child record, the merge task in the ActiveVOS
Console references the child record instead of the
parent record.

MDM-22528 After you remove a parameter from a cleanse

transformation mapping and apply the change, you
cannot add a parameter to the mapping.

MDM-22143 When you integrate Multidomain MDM 10.3 for IBM DB2
with Dynamic Data Masking 9.8.4, and then create a
security rule set for DB2, the affected master data is not
masked.

MDM-21986 Forward matching records are created during the

Automerge process, which can cause the process to run
slowly.

MDM-21984 When you use the MdmKeyStore class, a file descriptor

leak causes FileNotFoundException errors.

46 2020-11-10
 Reference Number Description

MDM-21376 In an Oracle RAC database environment with the Zero

Downtime feature, the extract process generates an
Oracle Golden Gate error.

MDM-22070 The cmx.server.properties file does not contain

the properties that were introduced in this release.
Workaround: Add the properties to the file after you
upgrade.

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

MDM-19586 When pattern validation rules with WHERE clauses are

applied, trust is downgraded for all records instead of
only the records that match the patterns in the WHERE
clause.

MDM-15369 When Chinese characters are loaded into a staging

table, some Chinese characters get corrupted.

MDM-14943 In WebSphere environments, when you log in to the Hub

Console, the following misleading error might appear:
SIP-11101: The Cleanse Match Server license
is either not valid or expired.
Workaround: Before you log in to the Hub Console,
ensure that the -
Dcom.ibm.crypto.provider.DoRSATypeChecking
Java option is set to false. The Java option specifies
whether data encryption is allowed and is required for
password hashing to work.

MDM-13617 In WebSphere version 8.5.5.9 environments, a stack

trace error appears in the cleanse log. The stack trace
error begins with the following text:
v01/installedApps/INCMDMHUBQANode01Cell/
siperian-mrm-cleanse.ear.ear/siperian-mrm-
cleanse.war/WEB-INF/lib/
com.informatica.mdm-siperian-
cleanse-10.2.0-SNAPSHOT.jar!/resources/
infinispanConfig.xml
You can safely ignore the error.

MDM-13372 In Microsoft SQL Server and JBoss environments, when

you restart the application server after deployment of
the MDM Hub, an error occurs. You can safely ignore the
error.

MDM-12164 When you delete cross-reference records associated

with base object records that were updated, the delete
operation might fail. This is caused by the
PUT_UPDATE_MERGE_IND crossreference table column.

2020-11-10 47
 Reference Number Description

MDM-12129 Even though the required message trigger are enabled,

the Restore API does not trigger MQ messages.

MDM-11898 When you run the Extract BVT Version batch job for
multiple base objects, the last extract date is not set.

MDM-10792 When the database contains partitioned tables, the

metadata validation process generates the following
warning:
SIP-PV-10233(31) - The tablespace of a
table in the database differs from the
tablespace specified in the metadata.
You can safely ignore the warning.

MDM-10476 When you unmerge a record with a large number of

cross-reference records, the Process Server generates
an out of memory error.

MDM-10201 To promote a change list to a schema that has

hierarchies enabled, you must have MDM Hub
administrator privileges.

MDM-9902 When 'Enable History of Cross-Reference Promotion' is

enabled for a base object, the history of cross-reference
record promotion is not maintained.

MDM-9816 When you refresh an Informatica Data Quality cleanse

function which has two mapplets with different ports
using WebSphere, the following error appears:
SIP-11134: Compile failed for compile
command

MDM-9604 When you promote an empty change list to an

Operational Reference Store with a business entity
configuration, the promote fails with the following error:
Object cannot be deleted because 'CO CS
Configs\TaskConfiguration\Task Types
\AVOSBeNotification\Task Roles\DataSteward'
is depending on it.
(deleteRole[id:ROLE.DataSteward])
Workaround: Remove the DataSteward role from the
target Operational Reference Store, and then promote
the change list.

MDM-9220 You cannot import or promote a changelist from MDM

Multidomain Edition version 9.6.1.

MDM-8738 The MDM Hub log file, cmxserver.log, increases

beyond the maximum specified file size.

MDM-8588 The first time that you import a schema in the Hub
Console, the following error might appear:
missing initial moveto in path definition
You can safely ignore the error message.

48 2020-11-10
 Reference Number Description

MDM-8060 When you import or promote a changelist from MDM

Multidomain Edition version 9.7.1, an proxy role error is
generated. The changelist is not imported or promoted.

MDM-7786 After adding a new role to a user, the Operational

Reference Store is marked as invalid.

MDM-7592 A source system that is not mapped to a column in the

base object can override a valid value in the column with
a null value. For example, SourceA and SourceB
contribute to BaseObjectC. SourceA is mapped to
ColumnX with minimum and maximum trust settings of
zero. SourceB is not mapped to ColumnX and has no
trust setting for it, but it is mapped to other columns in
BaseObjectC. When SourceB updates BaseObjectC,
ColumnX is incorrectly updated with a null value.
Workaround: Change the minimum trust setting for
SourceA to at least 2.

MDM-5830 After installation of the MDM Hub, the WebSphere

application server username and password are visible in
the installation logs.

MDM-1578 When you delete an active cross-reference record in the

Data Manager tool in the Hub Console, the record is
deleted but an error occurs. You can safely ignore the
error.

Data Director Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-22587 When you export search results that are based on a timeline, the export process ignores the
timeline and exports all data.

MDM-21988 When a user claims a task, the task inbox does not display a message to confirm that the
task is not yet claimed.

MDM-18157 On Chrome, when you display the interface in Chinese, some button labels are truncated.

2020-11-10 49
Data Director with Business Entities
The entity views are based on business entities. To use these views, upgrade Data Director applications
from subject areas to business entities.

Reference Description
Number

MDM-22817 When you filter child records by a date that does not exist in the child records, a record with a
non-matching date appears.

MDM-22815 You can change the default date format used by the calendar in the Entity 360 framework.
To change the default date format, use a text editor to create a bundleE360.properties file
that contains the property DATE_TIME_LONG_FORMAT. Then add the bundleE360.properties
file to the following location:
infamdm\hub\server\resources\entityE360
Note: If the entityE360 directory does not exist, create the directory.

MDM-22811 In the simple merge component, when you want to change a date value, the calendar does not
appear correctly.
Workaround: Type in a date.

MDM-22519 In the search results, some rows are empty. The rows represent records that are filtered out
because the user does not have permission to view the records.
Workaround: The MDM administrator has to delete the search index. From the Provisioning tool,
open the business entity and add or update any searchable field. Any change to the searchable
configuration deletes the index. Re-index the data for the business entity.

MDM-22369 When you preview a changed record from a task, the preview might not display the change bar
beside some of the changed values in child records.

MDM-21692 The calendar controls are not localized.

MDM-18665 When you delete the Status Cd code, the following error occurs:
Cannot read property 'taskId' of undefined
Workaround: You can edit this field, but you cannot delete it.

MDM-14958 In the Search box drop-down list, when the list exceeds the height of the browser window, you
cannot scroll the list to see the items that are off screen.
Workaround: In the browser, switch to full screen mode. Increase the resolution until you can see
the remainder of the list.

MDM-14952 In the History view, the timescale labels in the Options menu do not appear correctly initially.
Workaround: Interact with the timescale for the timescale labels to display correctly.

MDM-14933 In the Hierarchy view, business entities in the Relationships tab of the history do not open in
Business Entity view.
Workaround: Use the Search box to find the business entity, and then open the entity in a
Business Entity view.

MDM-14932 In the Timeline view, you cannot open the relationship records that appear on the Relationships
tab.

50 2020-11-10
 Reference Description
Number

MDM-14920 In the Hierarchy view, in the Entity Details dialog box, when you click More Details, the dialog box
closes without opening the selected business entity.
Workaround: Use the Search box to find the business entity, and then open the entity in a
Business Entity view.

MDM-14919 In the Hierarchy view, the anchor entity Actions > Open in New Tab option does not open a new
tab.

MDM-14918 In the Hierarchy view, the anchor entity Actions > Edit > Edit Entity option does not open the
business entity.
Workaround: From the View list, select the Business Entity view.

MDM-14890 In Microsoft Internet Explorer 10, the Log Out button is not visible from the Business Entity view
and details do not display correctly in the History view.
Workaround: Use another supported browser.

MDM-14781 In the Matching Records view, when you select a child record as the target record, the interface
lets you select a record in the pending state. However, pending records cannot participate in a
merge process, which means that the merge fails.
Workaround: Select a child record in the active state as the target record.

MDM-14460 If the time zone of the application server is different from the time zone of the client, the time of
an event in the History view differs from the time in the event details panel.

MDM-14385 When you view the details of merge and unmerge operations, user names are sometimes prefixed
with e360 in the Updated By or Created By fields.

MDM-14327 If there are multiple pages of search results for business entity child records and you type in a
page number beyond the range of pages displayed, subsequent attempts to view a page of
search results fail and an error occurs.

MDM-11397 If you use the mdm_sample Operational Reference Store, you cannot add or update the phone
number of a Person business entity.
Workaround: Before you add or update the phone number of a Person business entity, perform
the following steps:
1. In the Hub Console, start the Cleanse Functions tool, and then acquire a write lock.
2. Click Custom > Parse Phone Number - NA.
3. Click the Details tab of the Parse Phone Number - NA function.
4. Right-click on Condition and click Edit Condition.
5. In the Edit Condition dialog box, for each case value, change the country code from +1 to 1.
6. Save the changes and use the Repository Manager to validate the metadata.

MDM-8768 After you upgrade and then delete all the configuration files from the repository table
c_repos_component_instance, tasks might not display in the Task Manager inbox for the first
user who logs in to Informatica Data Director.
Workaround: Log out of Informatica Data Director and then log in again.

2020-11-10 51
 Reference Description
Number

MDM-8764 When you generate the business entity schema from a subject area configuration, mandatory
lookup fields are not included in the business entity view configuration or transformation
configuration.
Workaround: In the Provisioning tool, add the missing configuration code:
1. Select Advance Configuration > Business Entity Views (XML).
2. Add the following code to the lookup configuration:
<ns2:field name="<missing field name>"/>
3. Select Advance Configuration > Transformation Configuration (XML).
4. Add the following code to the co2view configuration:
<input name=”<missing field name>” field=”<missing field name>”/>
<output name=”<missing field name>” field=”<missing field name>”/>
5. Add the following code to the view2co configuration:
<input name=”<missing field name>” field=”<missing field name>”/>
<output name=”<missing field name>” field=”<missing field name>”/>
6. Select Advance Configuration > Business Entities (XML).
7. Add the following code to the lookup configuration:
<ns2:field name="<missing field name>" label="<missing field name>"
column="<missingcolumn name>" required="true"/>
8. Click Update.
9. Click Validate + Publish.

MDM-8606 In the Matching Records view, when you merge records, the system can appear unresponsive.
Workaround: Wait until the merge job finishes.

MDM-7597 If you delete a record and then search for the record, the ROWID of the deleted record still
displays.

MDM-5715 On Internet Explorer 9 and 10, if you group search results by type, you cannot then expand the
search results.
Workaround: Use Internet Explorer 11 or alternative browsers such as Chrome, Safari, or Firefox.

MDM-5333 Match and merge is not supported for business entity child records. If you try to add match
records to a child record, you might corrupt the data.

MDM-2699 In calendars, you cannot set a date before January 1, 1000.

MDM-2584 In the Task Manager, you are unable to sort tasks by Task ID, Task Type or Task Status.

MDM-2574 In the task inbox, setting the Owner filter to Unclaimed does not return the list of unclaimed
tasks.

52 2020-11-10
Data Director with Subject Areas
The legacy views are based on subject areas.

Reference Description
Number

MDM-16464 When you run a search query with a specified effective date, the search results display incorrect
values for records from a child subject area.

MDM-14872 In the Matches view, users can add a record as a merge candidate that has already been
selected to merge with another record. When the record is added as a merge candidate, an error
occurs.

MDM-13787 In the XREF view, you can select a cross-reference record to unmerge when an unmerge task
already exists for that record. An error occurs when the duplicate unmerge task is processed.

MDM-10613 In the Hierarchy view, when you end date a relationship and the relationship record is from a
different source system than the IDD SMOS system, the existing relationship record is deleted.

MDM-9796 In the Hierarchy view, when you disable an entity type in the Filters tab, you cannot create
relationships with those entities.
Workaround: Before you create relationships, open the Filters tab, and select the entity types
that you want to use in the relationship.

Provisioning Tool Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-22531 When you configure a read-only field with more than one default value, the Provisioning tool
displays a validation error.
Workaround: Use a cleanse job to set the default value for a read-only field.

MDM-22457 If you publish a layout with a duplicate name, the publish process fails with an error.

MDM-22444 If you mark a field as read-only in a business entity, a cleanse transformation on that field fails.
Workaround: Mark the field as read-only in a business entity view.

MDM-21991 When you include the legacy Merge Preview in a record view, the Provisioning tool displays an
error.

MDM-20600 When you remove a base object from the Hub Console, the Provisioning tool continues to show
the base object and does not generate validation errors.
Workaround: If you delete a base object, update the related business entity in the Provisioning
tool.

MDM-14749 When you delete a base object in the Hub Console, the dependencies are not removed from the
business entity configurations in the Provisioning tool.
Workaround: In the Provisioning tool, delete the dependencies on the base object.

2020-11-10 53
 Reference Description
Number

MDM-14255 When you configure an XML to Business Entity transformation, the parent node fields are not
available for mapping in the cleanse transformation of a child node element.
Workaround: Manually enter the path to the parent element that you want to map. Use the
Service Data Object (SDO) XPath expression, where / represents a root XML element. For
example, in the transformation for the address child node, to access the dunsNumber parent
element, use the path /OrderCompanyProfileResult[1]/ServiceResult[1]/
OrderProductResponseDetail[1]/InquiryDetail[1]/DUNSNumber[1]

MDM-14528 If you create a transformation with the same name as another transformation, a validation error
message does not appear. An error appears only when you try to publish the changes.

MDM-14521 When you use the Provisioning tool in the Chrome web browser, Chrome might become
unresponsive.

MDM-14449 If you make a field searchable in a reference entity that is referenced in two or more business
entities, then the field is searchable for all the business entities.
Furthermore, if you make a field searchable in a reference entity that is not referenced in any
business entity, then the field is not searchable.
Workaround: Make a field searchable in a reference entity that is referenced in only one
business entity.

MDM-13754 If a write lock is acquired in the Hub Console, the Provisioning tool does not work as expected.

MDM-8844 When you publish configuration changes through the Provisioning tool, you can overwrite these
changes if you generate a business entity schema through the IDD Configuration Manager.

MDM-8668 From the Modeling page, you can access and edit system columns.
Workaround: Avoiding editing system columns.

MDM-7219 The Provisioning tool fails to launch when the last slash is omitted.
Workaround: Add a slash character to the end of the URL: http:/host:port/provisioning/

Business Entity Services Known Limitations

The following table describes known limitations:
Note: In previous releases, business entity services were called composite services.

Reference Number Description

MDM-14375 When you specify more than one recordState for the GetRelated SOAP API, an error occurs.

MDM-10553 When you run a read composite service for a deleted grandchild record, the composite
service call does not return data.

54 2020-11-10
Search with Solr Known Limitations
Search refers to a full-text search on fields that are configured as searchable. Search with Solr was
formerly referred to as Smart Search.
The following table describes known limitations:

Reference Description
Number

MDM-22690 After searching for a record, the actions in the search results include actions that are not
applicable to a Data Director application with business entities.

MDM-20998 After running a delete process with SIF APIs or business entity services, the search index is not
deleted.

MDM-14953 The Initially Index Smart Search Data job might fail with the following error:
SIP-52050: Failed to retrieve the ZooKeeper client instance because the
connection to the ZooKeeper client instance timed out.
No collection linked.
Workaround: Re-run the job after 10 minutes. If you get the same error again, restart the
application server and re-run the job.

MDM-14945 After you delete a pending record, you get the following error in the cmxserver.log file:
[ERROR] com.informatica.mdm.sss.SmartSearchMDB: SIP-11041: Communication
error "invalid stream header: 3C3F786D" occurs when making a request to
Process Server

MDM-14944 The Initially Index Smart Search Data job fails if a business entity name contains an underscore.
Workaround: Avoid underscores in business entity names.

MDM-11238 When you use a search string within double quotes (") to perform an exact search, the search
might not return the expected results.
Workaround: Prefix each double quote with a backslash (\) and search again. For example,
\"Robin Williams\"

MDM-10723 After you set a field as a searchable field, a search request might fail.
Workaround: Perform one of the following tasks:
- Reload the collection with the following URL: http://<Host Name>:<Port>/MDESolr/
admin/collections?action=RELOAD&name=<Collection Name>
Host Name indicates the host name of the Process Server that you use as a ZooKeeper server,
and Port indicates the port number on which the Process Server listens. Collection Name
is the name of the collection or business entity to which you added the field.
You can get the collection name from the following directory: <MDM Hub Installation
Directory>\hub\cleanse\solr.
For example, 4d5354312e375056.Person is the collection name for the Person business
entity.
- Stop the application server, delete the ZooKeeper data directory, and then restart the
application server.

2020-11-10 55
 Reference Description
Number

MDM-10389 A search request might return one of the following errors:

MDM-11925 - [SearchService_30027]Exception occured while getting query the
constructor
MDM-12691 - An internal error occurred. Contact an administrator to get more
information for the client tool logs. If the administrator cannot
determine the cause of the error, contact Informatica Global Customer
Support.
Workaround: Restart the application server, and try again. If you get the same error, perform the
following tasks:
1. Stop the application server.
2. Delete the ZooKeeper data directory.
3. If you enabled search on multiple process servers, delete the following directory:
<MDM Hub Installation Directory>\hub\cleanse\solr
4. Restart the application server.
5. If you delete the solr directory, run the Initially Index Smart Search Data job.
6. Perform the search again.

MDM-9805 The WADL files for the REST services are out of date.
Workaround: For information about the REST services, see the Multidomain MDM Business Entity
Services Guide.

MDM-8488 When you search for a negative number or use a negative number to filter the search results, you
get the following error:
[SIP-11008] SIP-11008: [SearchServiceClient_00028] You cannot use the
following operators in the search string: AND, NOT, -, and OR. Add +
before each search word if the search results must contain the word. Do
not add + if the search word is optional or single word.

MDM-8598 After you restart the application server, the Initially Index Smart Search Data job or a search
request might return the following error in the application server log file:
No live SolrServers available to handle this request
Workaround: Restart the application server.

MDM-8161 If you configure the search to display many results, some browsers do not display all the records
or become unresponsive.

MDM-5785 A search request does not facet the dates that are earlier than 1970.

MDM-4753 The search UI displays two filters with the same name without identifying the objects that the
filters act upon. Filter fields do not have to be unique. A root object and a child object can both
have a field with the same name, such as Name, and both fields can be configured as a filter.
Workaround: Ensure that column names are unique for the root object and its children.

MDM-3289 If the composite objects do not include a field named displayName, the Name column in the
HORA-52192 Search workspace displays random field values when you perform a search.
Workaround: To set a field for the Name column, use a database tool to open the
C_REPOS_CO_CS_CONFIG table and set the displayName property of the composite objects to
an appropriate field in the BLOB data of the SEARCHABLE_CO configuration type.

56 2020-11-10
 Reference Description
Number

MDM-3235 The Initially Index Smart Search Data job might return incorrect metrics if you run the job more
than once.

MDM-2644 After you enable search on the Process Server, the application server log file does not include
any relevant error message if the collection creation fails due to insufficient memory.

MDM-1799 When you search for a negative value, the search request returns the positive and negative
matching values.

Business Process Management Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-22814 Siperian workflow engine. When you try to reassign a claimed task, the Assignees list is empty in
the Edit task dialog box.

MDM-14205 If you use the sample Operational Reference Store, an error occurs when you open the Workflow
Manager in the Hub Console. In the sample Operational Reference Store, the value of
WORKFLOW_ENGINE_NAME in MDM_SAMPLE.C_REPOS_DB_RELEASE does not match the value of
NAME in CMX_SYSTEM.C_REPOS_WORKFLOW_ENGINE.
Perform one of the following workarounds:
- Add the business entity-based workflow engine ActiveVOSBE to the configuration if it does not
exist, or;
- Update the configuration in the Sample Operational Reference Store to the name of the existing
business entity workflow engine. In the column CMX_SYSTEM.C_REPOS_WORKFLOW_ENGINE,
change the value to ActiveVOSBE.

MDM-13359 If you use ActiveVOS, a user cannot belong to a role that creates an unmerge task and also belong
to a role to approves that task type. If a user belongs to both roles, an error occurs when the user
tries to approve the unmerge task.

MDM-12011 When you install the MDM Hub with ActiveVOS, the following exception appears in the
postInstallSetup.log file:
java.util.concurrent.RejectedExecutionException
You can safely ignore this exception.

MDM-9079 In the ActiveVOS Console, on the MDM Identity Provider page, you must enter the password of the
MDM Hub user named admin in the MDM Connection Settings Password field. You cannot use the
password for any other user, even if the user has administrative privileges.

MDM-9041 When multiple workflow triggers apply to an action, the first applicable trigger is applied, even if
subsequent triggers are specific to the business entity.
Workaround: In the task configuration file, place the triggers that are specific to a business entity
at the beginning of the file. Place the more general triggers at the end of the file.

2020-11-10 57
 Reference Description
Number

MDM-8763 When you install the MDM Hub with embedded ActiveVOS in a Linux environment, the following
error appears in the postInstallSetup.log:
[exec] Unable to locate tools.jar. Expected to find it in /data/tmp/
install.dir.12594/Linux/resource/lib/tools.jar
You can safely ignore the error.

MDM-8622 When you import ActiveVOS tasks from version 9.7.1 and run a batch file to add presentation
parameters to the tasks, an error occurs.
You can safely ignore the error.

MDM-8086 The task priority set by the MDM Hub cannot be used to trigger an ActiveVOS escalation.

MDM-6473 The Hub Server silent installation process sets the incorrect ActiveVOS database URL when the
silent installer property AVOS.ORACLE.CONNECTION.TYPE is set to SID.
Workaround: Before you perform the Hub Server silent installation, set the silent installer property
AVOS.ORACLE.CONNECTION.TYPE to Service Name .

MDM-5290 When you change the BPM adapter, the number of merge tasks is counted incorrectly and the
number might exceed the threshold value for merge tasks.
Workaround: Set the value of the ROWID_TASK column in the _MTCH table to NULL.

Resource Kit Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-14102 When you deploy the web sample LookupWebServiceExample, the MDM Hub generates an
error in the application server log file. You can safely ignore the error.

58 2020-11-10
Sample Operational Reference Store Known Limitations
The following table describes known limitations:

Reference Description
Number

MDM-14684 After you upgrade, when you validate the IDD configuration, an error occurs stating that the
SrManager role does not exist in the task configuration file.
Workaround: Add the SrManager role.
1. In the Hub Console, add the SrManager role with the required privileges.
2. Use the Repository Manager in the Hub Console to validate the metadata.
3. Truncate the repository table C_REPOS_CO_CS_CONFIG.
4. In the IDD Configuration Manager, generate the business entity schema for the IDD
application.

MDM-14434 The Entity view does not display the full list of lookup column values.
Workaround: Use the Databases tool in the Hub Console to set the GETLIST limit to 300 for the
lookup base object.

Services Integration Framework Known Limitations

The following table describes known limitations:

Reference Description
Number

MDM-19151 The DeleteMatches service does not correctly process data blocked by InteractionID.

MDM-8880 SIF calls update the LAST_UPDATE_DATE column and the UPDATED_BY column with incorrect
data.

MDM-593 In Microsoft SQL Server environments on the Windows operating system: When SearchMatch
is run using multiple threads, the following error occurs:
SIP-10226=Error in building query to run MATCH verb.
Workaround:
Add the following entries to the registry subkey HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Services\Tcpip\Parameters:
Value Name: MaxUserPort
Value Type: DWORD
Value data: 65534

Informatica Platform Known Limitations

The following table describes known limitations:

Reference Number Description

MDM-18229 In a Linux environment, the option to install the Informatica platform is not available.

2020-11-10 59
Informatica Data Controls Known Limitations
The following table describes known limitations:

Reference Description
Number

MDM-8950 In Microsoft Internet Explorer 11, the Proactive Match window stops responding when you
click Import.
Workaround: In the Java Server Page file, enable compatible mode for the host page.

60 2020-11-10