The SELECT Aurora_Version() function is specific to Amazon Aurora not recognized by Cloud SQL.
As for the schemas not being created automatically on the destination database, this could be due to a variety of reasons. It might be a permissions issue, or it could be that the schema creation statements are not included in the migration process.
Here are a few steps you could take to resolve these issues:
-
Modify the Database Scripts: If possible, modify the database scripts to remove or replace any functions or queries that are not supported by the destination database. In this case, you might need to find an alternative to the
SELECT Aurora_Version()function. -
Create the Schemas Manually: If the schemas are not being created automatically, you could try creating them manually on the destination database before starting the migration.
-
Check the Permissions: Make sure that the account used for the migration has the necessary permissions to create schemas on the destination database.