Archives of the TeradataForum
Message Posted: Wed, 28 Apr 2004 @ 13:54:51 GMT
Hi everyone: Just FYI on this thread,,,, Hoping this will be useful information for other user's on this forum. This problem is documented on ncr support site. It's called "v2r5 incorrect results may be returned with FULL OUTER JOIN involving PPI table.doc" Following is the symptom and workaround. However, workaround is only for PTDBMS.05.00.00.31 which is not an option since we are on V2R.05.00.01.05. We are considering modifying PPI table to Non-PPI table until a fix is available. If you know of a particular patch ( or workaround) that fixes the problem let me know. Thanks for all the responses for this thread.
(1) Optimizer chooses full outer merge join
(2) Full outer join should have Left table as a PPI table and right table is non-PPI table/spool.
(3) Right table should have a non matching constraint (single table condition given in the ON clause).
Placing READ lock on non-PPI table will ensure to get correct results. This is only applicable up to PTDBMS.05.00.00.31.
Until fix for DR84238 becomes available, there is no valid workaround for PTDBMS.05.00.00.32 and higher
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|