By using AWS re:Post, you agree to the Terms of Use
/Error loading metadata using AWS SCT against an RDS SQL Server Instance/

Error loading metadata using AWS SCT against an RDS SQL Server Instance

1

I am trying to use the AWS Schema Conversion Tool to convert a SQL Server instance running on RDS to Aurora MySQL. I have a large number of databases in the same SQL Server instance, and was able to successfully convert the schema for 5 of them. Then I attempted to use the "Refresh from Database" menu option for one of the databases and received an error stating

Metadata loading was interrupted because of data fetching issues. For details, see the log.

On checking the logs, I see the following error that is causing the issue:

Error executing 'load-script-object-ext-properties' query: com.microsoft.sqlserver.jdbc.SQLServerException: Collection specified does not exist in metadata : 'sys'

Now I am unable to see the schema of any database on that server, and they ALL fail with the same issue.

I have tried creating a new SCT project, and using a different SQL login.

I am completely blocked at the moment, and not sure how to progress my migration.

2 Answers
0

Hi, Thank you for reaching out. Looking at the error from the log: its throwing a SQL Server exception listed here: https://docs.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-events-and-errors?view=sql-server-ver15 This script "load-script-object-ext-properties” could be getting invoked by SCT menu "Refresh from Database”.

You can try to connect to SCT through master user of the SQL Server database and see if you are able to see the schemas of any database. In addition, if you have not already granted the permission required, please do so by repeating the grant for each database as mentioned here: https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Source.SQLServer.html#CHAP_Source.SQLServer.Permissions

If the above does not help, as a test, please try to create a sample database and a table with master user of your RDS SQL Server instance and check if you are able to view the schemas then.

In order to further help you with this issue, we require details (such as complete log) that are non-public information. Please open a support case with AWS using the following https://console.aws.amazon.com/support/home#/case/create.

SUPPORT ENGINEER
answered 5 months ago
0

Sometimes, a simple fix by DISCONNECTING from the SOURCE-database and creating a new SOURCE-Connection will fix such problems within SCT.

answered 5 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions