Code Conversion - Informatica PowerCenter Conversion Issues

This section provides detailed documentation for the Error, Warning, and Information (EWI) messages that may be generated during Informatica PowerCenter conversion.

For assistance with any EWI, you can use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions, or contact aim-support@snowflake.com for additional support.

SSC-EWI-INF0001

This Informatica PowerCenter transformation is not supported.

Severity

Critical

Description

This issue is reported when an Informatica PowerCenter mapping is converted and a transformation with no supported equivalent is encountered. Its logic is not translated automatically and must be reproduced by hand.

Converted Code

!!!RESOLVE EWI!!! /*** SSC-EWI-INF0001 - INFORMATICA POWERCENTER TRANSFORMATION IS NOT SUPPORTED BY SNOWCONVERT ***/!!!
cte_fil_transform AS
(
   -- Unsupported transformation 'FIL_Transform' (UnsupportedTransformation)
   SELECT
      null AS ID,
      null AS NAME
)

Best Practices

SSC-EWI-INF0002

Informatica PowerCenter expression cannot be converted.

Severity

High

Description

This issue is reported when an Informatica PowerCenter mapping is converted and a specific expression cannot be translated into Snowflake SQL. The affected expression is left unconverted and requires a manual equivalent.

Best Practices

SSC-EWI-INF0003

Informatica PowerCenter workflow element cannot be converted.

Severity

High

Description

This issue is reported when an Informatica PowerCenter workflow is converted and a specific workflow element cannot be translated into Snowflake Scripting. The affected element is left unconverted and requires manual reproduction.

Best Practices

SSC-EWI-INF0004

Informatica PowerCenter mapping element could not be pre-processed.

Severity

High

Description

This issue is reported when an Informatica PowerCenter mapping is converted and a mapping element cannot be pre-processed. Because pre-processing did not complete for that element, its conversion may be incomplete and requires manual review.

Best Practices

SSC-EWI-INF0005

Informatica PowerCenter column name could not be resolved.

Severity

High

Description

This issue is reported when an Informatica PowerCenter mapping is converted and a column name cannot be resolved. As a fallback, the column name taken from the transform field is used, which may not match the intended reference.

Best Practices

SSC-EWI-INF0006

Embedded SQL cannot be converted.

Severity

High

Description

This issue is reported when an Informatica PowerCenter mapping is converted and embedded SQL from the source type cannot be converted into Snowflake SQL. The embedded SQL is left unconverted and requires a manual equivalent.

Best Practices

SSC-EWI-INF0007

Unexpected exception converting transformation.

Severity

High

Description

This issue is reported when an unexpected exception occurs while converting an Informatica PowerCenter transformation. The affected transformation may not be fully converted and requires manual review.

Best Practices

SSC-EWI-INF0008

Informatica TO_CHAR format contains unsupported elements that may require manual review.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter TO_CHAR call whose format string contains unsupported elements is converted. These elements may behave differently in Snowflake, so the converted format may require manual review.

Best Practices

SSC-EWI-INF0009

TO_CHAR format argument is not a literal and could not be converted.

Severity

Critical

Description

This issue is reported when the format argument of an Informatica PowerCenter TO_CHAR call is not a literal value. Because the format is determined at runtime rather than being a fixed literal, it cannot be converted automatically and requires manual review.

Best Practices

SSC-EWI-INF0010

Multiple models target the same table with mismatched column counts.

Severity

High

Description

This issue is reported when multiple models write to the same target table but with different column counts. Because the target instances have mismatched column sets, they cannot be merged into a single model and must be reconciled manually.

Best Practices

SSC-EWI-INF0011

Informatica PowerCenter built-in function not converted to Snowflake SQL.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted and a built-in function cannot be converted to Snowflake SQL. The affected function is left unconverted and requires a manual equivalent.

Best Practices

SSC-EWI-INF0012

Informatica PowerCenter built-in variable is not supported.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted and an unsupported built-in variable is encountered. The affected variable is not converted and requires manual handling.

Best Practices

SSC-EWI-INF0013

