DB2 - Problembeschreibung
| Problem IC96963 | Status: Geschlossen |
SQL20208N RC=4 WHEN DECLARING A GLOBAL TEMPORARY TABLE BASED ON MULTIPLE TABLES WITH DIFFERENT SECURITY POLICIES | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP4 or later * **************************************************************** | |
| Local-Fix: | |
N/A | |
| verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
| Lösung | |
Problem was first fixed in DB2 10.1 FP4 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC99300 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.10.2013 28.07.2014 28.07.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.1.0.4 |
|