Issues and Troubleshooting
Learn more about the conversion issues in SnowConvert, and how to solve them.
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. Mobilize.Net has been the leading authority on code conversion for 25 years, and trust us, we understand this. When using any of our products, 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 post in the SnowConvert forums or drop us an email at [email protected]. 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.
Here is the list of error codes that exist in SnowConvert. A description of the severity levels and some troubleshooting suggestions will follow this list of codes.
Code | Description | Severity |
---|---|---|
Recursive forward alias error | Medium | |
Interval type not supported | High | |
Collation not supported in trim functions, add original collation to function result to preserve it | Low | |
Invalid default value. | Low | |
Geo-Spatial not supported | Medium | |
Column name not supported. | Low | |
Output parameter translated as a return statement | Low | |
Cluster by performance review. | Low | |
Temporal column not supported. | Low | |
Uppercase not supported. | Low | |
Time zone not supported for time data type. | Low | |