Informatica PowerCenter mapplet variables are not supported.

Severity

High

Description

This issue is reported when an Informatica PowerCenter mapplet that contains variables is converted. These mapplet variables are not converted to dbt and require manual handling.

Best Practices

SSC-EWI-INF0014

Source Qualifier uses Informatica PowerCenter variables in SQL Query property.

Severity

Medium

Description

This issue is reported when a Source Qualifier uses Informatica PowerCenter variables in its SQL Query property. Because these variables are not converted automatically, the generated query requires manual review.

Best Practices

SSC-EWI-INF0015

Source Qualifier uses Informatica PowerCenter variables in WHERE conditions.

Severity

Medium

Description

This issue is reported when a Source Qualifier uses Informatica PowerCenter variables in a User Defined Join or Source Filter. Because these variables are not converted automatically, the resulting WHERE conditions require manual review.

Best Practices

  • Review the User Defined Join or Source Filter and replace the Informatica PowerCenter variables with equivalent values or parameters in Snowflake.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0016

INSTR search value is not a literal and regex escaping could not be applied.

Severity

Critical

Description

This issue is reported when the search value of an Informatica PowerCenter INSTR call is not a literal. Because the value is determined at runtime, regex special characters cannot be escaped, so the conversion requires manual review.

Best Practices

SSC-EWI-INF0017

INSTR negative start position is not supported.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter INSTR call uses a negative start position, which is not supported. The start position has been defaulted to 1, so the converted call requires manual review.

Best Practices

SSC-EWI-INF0018

Source Qualifier uses Informatica PowerCenter variables in Pre SQL property.

Severity

Medium

Description

This issue is reported when a Source Qualifier uses Informatica PowerCenter variables in its Pre SQL property. Because these variables are not converted automatically, the generated Pre SQL requires manual review.

Best Practices

SSC-EWI-INF0019

Source Qualifier uses Informatica PowerCenter variables in Post SQL property.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The Source Qualifier references Informatica PowerCenter variables inside its Post SQL property, and these variables cannot be resolved automatically during conversion.

Best Practices

  • Review the Post SQL statement and manually replace the Informatica PowerCenter variables with the appropriate Snowflake values or dbt configuration.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0020

ADD_TO_DATE format string is not a recognized Informatica date part.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The format string supplied to ADD_TO_DATE is not a recognized Informatica date part, so it was passed through as-is to the Snowflake DATEADD function. You should verify that the date part is valid in Snowflake.

Best Practices

SSC-EWI-INF0021

GET_DATE_PART format argument is not a literal and could not be converted.

Severity

Critical

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The format argument passed to GET_DATE_PART is not a literal value, so it could not be converted to a Snowflake DATE_PART date part.

Best Practices

SSC-EWI-INF0022

GET_DATE_PART format string is not a recognized Informatica date part.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The format string supplied to GET_DATE_PART is not a recognized Informatica date part, so it was passed through as-is to the Snowflake DATE_PART function. You should verify that the date part is valid in Snowflake.

Best Practices

SSC-EWI-INF0024

IS_DATE without format uses session date format in Informatica but Snowflake auto-detects formats.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. When IS_DATE is used without a format, Informatica relies on the session date format, whereas Snowflake automatically detects the format instead. This difference may lead to different results.

Best Practices

SSC-EWI-INF0025

Informatica IS_DATE format contains unsupported elements and may produce different results.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The Informatica IS_DATE format contains unsupported elements, so the converted expression may produce different results in Snowflake.

Best Practices

SSC-EWI-INF0026

Informatica TO_DATE format contains unsupported elements that may require manual review.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The Informatica TO_DATE format contains unsupported elements that may require manual review or may behave differently in Snowflake.

Best Practices

SSC-EWI-INF0027

TO_DATE format argument is not a literal and could not be converted.

Severity

Critical

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The format argument passed to TO_DATE is not a literal value, so it could not be converted to Snowflake.

Best Practices

SSC-EWI-INF0028

VSAM Normalizer transformation is not supported.

Severity

