fbpx

This is just a short warning when you are upgrading to Teradata 16.20.

We recently upgraded from Teradata 15.10 to 16.20 and detected that some of our reporting queries returned with each execution a different result set. Sometimes the result set was correct, sometimes wrong.

After analyzing a little bit I found out that it’s related to Incremental Planning and Execution (IPE). Seems that something can go wrong with the execution plan when this feature is active. I will further investigate and give you an update if I can find out more about this issue. It’s quite possible that there is already a patch available. Any input is appreciated.

Since I turned this feature off, the result set is always correct (I am adding below query band as a pre-SQL to each Microstrategy report until this issue is fixed):

SET QUERY_BAND = ‘DynamicPlan=OFF;’ FOR SESSION;

I think this information might be useful for some of you experiencing this problem.

 Explanatory note: I just want to save you valuable time in case you experience this issue and have yet no solution. It’s definitely not meant to talk down Teradata. 

__CONFIG_colors_palette__{"active_palette":0,"config":{"colors":{"62516":{"name":"Main Accent","parent":-1}},"gradients":[]},"palettes":[{"name":"Default Palette","value":{"colors":{"62516":{"val":"var(--tcb-skin-color-0)"}},"gradients":[]},"original":{"colors":{"62516":{"val":"rgb(19, 114, 211)","hsl":{"h":210,"s":0.83,"l":0.45}}},"gradients":[]}}]}__CONFIG_colors_palette__
__CONFIG_colors_palette__{"active_palette":0,"config":{"colors":{"b4fbe":{"name":"Main Accent","parent":-1}},"gradients":[]},"palettes":[{"name":"Default Palette","value":{"colors":{"b4fbe":{"val":"rgb(241, 99, 52)"}},"gradients":[]},"original":{"colors":{"b4fbe":{"val":"rgb(19, 114, 211)","hsl":{"h":210,"s":0.83,"l":0.45}}},"gradients":[]}}]}__CONFIG_colors_palette__
Previous Article
__CONFIG_colors_palette__{"active_palette":0,"config":{"colors":{"b4fbe":{"name":"Main Accent","parent":-1}},"gradients":[]},"palettes":[{"name":"Default Palette","value":{"colors":{"b4fbe":{"val":"rgb(241, 99, 52)"}},"gradients":[]},"original":{"colors":{"b4fbe":{"val":"rgb(19, 114, 211)","hsl":{"h":210,"s":0.83,"l":0.45}}},"gradients":[]}}]}__CONFIG_colors_palette__
Next Article
Buy the Book Teradata Query Performance Tuning

DWH Pro Admin

Roland Wenzlofsky is an experienced freelance Teradata Consultant & Performance Trainer. Born in Austria's capital Vienna, he is building and tuning some of the largest Teradata Data Warehouses in the European financial and telecommunication sectors for more than 20 years. He has played all the roles of developer, designer, business analyst, and project manager. Therefore, he knows like no other the problems and obstacles that make many data warehouse projects fail and all the tricks and tips that will help you succeed.

  • Avatar
    Roland Wenzlofsky says:

    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

  • Avatar
    Shardul Kumar says:

    We still dont have TD 16.20, still working on TD 15.10. But good to know this and thank you Roland!

  • {"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

    You might also like

    >