When the Presto Repository is hosted in a robust database solution, it must be started before the Presto Server for a successful startup. With the default Derby database, the Presto Repository runs as an embedded database that is automatically started with the Presto Server.

In environments where you application server is started automatically with the host, this can create timing errors. You may need to stop and restart the Presto Server after the Presto Repository has been restarted.

If you host the Presto Repository in a MySQL or Oracle database, you may also be able to have the database start automatically with the host.