Table of Contents

Search

  1. Abstract
  2. Apache Log4j RCE Vulnerability
  3. Installation and Upgrade
  4. 10.5 Fixed Limitations
  5. 10.5 Known Limitations
  6. Cumulative Known Limitations
  7. Emergency Bug Fixes Merged into Multidomain MDM 10.5

MDM Hub Known Limitations

MDM Hub Known Limitations

The following table describes the known limitations that were found in 10.5:
Reference Number
Description
MDM-43465
When you install the Hub Server and the Process Server from the command line, the password for the WebLogic Server administrative user is not masked in the command line.
MDM-42279
In WebLogic environments, when you run a report API, the report execution fails with the following error message:
{"status":"FAILED","jobId":"SVR1.7XHW ","errorCode":"SIP-10338","errorMessage":"SIP-10338: Internal server error: \{0} Contact Informatica Global Customer Support.
Workaround: Open the
cmxserver.properties
file to update the
activevos.jndi
property to the following value:
jdbc/ActiveVOS
MDM-41441
In JBoss EAP 7.4.x environments, you might experience log in issues with Data Director, Provisioning tool, and Hub Console.
Workaround: Apply EBF-24880 to resolve the issue.
MDM-36851
When you run a match job, you might get a runtime exception. Check the application server startup log to see the exception.
Workaround: Wait until the match job completes.
MDM-36438
During a fuzzy match, if the _STRP table is corrupted, the match job might fail.
Workaround: Open the
cmxcleanse.properties
file, add the
cmx.server.match.ignore_exceptions
property and set it to true. If the match job still fails, contact Informatica Global Customer support.

0 COMMENTS

We’d like to hear from you!