Symptoms:

  • LogPublisher reports errors like “A lock could not be obtained within the time requested”
  • LogPublisher reports timeouts

Solution:

The underlying I/O system is not able to handle the required use case with the configured amount of logging in an appropriate time. The I/O load relies on writing a full recovery log at the database system.  We strongly recommended high level storage systems based on SSD caching technology, which perform an average load of 1000 IOPS/second minimum.

Since version 7.0.8854:
You can disable the full recovery log at System options -> Archive options -> Backup – Enable full recovery (Write ahead log).

Please note: In case of disaster recovery, ALL transaction data could be lost! Better select a more performant I/O system.

See also:

Integrated database needs huge amount of disc space