× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi All,
I just got bitten by this error today:

Message ID . . . . . . . . . :
SQL0338
Message file . . . . . . . . :
QSQLMSG
Library . . . . . . . . . :
QSYS
Message ID . . . . . . . . . : SQL0338
Message file . . . . . . . . : QSQLMSG
Library . . . . . . . . . : QSYS
Message text . . . . . . . . : JOIN predicate not valid.

V6
R1

Message . . . . : JOIN predicate not
valid.
Cause . . . . . : The JOIN predicate is not valid because a column
is
specified that exists in a table that is outside the scope of the
join
predicate. The scope is generally determined from left to right but is
also
based on the position of the join-condition. If parentheses are
used,
columns inside the parentheses can not come from a table outside
the

parentheses.

Recovery . . . : Do one of the following and try the request
again:
-- Make certain that the column names, table names, and any qualifiers
are
specified
correctly.
-- Specify parentheses around joined tables to specify a join order
other
than left to right. Ensure columns exist in tables that are in the
same

scope.

V7 R1
Message text . . . . . . . . : JOIN predicate or MERGE ON clause not
valid.
essage . . . . : JOIN predicate or MERGE ON clause not
valid.
ause . . . . . : The JOIN predicate, or ON clause of a MERGE statement,
is
not valid because a column is specified that exists in a table that
is
outside the scope of the join predicate or ON clause. The scope
is
generally determined from left to right but is also based on the position
of
the join-condition. If parentheses are used, columns inside the
parentheses
cannot come from a table outside the parentheses. If an implicit join
(using
a comma) is specified prior to a joined table with an ON clause, columns
in
the ON clause cannot come from a table before the
comma.
ecovery . . . : Do one of the following and try the request
again:
-- Make certain that the column names, table names, and any qualifiers
are
specified
correctly.
-- Specify parentheses around joined tables to specify a join order
other
than left to right. Ensure columns exist in tables that are in the
same

scope.

-- For an ON clause in a MERGE statement, ensure referenced columns
are
within the scope of the ON
clause.
-- Specify a CROSS JOIN instead of an implicit
join.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.