You may run into issue when using SSMA to connect to Oracle database containing foreign characters (non-ASCII characters) in its schema. In the example below, we have an Oracle database containing a table with Japanese name:
The issue is caused by the Oracle client provider not able to process SQL statement containing non-ASCII characters. In order to display the table attributes, SSMA submits a separate query with table name as filtering criteria in its SQL statement. In the example above, when SQL statement submitted to the Oracle client provider containing table name Japanese character, the statement failed.
One workaround is by using OLEDB provider to connect to Oracle:
OLEDB provider is able to process the SQL statement containing non-ASCII character and show the table attributes correctly.
Note that if you have an existing SSMA project with Oracle Client Provider to connect, you need to create a new project using OLEDB Provider.