Re: JOIN USING problem
- From: CRPence <CRPence@xxxxxxxxxxxx>
- Date: Fri, 04 May 2012 16:20:10 -0700
On 04 May 2012 15:13, CRPence wrote:
On 04 May 2012 15:00, Jonathan Ball wrote:<<SNIP>> upgrade to V6R1 <<SNIP>>
I am running into a different problem at compile time. If I have the
schema (library) containing the tables in my library list at compile
time, the SQL precompiler throws an error SQL0203 saying that one of
the common columns (col3 or col4) is "ambiguous." This is exactly
why the columns had to be qualified with the table alias at V5R4.
However, if I qualify the column as as above, to remove the
ambiguity, the precompile fails as well.
This seems like a bug to me. Has anyone else encountered it?
Sorry, I had to do a "force quit" multiple times on my browser when looking at the PSP document for v7r1m0, found in the above web search, so initially I just sent the above.
If the PTF level is already c1256610 and\or latest DB Fixpack [i.e. SI42050 applied or superseded], then my SWAG is that very probably the v7r1 APAR SE50797 "OSP-DB-OTHER-MSGSQL0203 REFERENCING A FIELD IN A JOIN USING CLAUSE" which appears on the IBM i 7.1 PSP is likely going to have a corresponding APAR for IBM i 6.1; i.e. perhaps what got that fix in the 7.1 PSP listing, would be the same origin in the prior release, and similarly require a "replacement" PTF.
Seems the v6r1 APAR SE46048 "OSP-DB-OTHER-MSGSQL0203 OSP-DB-OTHER-MSGSQL0203" giving SI42050 correlates to the v7r1 PTF SI42092 [on C1116710] for APAR SE46048. The latter was the PTF that was replaced in v7r1 with PTF SI43721 for SE50797. If so, such a v6r1 PTF may exist already, available for test; unavailable on the web, as would be the case for the new APAR for different version of the OS. Regardless, probably best to call your service provider; probably ask directly if such a [test] PTF is available from a 6.1 APAR [as a SYSROUTE] from the 7.1 APAR SE50797.
- Prev by Date: Re: JOIN USING problem
- Next by Date: Re: JOIN USING problem
- Previous by thread: Re: JOIN USING problem
- Next by thread: Re: JOIN USING problem