DBPTK Enterprise - unable to remove database

[ars-lna]

After pushing SIARD Delete button, database name still appears in the list.
If we try to open the database, we see only Database(loading) message and a blank page.

[dosubot]

Hi @ars-lna! I'm Dosu and I’m helping the dbptk-ui team.

This issue is often caused by backend errors or resource limitations—such as Solr indexing failures, Java heap space exhaustion, or running out of disk space—which prevent the database from being fully deleted and removed from the list. When this happens, the UI may still show the database name, and trying to open it results in a perpetual "Database(loading)" message and a blank page. Increasing the Solr heap size in your docker-compose.yml (for example, SOLR_HEAP=8G) and ensuring there is enough disk space has resolved similar problems for other users [source 1] [source 2].

Check your backend logs for Solr or Java errors during the delete operation. If the backend fails to process the deletion, the frontend can't remove the database from the list. You may also want to verify if the database directory is still present on disk or has been moved to a database-garbage folder (if the DELETE_DBS_NOT_FOUND flag is enabled in your deployment scripts) [source 3].

Freeing up resources, increasing heap size, and cleaning up disk space usually resolves the issue. If the database directory remains, you may need to remove it manually after ensuring the backend is healthy.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[ars-lna]

@dosu, your suggestion: "If the database directory remains, you may need to remove it manually ...". Please explain, how to remove it manually.

[dosubot]

To manually remove a database directory in DBPTK Enterprise (especially after a failed delete in the UI), follow these steps:

1. Locate the database directories:

   • If you are using Docker, the SIARD database directories are stored on the host machine under ./volumes/siards/databases (relative to your docker-compose.yml location). This is mapped into the container at /volumes/siards via the DBPTKE_SHARED_FOLDER environment variable.
   • Each database is stored in its own subdirectory named after its UUID inside the databases folder.
   • Example path: ./volumes/siards/databases/<database-uuid> on your host machine [docker-compose.yml].

2. Stop DBPTK Enterprise services (recommended):

   • This prevents the backend or Solr from accessing the database while you delete it, avoiding possible inconsistencies.

3. Delete the database directory:

   • Use a file manager or run a command like rm -rf ./volumes/siards/databases/<database-uuid> (replace <database-uuid> with the actual folder name).
   • If your deployment uses the DELETE_DBS_NOT_FOUND flag, you may see a database-garbage folder where "orphaned" databases are moved instead of deleted outright [migration script].

4. Restart DBPTK Enterprise:

   • This ensures the backend and Solr reindex and the UI updates the list of available databases.

5. Check the UI:

   • The deleted database should no longer appear. If it still does, you may need to clear Solr indexes or restart related services.

Note: There is no evidence of automatic Solr cleanup if you delete the directory manually, so if you see stale entries in the UI, a Solr reindex or cleanup may be needed.

Let me know if you need the exact commands for your environment or more details on Solr cleanup.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.