Need for multiple database schemas

PMR TS000125312

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.