macOS - Software Lifecycle - Uninstall DBeaver Community

What the DBeaver Community uninstaller does

This Automox Worklet™ automatically detects the presence of the DBeaver Community application on macOS endpoints and removes it completely. DBeaver is a database management tool that supports SQL queries and administration across multiple database platforms including MySQL, PostgreSQL, Oracle, and Microsoft SQL Server.

The Worklet checks for the DBeaver.app bundle in the /Applications directory. If found, the Worklet removes the entire application package, eliminating the binary, configuration files, and associated resources in a single operation.

The Worklet is specifically designed for DBeaver Community edition. It does not affect other database management tools, IDEs, or applications that may share similar functionality.

Why remove DBeaver from your macOS endpoints

Uncontrolled database client software creates significant security and compliance risks. DBeaver Community provides direct database access to MySQL, PostgreSQL, Oracle, and SQL Server, allowing users to query, modify, and extract data without IT oversight. When unauthorized users install database tools, they bypass data access controls and audit logging that protect sensitive information.

Automated removal maintains consistent enforcement across your entire macOS fleet without requiring manual intervention on each endpoint. This is particularly valuable when sunsetting applications, transitioning to approved database management tools, or enforcing least-privilege software policies that restrict direct database access to authorized administrators.

By automating DBeaver removal through Automox, you gain visibility into which endpoints had the application installed and can track the remediation process in real time. This audit trail supports compliance reporting and security investigations.

How DBeaver uninstallation works

1. Evaluation phase: The Worklet checks whether the DBeaver.app directory exists in the /Applications directory. If the directory is present, the Worklet flags the endpoint for remediation and exits with a non-zero status. If DBeaver is not found, the Worklet exits with a zero status, indicating no action is required.

2. Remediation phase: The Worklet uses the bash rm command with the recursive flag to remove the entire /Applications/DBeaver.app directory and all contents. The removal operation attempts to delete the application package atomically. If removal succeeds, the Worklet exits with a zero status. If removal fails (due to permissions, locked files, or disk I/O errors), the Worklet exits with a non-zero status and logs diagnostic information to the Automox Activity Log.

DBeaver uninstallation requirements

• macOS 10.12 (Sierra) or later

• Administrator or root privileges to execute file system operations

• DBeaver Community version 1.0 or later installed in the /Applications directory

• No active DBeaver processes running at the time of remediation (the Worklet does not force-quit the application)

• Sufficient file system permissions to recursively delete the /Applications/DBeaver.app directory

Expected state after DBeaver uninstallation

Upon successful completion, the /Applications/DBeaver.app directory will be removed from the endpoint, and users can no longer launch the database client. Subsequent evaluation runs confirm compliance by verifying that DBeaver is not installed. The endpoint eliminates unauthorized database access capabilities while maintaining operational productivity for approved workflows.

User configurations and database connection profiles stored in ~/.dbeaver or ~/.config/dbeaver remain intact, allowing controlled reinstallation if users later receive proper authorization. Dock icons pointing to DBeaver become inactive. If DBeaver was running during Worklet execution, removal fails and the Automox Activity Log indicates the specific error. Retry the Worklet after users close the DBeaver application.

How to validate uninstall dbeaver community changes

1. Run this Worklet on a pilot macOS endpoint and review evaluation output for uninstall dbeaver community.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as exit, else.

4. Validate remediation effects from script operations such as exit, else, then rerun evaluation for compliance.