After installing SES, the search works fine, but I do have often in log files MDS related exceptions, like:
oracle.wsm.mds.MDSAccessException: WSM-04509 : cannot initialize the connection to the data store
Caused By: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Unknown host specified
Also the weblogic console shows critical error at JDBC: Connection Pool Name = null:null:mds-owsm, State = Unhealthy
Obviously the mds-owsm data source is incorrectly set after installation (URL=jdbc:oracle:thin:@dbhost.example.com:1521/orcl)
Is the mds-owsm data source necessary? (SES is working fine)
If not, how can I delete it? (there is no Fusion Middleware Control nor WLST)
If the mds-owsm is necessary, can I configure it to the same SES DB? (the EnterpriseSearchDS data source)
The problem appears right after SES installation and on all of our instances (testing, staging, production).
Edited by: user13277662 on 28.12.2011 3:44
This exception is non-fatal, but the errors tend to clobber the server logs. Please follow the workaround for bug 9268418 in the SES 11.2.2 release notes - http://docs.oracle.com/cd/E21698_01/relnotes.1122/e14092/toc.htm#autoId17
Thank you. I've followed the instructions in release notes for the bug 9268418.
It did not help. Most probably because the user 'dev_mds' does not exist in the database.
I tried to add manually the user 'dev_mds'. Than the status in the console became green.
But the exceptions are still in the log. Probably the reason is the metadata tables are missing in the DB.