|
Problem IC99667
|
Status: Geschlossen |
DRDA WRAPPER REPORTS SQL3324N WHEN CREATING NICKNAME FOR A TABLE USES LBAC |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
The user will receive a SQL3324N error when creating a DRDA
nickname for a table that use label-based access control (LBAC).
This problem is a regression of APAR IC96409, so it only
impacts the db2level higher than V97FP7.
To reproduce the problem:
On data source side:
db2 => CREATE SECURITY LABEL COMPONENT LEVEL ARRAY ['Top
Secret', 'Secret', 'Classified', 'Unclassified']
DB20000I The SQL command completed successfully.
db2 => CREATE SECURITY POLICY DATA_ACCESS COMPONENTS LEVEL WITH
DB2LBACRULES
DB20000I The SQL command completed successfully.
db2 => CREATE TABLE TTT(C1 SYSPROC.DB2SECURITYLABEL) SECURITY
POLICY DATA_ACCESS
DB20000I The SQL command completed successfully.
On Federation Side:
db2 => CREATE NICKNAME NNN FOR SERV.DB2INST1.TTT
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL3324N Column "C1" has a type of "DISTINCT" which is not
recognized. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* The users attempt to create nickname for tables using LBAC. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V10.5 FP4. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
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
|
| Lösung |
The problem is firstly fixed on V10.5 FP4. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 26.02.2014
08.09.2014
08.09.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.4
|
 |
