Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Apr 8, 2020

Partitioning by region via PME Data Source

MDM v10.1 describes the Data Source for the probabilistic matching tables via PME specific properties files. This has enabled to configure PME Data Source to be different then the Data Source for the rest of the MDM operational tables, in order to persist PME tables in the DB schema different from MDM operational schema, in order to partition search by region.

Configuring two different data sources to be used in the same two phase commit transaction will trigger distributed transaction management (XA) logic in WAS, to coordinate two phase commit across two data base resources (two schemas) and ensure ATOMisity of transaction. MDM always starts two phase commit transaction at the beginning of the service and therefore configuring PME data source differently from main MDM data source will add some XA transaction coordination overhead, however minor.

IBM confirmed that implementation with different PME datasources to partition search by region will continue to be supported in MDM 10.1.

In MDM v11 the data source for PME has been unified with the rest of MDM in version 11. This means that PME Data Source is coded to be the same as the rest of the MDM tables and it is not possible to change it via configuration point.

  • Admin
    Marcus Boone
    Apr 8, 2020

    We are reviewing the original support ticket to better understand the requirement and outcomes. its not obvious what Dell is trying to acheive. After review, we may be in touch for a call to clarify the requirement