Abstract
Installation and Upgrade
10.4 HotFix 2 Fixed Limitations
10.4 HotFix 2 Known Limitations
- MDM Data Director Known Limitations
- MDM Hub Known Limitations
10.4 HF2 Closed Enhancement Requests
- Data Director Closed Enhancement Requests
- MDM Hub Closed Enhancement Requests
10.4 HotFix 1 Fixed Limitations
10.4 HotFix 1 Known Limitations
10.4 Closed Enhancement Requests
- Data Director Closed Enhancement Requests
- Provisioning Tool Closed Enhancement Requests
10.4 Fixed Limitations
10.4 Known Limitations
- Data Director with Business Entities Known Limitations
- Provisioning Tool Known Limitations
Cumulative Known Limitations

Release Notes

10.4 HotFix 2

Back Next

MDM Hub Known Limitations

The following table describes the known limitations:

Reference Number	Description
MDM-25297	Informatica Multidomain MDM Installer creates two JMS queues, one for the internal SIF calls (SiperianQueue) and another for search requests. Both queues are a part of the Multidomain MDM installation. Intermittently, when you save a record in Data Director (IDD), the saving request goes to the search queue and an error appears. Workaround: Create a new destination of type Queue, under SiperianBus. For example, create SiperianQueue 1. Map it as a queue under xxx.sss.xxx queue. Restart the WebSphere application sever.

Reference Number

Description

MDM-25297

Informatica Multidomain MDM Installer creates two JMS queues, one for the internal SIF calls (SiperianQueue) and another for search requests. Both queues are a part of the Multidomain MDM installation. Intermittently, when you save a record in Data Director (IDD), the saving request goes to the search queue and an error appears.

Workaround: Create a new destination of type Queue, under SiperianBus. For example, create SiperianQueue 1. Map it as a queue under xxx.sss.xxx queue. Restart the WebSphere application sever.

Rename Saved Search

Table of Contents

Release Notes

Release Notes

MDM Hub Known Limitations

MDM Hub Known Limitations