Critical

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The Normalizer was generated from a COBOL source definition (VSAM) and cannot be automatically converted to Snowflake dbt, so manual conversion is required.

Best Practices

SSC-EWI-INF0029

Aggregator passthrough column approximated with MAX() function.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. An Aggregator without a GROUP BY contains one or more passthrough columns, and while Informatica returns the last value processed, Snowflake uses the MAX() function as an approximation. Results may differ depending on the input data order.

Best Practices

SSC-EWI-INF0030

ADD_TO_DATE format argument is not a literal and could not be converted.

Severity

Critical

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The format argument passed to ADD_TO_DATE is not a literal value, so it could not be converted to a Snowflake DATEADD date part.

Best Practices

SSC-EWI-INF0033

Sequence Generator Start Value exceeds integer range.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The Sequence Generator start value produces an offset that exceeds the integer range supported by the SQL literal, so the generated offset has been clamped. Manual adjustment of the start value offset is required.

Best Practices

SSC-EWI-INF0034

Mapping has multiple session overrides of its update strategy.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The mapping has multiple session overrides of its update strategy, which cannot be reconciled automatically during conversion.

Best Practices

SSC-EWI-INF0035

Update strategy not directly connected to target transformation requires manual changes.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The update strategy is not connected to the target transformation, so manual changes are required to complete the conversion.

Best Practices

SSC-EWI-INF0037

Informatica PowerCenter disconnected stored procedure call cannot be converted to Snowflake SQL.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. A disconnected stored procedure call cannot be converted to a SQL expression during the migration to Snowflake.

Best Practices

SSC-EWI-INF0038

Stored procedure uses a named connection that must be manually mapped.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The stored procedure uses a named connection, and named connections must be manually mapped to the corresponding Snowflake database and schema in the dbt profile or project configuration.

Best Practices

SSC-EWI-INF0039

dbt folder hooks execute once per model, not once per session.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. dbt folder hooks execute once per model in the folder, not once per session as in Informatica. If the procedure must run only once, consider using an on-run-start or on-run-end hook instead.

Best Practices

SSC-EWI-INF0040

Stored Procedure transformation is translated assuming the procedure has been converted to a UDF.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter mapping is converted. The Stored Procedure transformation is translated assuming the procedure has been converted to a UDF, because the original Informatica transformation called the procedure once per row while the translation calls it as an inline UDF. You should convert the stored procedure to a Snowflake UDF that returns OBJECT_CONSTRUCT with named fields matching the output port names.

Best Practices

SSC-EWI-INF0041

Port has Informatica-specific ERROR() default value with no Snowflake equivalent.

Severity

Low

Description

This issue is reported when an Informatica PowerCenter mapping is converted. A port declares a default value of ERROR('transformation error'), which is an Informatica-specific error function that has no direct Snowflake equivalent. The default value has been omitted from the translation.

Best Practices

SSC-EWI-INF0042

Informatica PowerCenter CUME running total translated to SUM aggregate approximation.

Severity

Medium

Description

The Informatica PowerCenter CUME function computes a running total row by row in pipeline order, depending on a preceding Sort transformation. It was translated to SUM, which computes a single total aggregate. Inside an Aggregator with a group by clause the final output value is equivalent because there is one row per group, but the running-total semantics and the sort-order dependency are lost.

Best Practices

SSC-EWI-INF0043

Sequence Generator row ordering is non-deterministic and state is not persisted.

Severity

Low

Description

The Sequence Generator is translated to ROW_NUMBER() OVER (ORDER BY 1). Row ordering is non-deterministic, so values may be assigned to different rows between runs, and the sequence state is not persisted across dbt executions, so it always restarts from the start value.

Converted Code

