MySQL blocks creation of an additional replication channel when master and relay repositories are still set to FILE.
ER_SLAVE_NEW_CHANNEL_WRONG_REPOSITORY appears when you add a new replication channel while repositories are still FILE based; switch master_info_repository and relay_log_info_repository to TABLE, flush replica, then restart replication to resolve the issue.
ER_SLAVE_NEW_CHANNEL_WRONG_REPOSITORY
MySQL raises error 3077 when you attempt to create or start an additional replication channel while the master info and relay log info repositories remain configured as FILE. From MySQL 5.7.6 onward, multi source replication requires both repositories to use TABLE persistence.
The server rejects the request immediately, preventing an inconsistent replication state. Converting the repositories to TABLE enables safe operation with multiple channels.
The primary trigger is a replica that still uses FILE based repositories and then executes CHANGE REPLICATION SOURCE or START REPLICA FOR CHANNEL commands to add a new channel.
It also appears after upgrades when legacy parameters master_info_repository and relay_log_info_repository stay set to FILE while the DBA enables multi source replication.
Stop replication, switch both repository variables to TABLE, flush the replica to migrate metadata, and restart replication. Once converted, you can freely manage additional channels.
Galaxy users can run these commands in the editor, save them as an endorsed query, and share the fix with the team.
Adding an analytics channel on an existing replica - convert repositories to TABLE before issuing CHANGE REPLICATION SOURCE.
Cloning a replica from an older template - update my.cnf to set both repositories to TABLE before first start.
Provision all new 5.7 or later replicas with TABLE repositories, even if you plan to run a single channel initially.
Automate validation scripts that block multi channel commands unless the repository settings are already TABLE.
ER_SLAVE_CHANNEL_DELETE_ERR occurs when dropping a non existent channel; verify names with SHOW REPLICA STATUS.
ER_SLAVE_MAX_CHANNELS_EXCEEDED appears when exceeding the channel limit; increase performance_schema_max_table_instances or drop unused channels.
After upgrading to 5.7 or later, older configuration files may still specify FILE, triggering error 3077 when a new channel is added.
Switching master_info_repository to TABLE but leaving relay_log_info_repository as FILE also causes the error because both must match.
Automated deployment tools that omit repository settings default to FILE, leading to failures during multi channel setup.
Raised when attempting to drop a channel that does not exist; confirm with SHOW REPLICA STATUS.
Appears when the server exceeds the allowed number of replication channels; adjust limits or remove unused channels.
TABLE based metadata keeps per channel state in separate rows, allowing concurrent updates without file lock contention.
The conversion can be done online; you only stop replication on the replica, not the primary, so application traffic continues.
Galaxy's editor lets you store endorsed setup scripts that always set repositories to TABLE, reducing human error.
Yes, but you must disable additional channels first; FILE supports only a single channel.
.avif)
.avif){kind=logo}
