MySQL returns error 3167 (HY000) when a SQL statement tries to use a server feature that has been disabled by configuration, plugin absence, or build options.
MySQL error 3167 ER_FEATURE_DISABLED_SEE_DOC occurs when a query references a feature that the server has been compiled without or that you have explicitly disabled. Enable the feature with the right plugin, configuration flag, or upgrade path, then rerun the statement.
ER_FEATURE_DISABLED_SEE_DOC
Error 3167 (SQLSTATE HY000) appears when a client issues a command that relies on a MySQL feature the current server binary or configuration has disabled. The server stops the statement and returns: "The '%s' feature is disabled; see the documentation for".
MySQL introduced this error in version 5.7.9 to clarify why certain statements fail instead of producing unclear generic errors. Fixing it requires enabling or installing the missing capability.
The most frequent trigger is running a statement that needs an optional component, such as Group Replication, the Performance Schema, or the XA transaction engine, when that component is switched off in my.cnf or was excluded at compile time.
Upgrading or migrating databases can surface the error when new syntax reaches an older server lacking the required feature set. Cloud providers may also disable features for security or licensing reasons.
First, identify the placeholder text shown in the message (for example, 'Group Replication'). Consult the documentation for that feature to confirm the installation steps, configuration flags, and version requirements.
Next, enable the feature by loading the proper plugin, editing my.cnf, or upgrading to a server build that supports it. Restart the MySQL service to apply changes and rerun the failed query.
Attempting START GROUP_REPLICATION on a standalone community build will trigger error 3167. Install the group_replication plugin or use MySQL Enterprise, then enable it with INSTALL PLUGIN and SET GLOBAL group_replication_enabled = ON.
Executing XA START when the mysqld binary was compiled with -DWITHOUT_XA=1 also raises the error. Replace the binary with a standard distribution that ships WITH_XA or recompile MySQL with XA support.
Pin your application queries to a documented feature matrix and ensure staging mirrors production configuration. Use SELECT PLUGIN_STATUS or SHOW VARIABLES to audit enabled capabilities during deployments.
Tools like Galaxy surface server variables and plugin status in a single pane, letting engineers verify feature availability before running feature-dependent SQL.
Error 1289 Unknown storage engine 'X' occurs when a table references an engine that is not loaded. Enable the storage engine plugin to resolve.
Error 1227 Access denied; you need (at least one of) the SUPER privilege often accompanies 3167 if the fix requires INSTALL PLUGIN. Grant the proper privilege or have an administrator perform the installation.
The MySQL binary was built without optional components such as XA or Group Replication.
The required plugin exists but has not been installed or loaded (INSTALL PLUGIN missing).
my.cnf or runtime variables explicitly switch off the feature (e.g., performance_schema=OFF).
Managed MySQL services may disable certain features for security or licensing.
Thrown when a CREATE TABLE specifies a storage engine not loaded. Install the engine plugin.
Occurs when attempting to query a disabled Performance Schema table. Enable the performance schema.
Appears when lacking privileges to enable or install the needed feature.
No. The server rejects the statement because the feature is off, not because of user privileges. You might still need SUPER to enable the feature.
Ignoring it means the requested functionality will never run. Applications relying on the feature will fail, so fixing is recommended.
Upgrading to a build that includes the feature often resolves the error, but you still may need to enable or configure it post-upgrade.
Galaxy exposes plugin status and server variables, alerting engineers before they execute feature-dependent SQL.