Conversion Issues

In this section, you will be able to find all the SnowConvert common issues with their respective description and possible solution.

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

Issue Codes

Here is the list of generic issue codes that exist in SnowConvert across all platforms. A detailed description of each issue code with its respective severity level can be seen in the following table.

Code	Description	Severity
MSCEWI1001	Error parsing the source code	Critical
MSCEWI1002	Removed next statement, not applicable in SnowFlake	Low
MSCEWI1003	Error executing a SQL conversion rule	Critical
MSCEWI1004	Error executing a script conversion rule	Critical
MSCEWI1005	File not generated log	Critical
MSCEWI1006	Error writing the top-level objects file	Critical
MSCEWI1007	Error writing the output file	Critical
MSCEWI1008	Expression at time zone changed	Low
MSCEWI1009	Error converting a top-level object	Critical
MSCEWI1010	No rule for procedure statement	Critical
MSCEWI1011	Unexpected end of the statement	High
MSCEWI1012	Unexpected end of the statement check line	High
MSCEWI1013	An Exception is thrown during conversion	Critical
MSCEWI1014	Procedure body not generated	Critical
MSCEWI1015	The input pivot/unpivot statement form is not supported	Medium
MSCEWI1016	Error writing details file	Critical
MSCEWI1017	Error writing summary file	Critical
MSCEWI1018	Error writing issues file	Critical
MSCEWI1019	Error writing the assessment report file	Critical
MSCEWI1020	Custom UDF Inserted	Low
MSCEWI1021	Syntax not supported	Medium
MSCEWI1022	Parameter missing dependency	Medium
MSCEWI1023	Loop performance review	Low
MSCEWI1024	Check constraint commented	Low
MSCEWI1025	Binding time variables might require a change	Low
MSCEWI1026	Qualified variables may require a cast	Low
MSCEWI1027	Variable with invalid query	Medium
MSCEWI1028	Type not supported	Medium
MSCEWI1029	No rule found for SQL node	Critical
MSCEWI1030	No rule was found for BTEQ node	Critical
MSCEWI1031	Function with Pending Equivalence Review	Medium
MSCEWI1032	Cast type not supported	Medium
MSCEWI1033	Semantic information not found	Low
MSCEWI1034	Format removed	Low
MSCEWI1035	CHECK statement not supported	Low
MSCEWI1036	Data type converted to another data type	Low
MSCEWI1037	Translation planned for the future	Medium
MSCEWI1038	Dynamic SQL statement may be unrecognized	Low
MSCEWI1039	Semantic information could not be loaded	Low
MSCEWI1040	Statement Not Supported	Low
MSCEWI1041	Crash parsing the source code file	Critical
MSCEWI1042	Non-relevant syntax	Low
MSCEWI1043	Translation for expression not supported	Medium
MSCEWI1044	Type changed to Date	Low
MSCEWI1045	Column name is a reserved keyword in Snowflake	Medium
MSCEWI1046	Verification of functional equivalence for function is pending	Low
MSCEWI1047	The statement was converted but its functionality is not implemented yet	Medium
MSCEW1048	Sequence warning.	Low
MSCEW1049	Not recognized function.	Low
MSCEWI1050	Missing dependent object	Low
MSCEWI1051	Unrecognized or unsupported parameter data type.	Medium
MSCEWI1052	Unusable object.	Medium
MSCEWI1053	Object may not work.	Low
MSCEWI1054	Unsupported outer join subquery	Low
MSCEWI1055	Data Type Not Recognized	Low
MSCEWI1056	Custom Types Not Supported	Low
MSCEWI1057	Create Type Variant Not Supported	High
MSCEWI1058	Functionality is not currently supported by Snowflake Scripting	Medium
MSCEWI1059	Non-Ansi Outer Join is not supported in OR predicate	Medium
MSCEWI1060	Non-Ansi Outer Join to multiple tables is not supported in Snowflake	High
MSCEWI1061	Column does not come from a Non-Ansi Outer Join Expression	Low
MSCEWI1062	Custom type usage changed to variant	Low
MSCEWI1063	Added statements because object used a custom type	Low
MSCEWI1064	Referenced custom type in query not found	High
MSCEWI1065	Columns from expression not found	High
MSCEWI1066	Number type column may not behave similarly in Snowflake	Low
MSCEWI1067	UDF was transformed to Snowflake procedure, calling procedures inside a query is not supported	High
MSCEWI1068	User defined function was transformed to a Snowflake procedure	Low
MSCEWI1069	User defined function inner logic was transformed to a single Common Table Expression	Low
MSCEWI1070	User defined function body not generated	Critical
MSCEWI1071	User defined function structured block was transformed to a single SQL Query	Low
MSCEWI1072	Window frame unit was changed to Rows	Low
MSCEWI1073	Pending Functional Equivalence Review	Medium
MSCEWI1074	Suffixes in numeric literals were removed	Low
MSCEWI1075	Current Of Clause is Not Supported	High
MSCEWI1076	Constants are not supported by Snowflake Scripting. It was transformed to a variable.	Low
MSCEWI1077	Cycle Found between CTE calls	Low
MSCEWI1078	Output parameters are not supported by Snowflake Scripting	Medium
MSCEWI1079	Parameter names were removed from call	Low
MSCEWI1080	Default value is not allowed on binary columns	Low
MSCEWI1081	Snowflake Scripting procedure cannot return more than one result set	Medium
MSCEWI1082	Auto-Generated code in order to support the output parameters functionality in Snowflake Sripting	Low
MSCEWI1083	Output parameters are not supported by Snowflake Scripting but their functionality is being emulated	Low
MSCEWI1084	XMLTABLE is not supported.	High
MSCEWI1085	Helper file generated for object	Low
MSCEWI1086	Replaced invalid characters for new identifier	Low
MSCEWI1087	Arguments do not match the called procedure parameters count, default parameters are not supported yet	Low
MSCEWI1089	Default value removed	Low
MSCEWI1090	Default value added	Low
​MSCEWI1091​	Create Index Not Supported	High
MSCEWI1092	Materialized View was converted to regular View	Low
MSCEWI1093	On Commit not supported	Medium
MSCEWI1094	Label declaration not supported	Low
MSCEWI1095	Object not renamed	Low
MSCEWI1096	TIME ZONE not supported for time data type	Medium
MSCEWI1097	Constraint in default expression is not supported.	Low
MSCEWI1098	Precision in milliseconds reduced to three digits.	Low
MSCEWI1099	Create table as subquery with no data is not supported in Snowflake	Low
MSCEWI1100	Multiple result sets are returned in temporary tables	Low
MSCEWI1101	Transaction label names are not supported in Snowflake	Low
MSCEWI1102	The statement option is removed and handled by conversion.	Low
MSCEWI1108	Snowflake does not have a PURGE clause inside the DROP TABLE statement	Low

