|
Problem IC95256
|
Status: Closed |
AN INSERT, UPDATE OR DELETE STATEMENT ON A TABLE WITH ROW AND COLUMN ACCESS CONTROL ENABLED MAY RESULT IN SQL901N OR SQL1224N. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
If row and column access control (RCAC) has been enabled on a
table, an INSERT, UPDATE or DELETE statement on the table that
fires a trigger may result in SQL901N or SQL1224N.
In the case of SQL901N, the following error and reason will be
returned:
SQL0901N The SQL statement or command failed because of a
database system
error. (Reason "no permission generated".) SQLSTATE=58004
db2diag.log will contain the corresponding entry:
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 23
sqlerrmc: no permission generated
sqlerrp : SQLNQD16
sqlerrd : (1) 0x801A006D (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFD76 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
DATA #8 : Hex integer, 4 bytes
0x00000040
DATA #9 : String with size, 46 bytes
insert into test (description) values ('test')
DATA #10: String, 299 bytes
Compiler error stack for rc = -2144272209:
sqlnn_cmpl [340]:rc(-2144272270) Global semantic
sqlns_qgs [ 97]:rc(-2144272270) Compiling FGAC
sqlnq_compile_fgac [100]:rc(-2144272270) Call to generat
sqlnq_generate_row_permiss[650]:rc(-2144272209) no permission g
If SQL1224N results, the trap stack looks like the following:
0x00002AAAB0901BE1 sqloDumpEDU + 0x0065
0x00002AAAAD848BD3 _Z15sqldDumpContextP9sqeBsuEduiiiiiPKcPvi +
0x00fd
0x00002AAAB1204AB9 _Z15sqlrr_dump_ffdcP8sqlrr_cbii + 0x0b07
0x00002AAAB30FF0F8 _Z13sqlzeDumpFFDCP8sqeAgentjP5sqlcai + 0x0040
0x00002AAAB30FCF0E
_Z12sqlzeSqlCodeP8sqeAgentjmjP5sqlcaitP13__va_list_tag + 0x0512
0x00002AAAAEFC83C1 _Z10sqlnn_erdsiiiiiz + 0x027f
0x00002AAAAFEDAE47 address: 0x00002AAAAFEDAE47 ; dladdress:
0x00002AAAAACE1000 ; offset in lib: 0x00000000051F9E47 ;
0x00002AAAAFED8D1C _Z18sqlnq_compile_fgacP9sqlnq_qur + 0x064a
0x00002AAAB040A361 _Z9sqlns_qgsP9sqlnq_qur17sqlnq_requestTypePc
+ 0x08dd
0x00002AAAAEFD5026
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq
lrr_cmpl_enviiPP9sqlnq_qur + 0x85ea
0x00002AAAAEFCC57A
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq
lrr_cmpl_env + 0x0076 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 3 or later *
**************************************************************** |
| Local Fix: |
Drop and recreate the trigger |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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 |
Problem has been fixed in DB2 Version 10.5 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
08.05.2014
08.05.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
| 10.5.0.4
|
|
