DB2 FOR LUW / DB2FORLUW / A50 - DB2

1.  Problem description: 
DB2 will trap with SIGSEGV with the following stack when issuing 
sql statement of "revoke role ROLE_AUTH_CONNECT from PUBLIC": 
 
  0x00007F5F7FD17205 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x0385 
  0x00007F5F7FD16E0C ossDumpStackTraceV98 + 0x002c 
  0x00007F5F7FD11F0D _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00fd 
  0x00007F5F861B5D74 sqlo_trce + 0x0404 
  0x00007F5F8620B2AA sqloEDUCodeTrapHandler + 0x027a 
  0x0000003FC180F710 address: 0x0000003FC180F710 ; dladdress: 
0x0000003FC1800000 ; offset in lib: 0x000000000000F710 ; 
  0x00007F5F86AD1D27 
_Z24sqlrlProcessRoutineAuthsP8sqlrr_cbmPhiS1_iS1_iS1_ihhbbP11sql 
r_aainfoP16aainfoRepositoryPmS6_PP20invalidated_packagesjb + 
0x19d7 
  0x00007F5F86AD3080 
_Z31sqlrlRevokeRoleFromUserOrPublicP8sqlrr_cbP10sqlr_rolesP27sql 
rlDropRoleLostTableAuthsP30sqlrlDropRoleLostSequenceAuthsP30sqlr 
lDropRoleLostVariableAuthsP29sqlrlDropRoleLostRoutineAuthsP28sql 
rlDropRoleLostModuleAuthsP12sqlrl_authidbbPbP18sqlrlPkgPrivUpdat 
eb + 0x11c0 
  0x00007F5F86AC5762 
_Z19sqlrlRolePrivilegesP8sqlrr_cbP15sqlrl_authparmsjP10sqlr_role 
sjbb + 0x0272 
  0x00007F5F86AC71D5 
_Z16sqlrlRevokeRolesP8sqlrr_cbP15sqlrl_authparmsb + 0x02c5 
  0x00007F5F83D50B6A 
_Z19sqlnq_auth_stmt_endP9sqlnq_qtbP3loc10actiontype + 0x02ba 
  0x00007F5F85F09A4D 
_Z20sqlnq_auth_role_stmtPP8stknode_i10actiontypePhP3loc + 0x013d 
  0x00007F5F8717F8D1 _Z12sqlnp_smactnP8sqlnp_cbi + 0x0a91 
  0x00007F5F83BC2FBD _Z12sqlnp_parserP8sqlnp_cb + 0x078d 
  0x00007F5F83BCAA0E 
_Z10sqlnp_mainP12sqlnq_stringbP3locPP9sqlnq_qur + 0x022e 
2.  Operating system and level: 
All platforms (Linux, AIx, zLinux, ...) of DB2 LUW 10.5 FP5 
 
3.  How to reproduce the problem: 
1). Create sample db: 
db2sampl 
2). Run these sql: 
db2 -tvf repro.sql 
3). Run these to get instance trapped (files referenced are in 
gsa: /gsa/tlbgsa/projects/d/dbtpmrs/pmrs/08805.379.000/repro): 
db2 connect to sample 
db2  -v "revoke role ROLE_AUTH_CONNECT from PUBLIC" 
revoke role ROLE_AUTH_CONNECT from PUBLIC 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL1224N  The database manager is not able to accept new 
requests, has 
terminated all requests in progress, or has terminated the 
specified request 
because of an error or a forced interrupt.  SQLSTATE=55032

DB2 WILL TRAP WITH SIGSEGV WHEN ISSUING THE SQL STATEMENT OF 
"REVOKE ROLE ROLE_AUTH_CONNECT FROM PUBLIC"

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

03.06.2015
20.01.2016
20.01.2016