DB2 - Problem description
Problem IT03675 | Status: Closed |
DB2EXMIG DOES NOT PRESERVE PERMISSIONS ON RECREATED TABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
It is expected that the migrated explain tables are usable by the same users before/after the db2exmig, but that doesn't happen on 10.5 . After upgrading a database to v10.5 FP3 there are new/recreated function and tables from the db2exmig output however the permission granted to tables that existed before the migration are lost. Looking at the permissions before/after the db2exmig (using the db2look tool) no permissions are granted to the tables before the migration. Example: $ db2look -d test -x -a -- Generate statistics for all creators -- This CLP file was created using DB2LOOK Version "10.5" -- Timestamp: Mon Jul 28 15:14:50 EDT 2014 -- Database Name: TEST -- Database Manager Version: DB2/AIX64 Version 10.5.3 -- Database Codepage: 1208 -- Database Collating Sequence is: SYSTEM_819 -- Alternate collating sequence(alt_collate): null -- varchar2 compatibility(varchar2_compat): OFF -- Binding package automatically ... -- Bind is successful -- Binding package automatically ... -- Bind is successful CONNECT TO TEST; -------------------------------------------- -- Authorization Statements on Tables/Views -------------------------------------------- GRANT SELECT ON TABLE "DB2INST "."EXPLAIN_PREDICATE" TO USER "TEST " ; COMMIT WORK; CONNECT RESET; TERMINATE; $ db2exmig -d test -e DB2INST DB2 Universal Database Version 10.5, 5622-044 (c) Copyright IBM Corp. 1999, 2012 Licensed Material - Program Property of IBM IBM DATABASE 2 Explain Table Migration Tool Connecting to the Database. Connect to Database Successful. Binding package - Bind was Successful Migrating Explain Tables from v9.7FP1 or later to current release. Examining the columns for table DB2INST.EXPLAIN_INSTANCE Found table DB2INST.EXPLAIN_STATEMENT. No changes required for this migration. Found table DB2INST.EXPLAIN_ARGUMENT. No changes required for this migration. Examining the columns for table DB2INST.EXPLAIN_OBJECT Found table DB2INST.EXPLAIN_OPERATOR. No changes required for this migration. Examining the columns for table DB2INST.EXPLAIN_PREDICATE Found table DB2INST.EXPLAIN_STREAM. No changes required for this migration. Found table DB2INST.EXPLAIN_DIAGNOSTIC. No changes required for this migration. Found table DB2INST.EXPLAIN_DIAGNOSTIC_DATA. No changes required for this migration. Found table DB2INST.EXPLAIN_ACTUALS. No changes required for this migration. Found table DB2INST.ADVISE_INSTANCE. No changes required for this migration. Examining the columns for table DB2INST.ADVISE_INDEX Found table DB2INST.ADVISE_WORKLOAD. No changes required for this migration. Found table DB2INST.ADVISE_MQT. No changes required for this migration. Found table DB2INST.ADVISE_PARTITION. No changes required for this migration. Found table DB2INST.ADVISE_TABLE. No changes required for this migration. Found all tables OK. Start migration. Old tables renamed...begin creating new explain tables. Altering Explain table DB2INST.EXPLAIN_INSTANCE Altering Explain table DB2INST.EXPLAIN_OBJECT Creating Explain table DB2INST.EXPLAIN_PREDICATE Creating Explain table DB2INST.EXPLAIN_PREDICATE with NOT LOGGED INITIALLY Creating Explain table DB2INST.OBJECT_METRICS (New) Altering Explain table DB2INST.ADVISE_INDEX begin insert into tables. Copying to Explain table EXPLAIN_PREDICATE from EMPRD_001406574918 Check all tables where copied properly. All tables confirmed to have been copied properly. Dropping old Explain table EMPRD_001406574918(EXPLAIN_PREDICATE) Dropped old Explain function DB2INST.EXPLAIN_GET_MSGS. Created new Explain function DB2INST.EXPLAIN_GET_MSGS. Migration of the explain tables to Version 10.05.3 format has succeeded. ******** WARNING ********** Because the 'NOT LOGGED INITIALLY' option was used in migrating the explain tables it is recommended that a backup of the explain tables be taken as soon as possible, if your backup procedures include the backing up of the explain tables. ******** WARNING ********** $ db2look -d test -x -a -- Generate statistics for all creators -- This CLP file was created using DB2LOOK Version "10.5" -- Timestamp: Mon Jul 28 15:15:31 EDT 2014 -- Database Name: TEST -- Database Manager Version: DB2/AIX64 Version 10.5.3 -- Database Codepage: 1208 -- Database Collating Sequence is: SYSTEM_819 -- Alternate collating sequence(alt_collate): null -- varchar2 compatibility(varchar2_compat): OFF CONNECT TO TEST; COMMIT WORK; CONNECT RESET; TERMINATE; | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users running on DB2 10.5 before Fix Pack 5 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 5 or later. * **************************************************************** | |
Local Fix: | |
Backup permissions using db2look before running the db2exmig tool and grant it back after running it. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.08.2014 31.03.2015 31.03.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.5 |