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 IC96963 Status: Closed

SQL20208N RC=4 WHEN DECLARING A GLOBAL TEMPORARY TABLE BASED ON MULTIPLE
TABLES WITH DIFFERENT SECURITY POLICIES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Starting DB2 9.5 FP8, declaring a global temporary table may 
result in SQL20208N  rc=4 when all of the following conditions 
are satisfied: 
 
 
- the global temporary is declared using the AS (fullselect) 
syntax 
 
- the fullselect references multiple tables with different 
security policies 
 
 
 
SQL20208N  Table "<table-name>" cannot be created. Reason code = 
      "<reason-code>". 
 
Explanation: 
 
The table cannot be created because it violates a restriction as 
indicated by the following reason code: 
 
4. A materialized query table that references a protected table, 
a view 
   that depends on a protected table, or a nickname on which 
caching is 
   not allowed cannot be created.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP4 or later                             * 
****************************************************************
Local Fix:
N/A
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
Problem was first fixed in DB2 10.1 FP4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC99300 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.10.2013
28.07.2014
28.07.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