There are some important considerations to keep in mind when upgrading to Teradata 16.20.
After upgrading to Teradata 16.20, we noticed that certain reporting queries produced inconsistent result sets upon each execution. Occasionally, the results were accurate, while at other times they were inaccurate.
Upon analysis, I found a correlation between Incremental Planning and Execution (IPE). When this function is enabled, the execution plan may encounter errors. I will conduct additional research and provide an update regarding this matter. It is possible that a patch has already been released. Your feedback is welcome.
Ever since disabling this feature, my result sets have been consistently accurate. To ensure this remains the case until a resolution is found, I am implementing the following query band as a pre-SQL step on every Microstrategy report.
SET QUERY_BAND = ‘DynamicPlan=OFF;’ FOR SESSION;This information could be helpful to those encountering this issue.
Related Services
🔧 Need Expert Database Administration?
Our team brings 25+ years of enterprise DBA experience across Teradata, Snowflake, and Oracle.
Meet Our Team →📋 Considering a Move From Teradata?
Get a personalized migration roadmap in 2 minutes. We have migrated billions of rows from Teradata to Snowflake, Databricks, and more.
Free Migration Assessment →
The Problem was fixed with an update.
Hey Guys,
Thanks for the update, can you provide a test case that demonstrates this wrong result?
We are on 16.10 right now and are soon upgrading to 16.20
Would someone care to respond to my above mentioned query?
Still awaiting response from OP
As far as I know, the issue was fixed with a patch/update.
We still dont have TD 16.20, still working on TD 15.10. But good to know this and thank you Roland!