Hi Gregg,
thanks for your answers. I time allows for it, I will give it a go on my sandbox environment.I agree with you regarding the distributed.properties file. If it's good for one password, then it _should_ be ok for other passwords as well. Regarding context.xml, yes, your comment is really interesting! Simply trash the file and it should be ok. On the other hand, it is not _that_ surprising. We have Oracle Data Guard on the DB side. In the context.xml file, I have painstaikingly put together an elaborate Data Guard aware connectionURL, which is apparently not used. The DB usually runs on server A. Sometimes after patching the underlying servers (OS patch, or DB maintenance), they forget to switch the DB back to server A. From a DB perspective, the DB is fully available, running ok on server B. But CARA can't connect to it, so I assume it uses the parameter values fetched from webapps/datamanagement/WEB-INF/distributed.properties. More or less the same parameters, simply using another form. In this file, however, you have the parameter data.management.database.host, which is a hostname, not a Data Guard aware connection string. And you MUST provide this with a single hostname, I have tried quite a number of things that failed one after the other. At this place, there is a single point of failure, even if all other RA components are laid out in HA architecture. A while ago I have opened an idea for this but without much response so far. See Make DB configuration Oracle Dataguard aware .
anyway, always good to hear from you.
Cheers
Bernard