Because a MySQL migration job
doesn't migrate user data,
sources which contain metadata defined by users with the
DEFINER clause will
fail when invoked on the new Cloud SQL replica, as the users do not yet
To identify which
DEFINER values exist in your metadata, use these queries and
check if there are entries for either
root%localhost or for users that don't exist in the
SELECT DISTINCT DEFINER FROM INFORMATION_SCHEMA.EVENTS; SELECT DISTINCT DEFINER FROM INFORMATION_SCHEMA.ROUTINES; SELECT DISTINCT DEFINER FROM INFORMATION_SCHEMA.TRIGGERS; SELECT DISTINCT DEFINER FROM INFORMATION_SCHEMA.VIEWS;
To run a migration job from a source which includes such metadata, you can do one of the following:
Create the users on your destination Cloud SQL instance before starting your migration job.
Create a migration job without starting it. That is, choose Create instead of Create & Start.
Create the users from your source MySQL instance on your destination Cloud SQL instance using the Cloud SQL API or UI.
Start the migration job from the migration job list or the specific job's page.
INVOKERon your source MySQL instance prior to setting up your migration job.