Synchronizing Database Tables

Each COO Service reports if a database synchronization is necessary using the property Database Synchronization Required (COOSYSTEM@1.1:coosrvdbsyncrequired) at the “Tables” page of the COO Service object and using Fabasoft app.telemetry counters. Additionally, there are performance counters on Windows and SNMP counters on Linux systems, but they are not available in a container environment.

The synchronization is done during the restart of the COO Service, if requested, and may take a large amount of time, depending on the database size. In case of an error, the synchronization is resumed on the next restart. An upgrade may implicitly trigger a schema synchronization.

In a classic environment it can be requested by selecting the task “Synchronize Database Tables” using the Fabasoft Server Management MMC snap-in (Windows) or the Web Management Console (Linux). The task can be achieved on the command line using fscinstall -syncdatabase. The Fabasoft Folio Management service restarts the COO Service and the synchronization is done on startup before any requests are served.

In a container environment it can be requested by executing the command line cooload -syncdatabase within the administration (or any other kernel) container. The COO Service then gracefully shuts itself down, allowing the currently running RPCs to finish by waiting for a maximum of 10 seconds, and is then restarted by the container orchestration environment (e.g. Kubernetes or OpenShift). The synchronization is done on startup before any requests are served.