DB2 - Problem description
Problem IC88627 | Status: Closed |
ADMIN_MOVE_TABLE() MAY FAIL WITH SQL0567N IF A TABLE HAS "PUBLIC" PRIVILEGE GRANTED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If a table has the PUBLIC privilege granted then an ADMIN_MOVE_TABLE() may fail during SWAP phase with SQL0567N. For examle, suppose table T1 has the following authorization: GRANT SELECT ON TABLE "MYSCHEMA"."T1" TO PUBLIC ; Then ADMIN_MOVE_TABLE() might fail: CALL SYSPROC.ADMIN_MOVE_TABLE( 'MYSCHEMA', 'T1', 'TABLESPACEA', 'TABLESPACEB', 'TABLESPACEA', '', '', '', '','','SWAP' ) STAGING : T1xyz STATUS : REPLAY TARGET : QCM8T1 VERSION : 09.07.0005 ADMIN_MOVE_TABLE - SWAP step aborted. SQL0567N The operation failed because the specified authorization name does not meet the identifier naming rules. Authorization name: "PUBLIC". SQLSTATE=42602 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 2. * **************************************************************** | |
Local Fix: | |
Revoke the SELECT privilege on the source table to the PUBLIC group before the SWAP, and then after the SWAP is finished successfully, set the privilege back from the command line immediately, i.e.: db2 revoke SELECT ON TABLE "MYSCHEMA"."T1" from public db2 "CALL SYSPROC.ADMIN_MOVE_TABLE( 'MYSCHEMA', 'T1', 'TABLESPACEA', 'TABLESPACEB', 'TABLESPACEA', '', '', '', '','','SWAP' )" db2 grant SELECT ON TABLE "MYSCHEMA"."T1" to public | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 10.1 Fix Pack 2. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.11.2012 10.01.2013 10.01.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |