DB2 - Problem description
Problem IC95218 | Status: Closed |
DB2RELOCATEDB CAN FAIL WITH DBT1015N WHEN CHANGING STORAGE_PATH | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When db2relocatedb is issued to change the DB_PATH without changing STORAGE_PATH, it succeeds with no error. However, subsequent db2relocatedb command to change STORAGE_PATH fails with DBT1015N. Here is the repro steps: $ db2 create db p36705 on $PWD/src $ db2 terminate ; db2stop $ cat rel.cfg INSTANCE=v95fp5 DB_NAME=P36705 DB_PATH=/dbpath/36705/src,/dbpath/36705/des $ cp -pr src des $ db2relocatedb -f rel.cfg Files and control structures were changed successfully. Database was catalogued successfully. DBT1000I The tool completed successfully. $ db2 terminate ; db2start $ db2 connect to p36705 $ db2 list tablespaces ... Tablespace ID = 1 Name = TEMPSPACE1 Type = System managed space Contents = System Temporary data State = 0x4000 <<< tablespace is offline Detailed explanation: Offline ... $ db2 terminate ; db2stop $ cat rel2.cfg INSTANCE=v95fp5 DB_NAME=P36705 DB_PATH=/dbpath/36705/des STORAGE_PATH=/dbpath/36705/src,/dbpath/36705/des $ db2relocatedb -f rel2.cfg DBT1015N Unable to allocate memory. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using db2relocatedb * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 3. * **************************************************************** | |
Local Fix: | |
Change DB_PATH and STORAGE_PATH at the same time. | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First 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 10.03.2014 10.03.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 |