!!!RESOLVE EWI!!! /*** SSC-EWI-INF0043 - THE SEQUENCE GENERATOR IS TRANSLATED TO ROW_NUMBER() OVER (ORDER BY 1). ROW ORDERING IS NON-DETERMINISTIC (VALUES MAY BE ASSIGNED TO DIFFERENT ROWS BETWEEN RUNS) AND SEQUENCE STATE IS NOT PERSISTED ACROSS DBT EXECUTIONS (ALWAYS RESTARTS FROM START VALUE). ADD A DETERMINISTIC ORDER BY IF STABLE SEQUENCE ASSIGNMENT IS REQUIRED. ***/!!!
SELECT
   *,
   ROW_NUMBER() OVER (ORDER BY 1) + 9 AS NEXTVAL
FROM
   source_data

Best Practices

SSC-EWI-INF0044

Sequence Generator cycle count is not evenly divisible.

Severity

Low

Description

The Sequence Generator cycle count is not evenly divisible because the difference between the end value and the start value is not a multiple of the increment. The generated sequence will not reach the end value before cycling, so manual adjustment may be required.

Best Practices

SSC-EWI-INF0045

Sequence Generator has Cycle=YES but EndValue is the default.

Severity

Low

Description

The Sequence Generator has Cycle set to YES, but its end value is left at the default maximum. The cycle expression cannot be generated with a meaningful cycle count, so the sequence is emitted without cycling and manual adjustment is required if cycling behavior is needed.

Best Practices

SSC-EWI-INF0046

Active Java Transformation cannot be automatically translated.

Severity

High

Description

An active Java transformation cannot be automatically translated, and the transformation may change row cardinality. This issue is reported when an Informatica PowerCenter mapping is converted.

Best Practices

SSC-EWI-INF0047

Output-only port is set by Java code and cannot be automatically translated.

Severity

Low

Description

An output-only port is set by Java code and cannot be automatically translated. This issue is reported when an Informatica PowerCenter mapping is converted.

Best Practices

SSC-EWI-INF0048

Java Transformation uses update strategy (setOutRowType).

Severity

Low

Description

A Java transformation uses an update strategy through the setOutRowType method. Manual migration of the row-type logic is required.

Best Practices

SSC-EWI-INF0049

Java Transformation generates transactions (commit/rollback).

Severity

Low

Description

A Java transformation generates transactions through commit and rollback calls, and Snowflake transaction semantics differ. Manual review is required.

Best Practices

SSC-EWI-INF0050

Informatica PowerCenter user-defined function call cannot be automatically converted to Snowflake SQL.

Severity

Medium

Description

An Informatica PowerCenter user-defined function call, written with the :UDF. prefix followed by the function name, was not converted to Snowflake SQL. This issue is reported when an Informatica PowerCenter mapping is converted.

Best Practices

SSC-EWI-INF0051

Informatica PowerCenter ERROR() function has no Snowflake equivalent.

Severity

High

Description

The Informatica PowerCenter ERROR() function causes the Integration Service to skip the current row and log a message. There is no equivalent row-skip mechanism in Snowflake SQL, so the function is replaced with NULL.

Best Practices

SSC-EWI-INF0052

Informatica REG_EXTRACT match_from_start parameter has no Snowflake equivalent.

Severity

Medium

Description

The Informatica REG_EXTRACT function accepts a match_from_start parameter, where a non-zero value anchors the match at the start of the string. Snowflake REGEXP_SUBSTR has no equivalent anchor parameter.

Best Practices

  • When match_from_start is non-zero, prefix the pattern with a ^ anchor manually or verify that anchoring is not required for your data.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0053

SET_DATE_PART format argument is not a literal and could not be converted.

Severity

Critical

Description

The SET_DATE_PART format argument is not a literal, so it could not be converted to a Snowflake DATE_PART date part. This issue is reported when an Informatica PowerCenter mapping is converted.

Best Practices

SSC-EWI-INF0054

SET_DATE_PART format string is not supported in Snowflake.

Severity

Critical

Description

The SET_DATE_PART format string is not supported in Snowflake because DATE_PART does not accept millisecond or microsecond parts in this context. This issue is reported when an Informatica PowerCenter mapping is converted.

Best Practices

SSC-EWI-INF0055

Informatica PowerCenter Email task contains workflow/service variables that cannot be resolved.

Severity

Medium

Description

