Sequence For Restarting Vocera Analytics After MariaDB Lock Wait Timeout

The MariaDB service must be restarted before starting any other service in case of a lock wait timeout by Engage Data Export adapter. This topic describes the sequence of steps to be followed to restart the services successfully.

The Engage Data Export adapter experiences lock wait timeout if there is a loss of network connectivity.

To resolve the lock wait timeout, the database service on Windows must be restarted prior to restarting the other services, or Engage Data Export adapter. Specifically, the MariaDB service must be restarted prior to Spark and Data Export Adapter. The Spark service has the Hikari Connection Pool that must be created again with the database in a normal state. The Data Export Adapter can be restarted earlier, however it will not be able to successfully resume operation until the database is reset and restarted.

Perform the following sequence of steps for stopping and starting services:

Use the Stop All Services button to stop services that may be currently accessing the database.
Navigate to the Windows Services and Stop the MariaDB service.
The MariaDB service is now stopped.
Restart the MariaDB Windows service.
Use the Start All Services button to start services for Vocera Analytics.
Restart any other processes such as Engage Data Export adapters.