DOM data storage

All DOM data are stored in an indexing database. Data for each object are stored in a separate index. Currently, the following indices are in use:

Object name	Index name
SectionDefinition	cdomsectiondefinition_{moduleId}
DomTemplate	cdomtemplate_{moduleId}
DomDefinition	cdomdefinition_{moduleId}
DomInstance	cdominstance_{moduleId}
DomBehaviorDefinition	cdombehaviordefinition_{moduleId}
HistoryChange	chistory_dominstance_{moduleId}

Caching

From DataMiner 10.3.9/10.4.0 onwards, a full cache of the DOM configuration objects (SectionDefinition, DomDefinition, and DomBehaviorDefinition) is present by default. This means that all of these objects are stored in memory to improve the performance of the DOM manager. These caches are kept in sync across the cluster using the DOM events.

Note

• Correct delivery of the DOM events is important to keep these caches in sync. If the DMS is unstable and Agents frequently lose connection to each other, we recommend disabling the caches. You can do so using the caching settings in the ModuleSettings.
• If a DOM configuration object event is lost, the cache may not reflect the correct state. This will be automatically fixed at midnight, as the "midnight sync" will ensure that the caches are correct by comparing them with the database. You can also trigger this sync manually in the SLNetClientTest tool. For more information, see Triggering a midnight sync for a DOM manager.