An Informatica PowerCenter Email task contains workflow or service variables in the email subject or body. These variables cannot be automatically resolved in Snowflake, so manual conversion is required.

Best Practices

SSC-EWI-INF0056

Informatica PowerCenter Email task has no recipients.

Severity

High

Description

An Informatica PowerCenter Email task has an empty or missing email user name attribute. The generated notification integration and SYSTEM$SEND_EMAIL call will fail at runtime.

Best Practices

SSC-EWI-INF0057

Informatica PowerCenter Decision task condition references task status or row counts.

Severity

High

Description

An Informatica PowerCenter expression references task status or row count properties, such as task status, previous task status, source success rows, target failed rows, total transformation errors, first error code, first error message, start time, and end time. These runtime metrics have no direct equivalent in Snowflake Task DAGs, so manual conversion is required.

Best Practices

SSC-EWI-INF0058

Informatica PowerCenter workflow link condition cannot be translated to a Snowflake WHEN clause.

Severity

High

Description

An Informatica PowerCenter workflow link condition references variables or expressions that cannot be evaluated in a Snowflake Task WHEN clause, so the WHEN clause was omitted. The task will run unconditionally unless the condition is enforced inside the task body.

Best Practices

SSC-EWI-INF0059

Sequence Generator fan-out: per-pipeline counters in dbt vs shared counter in Informatica.

Severity

Medium

Description

This issue is reported when a Sequence Generator is connected to multiple independent pipelines in a fan-out topology. In Informatica PowerCenter the sequence counter is shared across all pipelines, so it produces non-overlapping identifiers, but in dbt each pipeline receives an independent ROW_NUMBER() starting from 1, so counter values will overlap between pipelines. Review the generated per-pipeline intermediate models and decide whether sequential numbering across pipelines is required.

Best Practices

  • Review the generated per-pipeline intermediate models and confirm whether unique identifiers across all pipelines are required, adjusting the numbering logic if overlap is not acceptable.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0060

Informatica PowerCenter ABORT() function has no Snowflake equivalent.

Severity

High

Description

This issue is reported when an Informatica PowerCenter mapping that uses the ABORT() function is converted. The ABORT() function immediately stops the Integration Service session and marks it as failed, but there is no equivalent session-abort mechanism in Snowflake SQL, so the function is replaced with NULL. You should implement the required error-handling logic using Snowflake streams, tasks, or pre and post SQL scripts.

Best Practices

  • Implement the required error-handling logic using Snowflake streams, tasks, or pre and post SQL scripts to replace the removed abort behavior.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0061

Lookup condition predicate not fully converted.

Severity

Medium

Description

This issue is reported when one or more Lookup condition predicates could not be fully converted, for example function calls, literals, or complex expressions. As a result the generated join or WHERE clause may be incomplete. Review the original Lookup condition and add the missing predicates manually.

Best Practices

SSC-EWI-INF0062

Informatica PowerCenter mapplet input port has no incoming connector.

Severity

Low

Description

This issue is reported when a mapplet input port has no incoming connector. In this case NULL is used as a fallback SQL expression for that port.

Best Practices

  • Verify whether the mapplet input port should receive a value and provide the correct source expression if the NULL fallback is not appropriate.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0063

Source Qualifier SQL Query is procedural, not a single SELECT or CTE.

Severity

High

Description

This issue is reported when a Source Qualifier SQL query contains procedural code and cannot be converted into a dbt model body. The original SQL is preserved as a comment.

Best Practices

SSC-EWI-INF0064

Flat File Lookup stage path variable requires manual mapping to a Snowflake stage.

Severity

High

Description

This issue is reported when a Flat File Lookup stage path variable requires manual mapping to a Snowflake stage. The referenced file format must already exist in the target database.

Best Practices

SSC-EWI-INF0065

Expression transformation uses Lagger Technique but no preceding Sorter found for ORDER BY.

Severity

Medium

Description

This issue is reported when an Expression transformation uses the Lagger Technique, a local variable forward reference that accesses values from previous rows. It is translated to a LAG window function with a non-deterministic ORDER BY 1 because no preceding Sorter transformation was found. Manual intervention is required to replace ORDER BY 1 with a deterministic column so that row ordering is correct.

