Issues and Troubleshooting

Learn more about the conversion issues in SnowConvert, and how to solve them.

This is a deprecated version of the SnowConvert documentation, please visit the official site HERE.

Before we get too far down the troubleshooting road, recall that we highly recommend that you go through our training labs in order to get the most out of SnowConvert.

Conversions of any large quantity of code will likely have a few errors and warnings. When using any of our tools, you can count on us to be your partner in resolving any errors you may encounter.

Below is a list of specific conversion issues for Teradata that you may see when you perform a conversion with SnowConvert along with a severity level for each. Some suggested solution paths based on the severity level will follow the list of codes.

Take a minute to read through the list and the troubleshooting tips to help diagnose some of the error codes you have encountered. If you have a question that cannot be answered here, please reach out! You can drop us an email at [e-mail]. This is a living list, so it will grow and change as SnowConvert evolves. Updates to issue and error handling will appear on this page, and will also appear in the release notes.

Issue Codes

Here is the list of issue codes that exist in the SnowConvert for the Teradata platform. A detailed description of each issue code with its respective severity level can be seen in the following table.

Code	Description	Severity
MSCEWI2001	Recursive forward alias error	Medium
MSCEWI2002	Interval type not supported	High
MSCEWI2003	Collation not supported in trim functions, add original collation to function result to preserve it	Low
MSCEWI2004	Invalid default value.	Low
MSCEWI2005	Geo-Spatial not supported	Medium
MSCEWI2006	Column name not supported.	Low
MSCEWI2007	Output parameter translated as a return statement	Low
MSCEWI2008	Cluster by performance review.	Low
MSCEWI2009	Temporal column not supported.	Low
MSCEWI2010	Uppercase not supported.	Low
MSCEWI2011	Time zone not supported for time data type.	Low
MSCEWI2012	Not supported by binary type.	Low
MSCEWI2013	Column converted from Blob data type.	Low
MSCEWI2014	Column converted from Clob data type.	Low
MSCEWI2015	Set table not supported.	Low
MSCEWI2016	Global temporary table not supported.	Low
MSCEWI2017	Global temporary table trace not supported.	Low
MSCEWI2018	Collation not supported in variant column.	Low
MSCEWI2019	Converted to Varchar for current session default.	Low
MSCEWI2020	Only Posix regex supported.	Low
MSCEWI2021	Unsupported use of 'match_arg' parameter.	Low
MSCEWI2022	Work or error table commented.	Low
MSCEWI2023	Dynamic SQL statement may be unrecognized	Medium
MSCEWI2024	Abort statement not supported	Low
MSCEWI2025	Output format not supported	Low
MSCEWI2026	Json fields are inserted in an ascending ordering	Low
MSCEWI2027	Snowflake does not support Teradata built-in time dimensions column options	Low
MSCEWI2028	Run file must contain python statements only	Low
MSCEWI2029	Queue table not supported	Low
MSCEWI2030	DBC reference not supported	Medium
MSCEWI2031	The result may differ due to char type having a fixed length in Teradata	Low
MSCEWI2032	Columns were reordered.	Medium
MSCEWI2033	Columns may be reordered	Medium
MSCEWI2034	Multistatement SQL not supported.	Low
MSCEWI2035	Cast might implicate an automatic trimming with Substring function.	Low
MSCEWI2036	STRING to STRING Cast might require to be changed to Substring function.	Low
MSCEWI2037	DELETE ALL statement replaced to TRUNCATE	Low
MSCEWI2038	Repeated label was renamed	Low
MSCEWI2039	Input format not supported	Medium
MSCEWI2040	Format in a table not supported	Low
MSCEWI2041	TRUNC added to ensure integer	Medium
MSCEWI2042	Binding time variables might require change in query	Low
MSCEWI2043	Default decimal precision in convert timezone is three digits	Low
MSCEWI2044	Warning lose of decimal precision in time	Low
MSCEWI2045	VIEW Check Option Not Supported in Snowflake	Low
MSCEWI2046	Temporary Table might have duplicated rows	Low
MSCEWI2047	Function does not support argument with certain collation constraints	Medium
MSCEWI2048	A function was not recognized by the conversion too	Low
MSCEWI2049	TPT-Statement not processed	Low
MSCEWI2050	TRANSLATE function has different behavior in certain cases	Low
MSCEWI2051	Teradata BYTES function results differs from Snowflake LENGTH function for byte columns	Low
MSCEWI2052	Snowflake implicit conversion to numeric differs from Teradata and may fail for non-literal string values	Low
MSCEWI2053	Snowflake does not support the period datatype, all periods are handled as varchar instead	Low
MSCEWI2054	Teradata Database Temporal Table is not supported in Snowflake	Medium
MSCEWI2055	Snowflake supported formats for TO_CHAR differ from Teradata and may fail or have different behavior	Low
MSCEWI2056	Column added to the Select's columns to avoid errors when referencing strtok_split_to_table function.	Low
MSCEWI2057	Binary data in NEW JSON is not supported	Low
MSCEWI2058	Non-standard time zone offsets are not supported in Snowflake, rounded to nearest valid time zone	Low
MSCEWI2059	Snowflake user default time zone may require configuration to match Teradata value	Low
MSCEWI2060	Snowflake user default time zone may require configuration to match Teradata value	Medium
MSCEWI2061	TD_UNPIVOT transformation requires column information that could not be found, columns missing in result	Medium
MSCEWI2062	JSON value was not recognized due to invalid format	Medium
MSCEWI2063	JSON path was not recognized	Medium
MSCEWI2064	Unicode BMP escape is not supported	Low
MSCEWI2065	Non Unique Primary Index is not supported in Snowflake	Low
MSCEWI2066	The following identifier has one or more Unicode escape characters that are invalid in snowflake	Low
MSCEWI2068	Snowflake does not support profiles, referencing role instead	Medium
MSCEWI2069	ST_DISTANCE results are slightly different from ST_SPHERICALDISTANCE	Low
MSCEWI2070	A return statement was added at the end of the label section to ensure the same execution flow	Medium
MSCEWI2071	GOTO statement was replaced with the label section with the same name	Low
MSCEWI2072	LABEL not found, GOTO statement was replaced with return statement	Low
MSCEWI2073	Bash variables found, using SnowSQL with variable substitution enabled is required to run this script	Low
MSCEWI2074	Period types are handled as two data fields	Low
MSCEWI2075	The Snowflake error code mismatch the original Teradata error code	Low
MSCEWI2076	The use of foreign tables is not supported in Snowflake	Medium
MSCEWI2077	RESET WHEN clause is not supported in this scenario due to its condition	Medium
MSCEWI2078	The Expand On clause functionality is transformed into a CTE block	Low
MSCEWI2079	The required period type column was not found	Low
MSCEWI2080	Non-literal delimiters with spaces need their backslash scaped in snowflake	Low
MSCEWI2081	Translate function TO_UNICODE encoding is not required	Low
MSCEWI2082	Translate function using the current encoding is not supported	Medium
MSCEWI2083	Not able to transform two or more complex Select clauses at a time	Medium
MSCEWI2084	Transaction and profile level query tags not supported in Snowflake, referencing session query tag instead	Medium
MSCEWI2085	Redundant reference to a Table in UpdateStatement removed.	Low
MSCEWI2086	Shell variables found, manually assigning values to the variables is required to run this script.	Low
MSCEWI2087	GOTO statement was removed due to if statement inversion	Medium
MSCEWI2088	LAYOUT was not found	Low
MSCEWI2089	DML label was not found	Low
MSCEWI2090	Conditions not found in the update statement for transformation	Low
MSCEWI2091	Expression converted as cast with possible errors due to missing dependencies	Low

