Issues and Troubleshooting
In this section, you will find information about Errors, Warnings, and Issues on the 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 IBM DB2 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.
Here is the list of error codes that SnowConvert might generate for IBM DB2 conversions. A description of the severity levels and some troubleshooting suggestions will follow this list of codes.
In this section, you could find an explanation of the severities.
Warnings for source code that there was no direct conversion to Snowflake. The code has been converted to a functionally equivalent output but should still be reviewed.
Errors that produce a functional or runtime difference. The user may have to invest a low amount of manual effort to complete the conversion.
Errors that produce a functional or runtime difference. The user may have to invest a high amount of manual effort to complete the conversion.
Parsing errors or errors that cause significant conversion exceptions in SnowConvert. If the source code is correct, a significant intervention will be required.