|
Problem IC99650
|
Status: Closed |
DRDA WRAPPER REPORTS SQL3324N WHEN CREATING NICKNAME FOR A TABLE USES LBAC |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* The user is creating a DRDA nickname for a table that use *
* label-based access control (LBAC). *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW V10.1 FP4 or Federation Server V10.1 FP4 *
**************************************************************** |
| Local Fix: |
|
| 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 |
The problem is firstly fixed on V10.1 FP4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.02.2014
02.06.2014
02.06.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
|
 |