Platform Specific Issues and Troubleshooting

Have an issue related to a specific source platform? Check out the individual pages for each source SnowConvert platform:

• SnowConvert for Oracle

• SnowConvert for SQL Server

• SnowConvert for Teradata

• SnowConvert for Scala

Issues Severity

In this section, you can find an explanation of the severities.

None (Information Only)

Informative notes for the user about successful conversion scenarios. No further action is needed. Some examples include:

• Code converted to a functionally equivalent output but that was emulated through a conversion workaround (primarily due to non-existing functionality in Snowflake)

• Code that is removed from the output because is no longer required (primarily due to architectural reasons)

Low

Warnings for the user about successful conversion scenarios that might be helpful to review. Some examples include:

Code converted to a functionally equivalent output but

• might still present minor differences in specific situations.

• might have performance issues in specific cases.

• some code improvements were not applied due to missing dependencies (tables, views definitions) in the input source code.

Medium

Errors that produce a functional or runtime difference. The user may have to invest a low amount of manual effort to complete the conversion.

High

Errors that produce a functional or runtime difference. The user may have to invest a high amount of manual effort to complete the conversion.

Critical

Errors that cause exceptions in SnowConvert. If the input source code is correct, a significant manual intervention will usually be required to complete the conversion. Examples are parsing and conversion errors.

Need more support?

Reach out! Whether you need additional support working through migration or if you need an additional feature, let us know. We are your partner in the conversion process. You can email us at [e-mail]. If you have a contract for support, reach out to your sales engineer and they can direct your support needs.