FMW Control Console 220.127.116.11 Does Not Display Metadata Repository Folder(MDS) After Configuring The Associated DataSource As MultiDS
Last updated on MARCH 09, 2017
Applies to:Oracle Metadata Services - Version 18.104.22.168.0 to 22.214.171.124.0 [Release Oracle11g]
Information in this document applies to any platform.
In Enterprise Manager Fusion Middleware Control(fmwc) 126.96.36.199, Metadata Repository folder is not displayed in Navigation Tree(left pane) after configuring the associated DataSource as MultiDS
Metadata repositories are associated with the DataSource Names.
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.
Any DataSource with names pre-fixed by "mds-" will be displayed in fmwc under the Metadata Repository folder.
If everything is working as expected, when a MDS data source is added as a child of a multi data source, this data source is no longer exposed as an MDS repository.
Using mds-owsm as example, if the child DataSources "mds-owsm-rac0 & mds-owsm-rac1" are added to mds-owsm, then only mds-owsm should be displayed.
In 188.8.131.52, if mds-owsm is a generic DataSource(DS), it is displayed in fmwc. But if mds-owsm is recreated as a MultiDataSource using same DS and JNDI names, it is no longer displayed in fmwc.
If mds-owsm is the only DS configured, then the MDS folder will not be displayed.
DataSource is recreated as a MultiDataSource using same DS and JNDI names.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms