<p>Error 1619 appears when you try to delete a built-in MySQL plugin with DELETE PLUGIN, an operation the server blocks.</p>
<p>MySQL Error 1619 WARN_PLUGIN_DELETE_BUILTIN occurs when DELETE PLUGIN targets a built-in module. Built-in plugins are compiled into the server and cannot be removed; disable them with configuration changes or upgrade to 5.7.4+, where the warning was removed, to clear the issue.</p>
Built-in plugins cannot be deleted
MySQL raises Error 1619 when the DELETE PLUGIN statement references a plugin that is compiled directly into the MySQL server binary. These built-in plugins are integral to the executable and cannot be dropped dynamically.
The error text Built-in plugins cannot be deleted makes clear that the operation is disallowed. From MySQL 5.7.4 onward, the warning was removed because MySQL blocks the statement at parse time.
The error appears immediately after executing DELETE PLUGIN plugin_name on versions prior to 5.7.4. On later versions the statement fails during parsing with a similar message. It is platform-agnostic and surfaces in any MySQL edition that supports plugins.
Leaving a failed DELETE PLUGIN in deployment scripts causes automated builds to stop, replication to break, and configuration management tools to report drift. Cleaning the script or disabling the plugin correctly restores reliable provisioning.
The primary trigger is a DELETE PLUGIN command executed against a built-in plugin. Other causes include misunderstanding plugin status, copy-pasted instructions meant for optional plugins, and automated migrations created for different MySQL versions.
First, verify whether the target plugin is built-in by querying INFORMATION_SCHEMA.PLUGINS. If Type is BUILT_IN, deletion is impossible. Instead, comment out the DELETE PLUGIN line or disable the plugin in my.cnf if the server allows skip-style options.
On versions 5.7.4 and later, simply remove the faulty command. For earlier versions, prevent execution with conditional logic in deployment scripts.
During an upgrade, a script tries to drop InnoDB or CSV plugins: remove the line because both are built-in. Another scenario involves a cloud image originally compiled without PERFORMANCE_SCHEMA; dropping it later throws 1619. Validate plugin type before deletion.
Check plugin metadata before running DELETE PLUGIN. Maintain version-specific deployment scripts. Use IF NOT EXISTS logic where available. Track plugin loads in your configuration management tool so built-in status is documented.
Error 1510 ER_PLUGIN_IS_NOT_LOADED arises when unloading an unplugged plugin. Fix by INSTALL PLUGIN first or removing the UNINSTALL PLUGIN line. Error 1530 ER_PLUGIN_BUSY appears when a plugin is in use; stop related sessions before unloading.
Attempting to remove core plugins like InnoDB or Performance Schema triggers error 1619 because they are compiled into the server.
Migrating scripts from other environments that treat a plugin as optional often includes DELETE PLUGIN lines that fail on servers where the plugin is built-in.
Commands valid on older MySQL versions might reference plugins that later became built-in, making the deletion step obsolete and erroneous.
Infrastructure as Code templates sometimes generate DELETE PLUGIN statements without checking plugin type, leading to repeated failures.
Raised when UNINSTALL PLUGIN targets a plugin that is not currently active.
Occurs when a plugin is in use and cannot be uninstalled until related operations finish.
This connection error may appear during plugin misconfiguration that blocks authentication plugins.
No. Built-in plugins are compiled into the server. You must recompile MySQL without the plugin or upgrade to a distribution that omits it.
Ignoring the warning leaves invalid commands in your automation, which may break future deploys. Remove or replace the statement.
MySQL 5.1 through 5.7.3 raise error 1619 at execution. Starting with 5.7.4 the warning was removed and the parser blocks the command earlier.
Galaxy highlights server warnings instantly in its editor and lets teams review and version deployment scripts, reducing the chance of pushing a DELETE PLUGIN command against a built-in module.
.avif)
.avif){kind=logo}
