Multi Datasource MDS not Displayed in Enterprise Manager Navigation Tree
(Doc ID 1540118.1)
Last updated on MARCH 18, 2019
Applies to:Oracle WebCenter Portal - Version 188.8.131.52.0 and later
Oracle Metadata Services - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Multi DS MDS Repositories are not shown under Metadata Repositories in EM.
As a result, it is not possible to deploy an application from EM into the Multi DS MDS Repositories.
The Multi DS data source is called mds-CustomPortalDS, to comply with the following documentation:
220.127.116.11 Configuring Multi Data Sources for MDS Repositories
Oracle Fusion Middleware High Availability Guide
11g Release 1 (11.1.1)
Part Number E10106-20
The multi data source's name must be pre-fixed with mds-. This ensures that the multi data source can be recognized as an MDS repository that can be used for MDS management functionality through Fusion Middleware Control, WLST, and JDeveloper.
When an MDS data source is added as a child of a multi data source, this data source is no longer exposed as an MDS repository. For example, it does not appear under the Metadata Repositories folder in the Fusion Middleware Control navigation tree, you cannot perform MDS repository operations on it, and it does not appear in the list of selectable repositories during deployment.
Steps to Reproduce
1. Create 2 Generic Data Sources to connect to the MDS schema on both RAC instances
2. Create a MultiDS data source with the name mds-CustomPortalDS and add the 2 generic data sources to it that were created in step 1
3. Activate the changes
4. Notice that the new data source does now show up under Metadata Repositories in EM.
As a result, when performing a deployment from EM, the right Multi DS data source cannot be specified as the MDS Repository.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document