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,
Post an idea
Upvote ideas that matter most to you
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.
Starting with MDM v11.0 the installation process does not support different database schema's anymore, which would isolate the MDM Configuration and Management Database tables from the MDM Server database tables. This was supported in MDM v10.1, see for example: https://www.ibm.com/support/knowledgecenter/SSWSR9_10.1.0/com.ibm.mdmhs.instl.gd.doc/concepts/c_manuallyinstallingtheconfigurationandmanagementdatabasefordb2.html
Background: The objective is to isolate the configuration tables from the operational tables of MDM in different schemas, to support running different versions of MDM, in order to achieve the lowest downtime when migrating and using a active/passive configuration. But the same schema is not supported for two instances with different versions. In MDM v10, this setup was possible using two different schemas for the configuration tables (for 2 versions) and one schema for the operational data. Now, with MDM v11 these different schemas are not supported during the installation process.This requires a (manual) post installation step now. But the customer is obliged to run an automatic deployment process in production, without post deployment steps.
This issue has been discussed in PMR/Case TS000125312 (which contains many other topics as well
Talking to other customers they have a similar issue with this and would like to have this option back, to ease the deployment of MDM , in multiple environments, with automatic deployment tools, without requiring post deployments scripts to correct settings afterwards.
Do not place IBM confidential, company confidential, or personal information into any field.