This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Support Oracle Single Schema for multiple clusters data
In this link https://www.ibm.com/docs/en/spectrum-symphony/7.3.2?topic=database-setting-up-external-production You have this precondition in the 'Before you begin' section: "For data security, each cluster should have a different database schema to store its historical data when sharing the same database." However this would increase a lot of operation / and configuration complexity, especially in big firms that have a lot of user / schema rules. It also breaks backward compatibility, our existing setup procedure does not work well anymore. We would like IBM Symphony has the option of enable and support the single Oracle Schema (User) that can store data from multiple Symphony clusters.
To be more specific, in your current Oracle EGO and SOAM schemas, a few tables do not have CLUSTER_NAME in their primary Keys which can cause lose of data from some clusters. We could add the CLUSTER_NAME in the primary keys, however, IBM currently does not support client modification.
Do not place IBM confidential, company confidential, or personal information into any field.