type property

Identifies the specific error that occurred. Possible string values are:

• "SQL_EXTERNAL_SYNC_SETTING_ERROR_TYPE_UNSPECIFIED"
• "CONNECTION_FAILURE"
• "BINLOG_NOT_ENABLED"
• "INCOMPATIBLE_DATABASE_VERSION"
• "REPLICA_ALREADY_SETUP"
• "INSUFFICIENT_PRIVILEGE" : The replication user is missing privileges that are required.
• "UNSUPPORTED_MIGRATION_TYPE" : Unsupported migration type.
• "NO_PGLOGICAL_INSTALLED" : No pglogical extension installed on databases, applicable for postgres.
• "PGLOGICAL_NODE_ALREADY_EXISTS" : pglogical node already exists on databases, applicable for postgres.
• "INVALID_WAL_LEVEL" : The value of parameter wal_level is not set to logical.
• "INVALID_SHARED_PRELOAD_LIBRARY" : The value of parameter shared_preload_libraries does not include pglogical.
• "INSUFFICIENT_MAX_REPLICATION_SLOTS" : The value of parameter max_replication_slots is not sufficient.
• "INSUFFICIENT_MAX_WAL_SENDERS" : The value of parameter max_wal_senders is not sufficient.
• "INSUFFICIENT_MAX_WORKER_PROCESSES" : The value of parameter max_worker_processes is not sufficient.
• "UNSUPPORTED_EXTENSIONS" : Extensions installed are either not supported or having unsupported versions
• "INVALID_RDS_LOGICAL_REPLICATION" : The value of parameter rds.logical_replication is not set to 1.
• "INVALID_LOGGING_SETUP" : The primary instance logging setup doesn't allow EM sync.
• "INVALID_DB_PARAM" : The primary instance database parameter setup doesn't allow EM sync.
• "UNSUPPORTED_GTID_MODE" : The gtid_mode is not supported, applicable for MySQL.
• "SQLSERVER_AGENT_NOT_RUNNING" : SQL Server Agent is not running.
• "UNSUPPORTED_TABLE_DEFINITION" : The table definition is not support due to missing primary key or replica identity, applicable for postgres.
• "UNSUPPORTED_DEFINER" : The customer has a definer that will break EM setup.
• "SQLSERVER_SERVERNAME_MISMATCH" : SQL Server @@SERVERNAME does not match actual host name.
• "PRIMARY_ALREADY_SETUP" : The primary instance has been setup and will fail the setup.
• "UNSUPPORTED_BINLOG_FORMAT" : The primary instance has unsupported binary log format.
• "BINLOG_RETENTION_SETTING" : The primary instance's binary log retention setting.
• "UNSUPPORTED_STORAGE_ENGINE" : The primary instance has tables with unsupported storage engine.
• "LIMITED_SUPPORT_TABLES" : Source has tables with limited support eg: PostgreSQL tables without primary keys.
• "EXISTING_DATA_IN_REPLICA" : The replica instance contains existing data.
• "MISSING_OPTIONAL_PRIVILEGES" : The replication user is missing privileges that are optional.
• "RISKY_BACKUP_ADMIN_PRIVILEGE" : Additional BACKUP_ADMIN privilege is granted to the replication user which may lock source MySQL 8 instance for DDLs during initial sync.
• "INSUFFICIENT_GCS_PERMISSIONS" : The Cloud Storage bucket is missing necessary permissions.
• "INVALID_FILE_INFO" : The Cloud Storage bucket has an error in the file or contains invalid file information.
• "UNSUPPORTED_DATABASE_SETTINGS" : The source instance has unsupported database settings for migration.
• "MYSQL_PARALLEL_IMPORT_INSUFFICIENT_PRIVILEGE" : The replication user is missing parallel import specific privileges. (e.g. LOCK TABLES) for MySQL.
• "LOCAL_INFILE_OFF" : The global variable local_infile is off on external server replica.
• "TURN_ON_PITR_AFTER_PROMOTE" : This code instructs customers to turn on point-in-time recovery manually for the instance after promoting the Cloud SQL for PostgreSQL instance.