|
Problem IC99300
|
Status: Closed |
SQL20208N RC=4 WHEN DECLARING A GLOBAL TEMPORARY TABLE BASED ON MULTIPLE TABLES WITH DIFFERENT SECURITY POLICIES |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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 users with DGTT *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) or higher. *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.02.2014
22.09.2014
22.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
