Loading...
Select Version
After a system crash, SESDCN must be restarted to preserve transaction consistency (see the “ Core manual”). SESDCN is responsible for coordinating, executing and monitoring the restart. If SESDCN has been loaded several times in the configuration, the SESDCN loaded first assumes this task. The SESDCN that carries out the restart is called the master DCN.
A SESDCN restart is the logical continuation of the previous SESDCN session. All the DCN options and distribution-rule entries of the previous session therefore apply.