SSC-FDM-0013
Timezone expression could not be mapped
Description
This FMD message is added to indicate scenarios where the actual value of a timezone expression cannot be determined, and therefore, the translated results might be different. When the timezone value used is a literal string, SnowConvert can take it and map it to its corresponding timezone value in Snowflake. However, when this value is specified by an expression, SnowConvert cannot get the timezone value that will be used at runtime and, therefore, cannot map this value to its corresponding Snowflake equivalent.
Example Code
Input Code (Oracle)
Output Code
Input Code (Teradata)
Output Code
Timezone Compatibility in Oracle
The majority of timezone name expressions in Oracle are directly supported in Snowflake, when this is the case, the migration will run without issues. Additionally, here is a list of which ones are not supported by Snowflake at the moment, and therefore will include the functional difference message.
Africa/Doula
Asia/Ulaanbaator
Asia/Yetaterinburg
Canada/East-Saskatchewan
CST
PST
US/Pacific-New
Recommendations
No end-user action is required.
If you need more support, you can email us at snowconvert-support@snowflake.com
Last updated