|
Problem IT35061
|
Status: Closed |
WHEN A USER ID WITH INSUFFICIENT PRIVILEGE ATTEMPTS TO RUN REORGFROM WITHIN A STORED PROCEDURE, THE STORED PROCEDURE RETURNS RC
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
When the same user attempts to execute runstats from within the
store procedure, it correctly returns an error.
repro steps:
---------------
db2 "create procedure jchwong.test3() begin declare reorg_str
varchar(500); set reorg_str = 'REORG TABLE DB2INST1.EMPLOYEE';
call sysproc.admin_cmd(reorg_str); commit; end--;"
db2 "call jchwong.test3()"
Return Status = 0
The same test for runstats generates expected results (i.e.
error):
db2 "create procedure jchwong.test2() begin declare runstats_str
varchar(500); set runstats_str = 'RUNSTATS ON TABLE
DB2INST1.EMPLOYEE'; call sysproc.admin_cmd(runstats_str);
commit; end--;"
db2 "call jchwong.test2()"
SQL2311N The user does not have the authority to run the
RUNSTATS utility on
table "DB2INST1.EMPLOYEE ". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 version 11.5.6.0 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 version 11.5.6.0 *
**************************************************************** |
| Comment |
First fixed in Db2 version 11.5.6.0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.11.2020
21.06.2021
21.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
