home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC62887 Status: Closed

QUERIES WITH A UNION ALL VIEW OF TABLES FROM FEDERATED SERVERS MAY CAUSE
MEMORY OVERWRITTEN

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Queries with a Union All view of tables from remote data sources 
(data from federated servers) may cause memory overwritten.  The 
problem may happen when all of the following conditions are met 
 
1. The database manager configuration parameter 'FEDERATED' is 
set to 'YES'. 
2. Running a query with a Union All view of tables from the 
federated servers, referred to as UAV. 
3. The query has a IN or EXISTS subquery with view UAV as the 
parent table of the subquery. 
4. The view UAV has a column referencing to constants of 
CHARACTER type. 
5. The constants of CHARACTER type in 4) has different length 
6. Each table from the federated servers has a unique index 
 
A typical use of the constants is to use different values to 
identify the tables under the Union All view. 
 
For example, 
 
The Union All view is defined as: 
CREATE VIEW UAV AS 
SELECT 'BR' AS TABNAME, T.* FROM FED_TABLE1 
UNION ALL 
SELECT 'BR1' AS TABNAME, T.* FROM FED_TABLE2; 
 
Both table FED_TABLE1 AND table FED_TABLE2 have unique indexes 
defined in the remote servers where the data of the table 
physically located. 
 
Assume TABLE_REF is a table. 
 
The query 
 
SELECT UAV.* 
FROM  UAV 
WHERE UAV.TABNAME IN (SELECT TABNAME FROM TABLE_REF); 
 
may cause memory overwritten.
Problem Summary:
QUERIES WITH A UNION ALL VIEW OF TABLES FROM FEDERATED SERVERS 
MAY CAUSE MEMORY OVERWRITTEN
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB Version 9.7, FixPak 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.09.2009
28.12.2009
28.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList