Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97633 Status: Closed

FEDERATED QUERY MAY RECEIVE SQL0418N ERROR IF FEDERATED DATABASE SET
STMT_CONC=LITERALS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Federated query failed with the following error when STMT_CONC 
is set to LITERALS: 
 
( 
   (select 'comset3' as SCHEMA ,'CSFRDCSPEC_HOLD_RULE_DC' as 
TBL_NAME , 
           DCSPEC_ID,DCITEM_NAME 
   from comset3.CSFRDCSPEC_HOLD_RULE_DC) except 
   (select 'comset3' as SCHEMA ,'CSFRDCSPEC_HOLD_RULE_DC' as 
TBL_NAME , 
           DCSPEC_ID,DCITEM_NAME 
   from comset4.CSFRDCSPEC_HOLD_RULE_DC)) 
Union ( 
(select 'comset4' as SCHEMA ,'CSFRDCSPEC_HOLD_RULE_DC' as 
TBL_NAME ,DCSPEC_ID, 
        DCITEM_NAME 
from comset4.CSFRDCSPEC_HOLD_RULE_DC) except 
   (select 'comset4' as SCHEMA ,'CSFRDCSPEC_HOLD_RULE_DC' as 
TBL_NAME , 
           DCSPEC_ID,DCITEM_NAME 
   from comset3.CSFRDCSPEC_HOLD_RULE_DC)) 
 
SQL1822N  Unexpected error code "-418" received from data source 
"DB2SERVER". 
Associated text and tokens are " SQL0418N  A statement contains 
a use of an 
untyped par".  SQLSTATE=560BD 
 
 
From access plan, the parameter marker is used in select list of 
the remote statement: 
 
RMTQTXT : (Remote statement) 
            SELECT DISTINCT A0."DCSPEC_ID", A0."DCITEM_NAME", 
-1, :H0 , :H1  FROM "SIVIEW"."CSFRDCSPEC_HOLD_RULE_DC" A0 FOR 
READ ONLY
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users whose federated database SET STMT_CONC=LITERALS will   * 
* be affected                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 fp4 or above                                * 
****************************************************************
Local Fix:


available fix packs:


DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 


Solution


The fix will be included in v10.1 fp4


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.11.2013
02.06.2014
02.06.2014


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)


10.1.0.4

FixList