Central Management Service

The CMS store is used by the Central Management Service to maintain a current Lync Server 2010 Topology for the entire Lync deployment (Topology, Policies, Voice Routes, etc…). Here is what you need to know about the CMS:
The database used for this purpose is called “Xds”; it maintains the Lync configuration as published by the Topology Builder.
There is only one master copy of CMS database which is automatically installed on the first instance of a Standard or Enterprise Edition Lync pool.
Every subsequent Lync server in the topology gets a read-only copy of it. A topology change on the master is replicated to each read-only copy on each Lync server. This is a key element to Lync Server’s survivability feature set – if the network connection between a Lync Edge server goes down for example, the Edge server still knows about the topology and can keep functioning.

Changes are replicated to all Lync server roles except the Lync Edge using the Windows file copy SMB protocol. Changes are replicated to the Edge role via HTTPS. The Windows service “Lync server replica replicator agent” is responsible for receiving the snapshot and uploading the local copies of the databases. It then sends a status update to the Master Replicator (also a windows service) running on the CMS.

In CCM, on the Dependancy tab for CMS I have added :

OracleServiceBW
OracleMTSRecoveryService
OracleOraHome92TNSListener
OracleOraHome92Agent