How should you troubleshoot each error type? Troubleshooting is not an exact science, especially when it comes to complex code conversion. We’ve given you a description of each of the severity levels and some suggestions on how to handle each error type below.

Error Severity

Conversion errors happen. For Snowflake SnowConvert, errors are put into the following categories:

• Low

• Medium

• High

• Critical

Regardless of the error severity, step 1 in troubleshooting a conversion is always to check the source code, especially if you receive a large number of errors. Ensure that it compiles in Teradata first. Oftentimes a misplaced quote or parenthesis could lead to an entire file not converting correctly.

Beyond that, please review the severity levels and information below. It’s worth reiterating that if you have a conversion that did not succeed, please reach out! We would love to hear from you.

Let’s look at each severity level and see what we recommend as the next steps.

Low

Low-level errors are not actually errors. They are considered warnings. In other words, we are confident the code as a whole was converted, and it will compile in Snowflake. However, some things may look different. For example, SnowConvert changes a CREATE SET TABLE statement to a CREATE TABLE statement. An issue will be logged with code MSCEWI2015 in the issues report, and a comment will be placed above the line where the original CREATE SET TABLE statement was written. The code was successfully converted, but there was a change made. The reason you would create a SET table in Teradata may still exist for your table in Snowflake, but Snowflake’s architecture does not support Set Tables. For 99%+ of all Set Tables we've seen, this transformation is sufficient and the output code is functionally equivalent. Having said that, we would still recommend that you take a look at the output to ensure that the standard table is functionally equivalent in Snowflake. We are confident that it will but would recommend that you still check on it.

Medium

Medium-level errors indicate that a small piece of an object did not convert correctly, such as a line of code in a table statement or a macro/procedure. Check the issues report finding the exact location of the error. Depending on the context, that line or statement may not be necessary or there may be an issue with the source code. There are some terms or elements that SnowConvert does not yet recognize, even though the tool receives regular updates and version releases. For these types of errors, the output is usually a commented-out version of the input. Check the line in the output, and determine if that will need a manual conversion or if it can be removed. If you are not sure what to do next, reach out!

High

A high-level error indicates that an entire object could not be converted. This will require you to evaluate the object in question (procedure, macro, join, and so on) and evaluate the source code. Most high-level conversion errors indicate there is information that simply did not make sense. The vast majority are resolved by updating the source code, not the output code. The remainder usually comes from a term that SnowConvert does not yet recognize. Post in the forums or send us an email so we can partner with you in solving this problem.

Critical

Critical errors are exceptionally rare (less than 1% of objects' error codes), but they do happen. A critical error will most likely cause SnowConvert to fail and a crash report screen to come up. Please give as much information as you can in the crash report screen so we can diagnose the issue. If a crash report screen does not appear, please check the issues report focusing on the critical errors. Though the program completely converted the code, the presence of critical errors could indicate there are other unrecognized errors as well. Hopefully and most likely, you will not find yourself in this situation. If you do, check the source code again, and let us know.

Need more support?

As has been mentioned previously in this article, please reach out to us if you need more support. Snowflake wants to be your partner in the conversion process, so let us know how we can help. You can email us at [e-mail]. If you have a contract for support with Snowflake, reach out to your sales engineer and they can direct your support needs.