Best Practices

  • Replace the non-deterministic ORDER BY 1 in the generated LAG window function with a deterministic column that guarantees correct row ordering.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0066

Informatica PowerCenter self-referencing source-to-ref override was not applied.

Severity

Low

Description

This issue is reported when a self-referencing source-to-ref override could not be applied because the expected source reference was not found in the generated SQL. As a result the dbt model may fail to compile. Verify that the source reference exists and manually replace it with the correct ref call if needed.

Best Practices

SSC-EWI-INF0067

Informatica PowerCenter file could not be parsed and was skipped.

Severity

Medium

Description

This issue is reported when an Informatica PowerCenter file could not be parsed and was therefore skipped. The message includes the affected file name and the reported cause.

Best Practices

SSC-EWI-INF0068

Fixed-width flat file format is not supported.

Severity

High

Description

This issue is reported when a flat file source uses a fixed-width format, which cannot be mapped to a Snowflake file format. Manual conversion is required.

Best Practices

  • Manually convert the fixed-width flat file into a format that Snowflake supports, such as a delimited file with an appropriate file format.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0069

Flat File Source stage path variable requires manual mapping to a Snowflake stage.

Severity

High

Description

This issue is reported when a Flat File Source stage path variable requires manual mapping to a Snowflake stage. The referenced file format must already exist in the target database.

Best Practices

SSC-EWI-INF0070

Flat file source code page has no known Snowflake ENCODING mapping.

Severity

Medium

Description

This issue is reported when a flat file source code page has no known Snowflake ENCODING mapping. The file format will default to UTF-8, so you should verify this or add the encoding clause manually.

Best Practices

SSC-EWI-INF0071

Flat file source text qualifier cannot be mapped to Snowflake FIELD_OPTIONALLY_ENCLOSED_BY.

Severity

Medium

Description

This issue is reported when a flat file source text qualifier is not a recognized single-character value and cannot be mapped to Snowflake’s FIELD_OPTIONALLY_ENCLOSED_BY option. The clause has been omitted, so add it manually if needed.

Best Practices

  • Review the source text qualifier and add a valid single-character FIELD_OPTIONALLY_ENCLOSED_BY value to the file format manually if needed.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0072

Flat file target requires manual mapping of stage path variable.

Severity

High

Description

This issue is reported when a flat file target requires manual mapping. You must set the associated variable to your Snowflake stage path.

Best Practices

SSC-EWI-INF0073

Flat file target has ‘Append if Exists’ enabled but Snowflake does not support appending to stage files.

Severity

Medium

Description

This issue is reported when a flat file target has the ‘Append if Exists’ option enabled. Snowflake COPY INTO does not support appending to existing stage files, so the generated output uses overwrite mode instead.

Best Practices

  • Review the overwrite behavior of the generated COPY INTO output and adjust your process if appending to existing stage files was required.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0074

Flat file target has a non-UTF8 codepage but ENCODING is not supported in COPY INTO location (unload).

Severity

Medium

Description

This issue is reported when a flat file target has a non-UTF-8 codepage mapped to a Snowflake encoding. The ENCODING option is only valid for COPY INTO a table when loading, not for COPY INTO a location when unloading, and Snowflake always writes UTF-8 when unloading to a stage.

Best Practices

  • Account for the fact that Snowflake always writes UTF-8 when unloading, and add a downstream conversion step if a different target encoding is required.
  • Use the Snowflake AIM Agent for Data Warehouses to get AI-powered explanations and actionable solutions for this issue.
  • If you need more support, email us at aim-support@snowflake.com.

SSC-EWI-INF0075

Flat file target uses an escape character but Snowflake CSV unload does not support escape characters.

Severity

Medium

Description

This issue is reported when a flat file target uses an escape character. Snowflake COPY INTO a location with CSV format does not support an escape character for unloading, so fields containing the delimiter must be enclosed instead.

Best Practices