|
Problem IT01611
|
Status: Closed |
DB2RELOCATEDB COMMAND MAY SET INCORRECT PATH FOR LOGARCHMETH1 AND LOGARCHMETH2 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2relocatedb command may set incorrect path for LOGARCHMETH1
and LOGARCHMETH2 when both are defined in the configuration
file.
$ pwd
/db1/db2inst1/sample
$ db2 create db sample on $PWD
$ mkdir -p arc1/test1 arc1/test2 arc2/test1 arc2/test2
$ db2 update db cfg for sample using logarchmeth1
disk:$PWD/arc1/test1 logarchmeth2 disk:$PWD/arc2/test1
$ db2 connect to sample ; db2 backup db sample to /dev/null
$ db2 connect to sample ; db2 get db cfg | grep LOGARCHMETH
First log archive method (LOGARCHMETH1) =
DISK:/db1/db2inst1/sample/arc1/test1/
Second log archive method (LOGARCHMETH2) =
DISK:/db1/db2inst1/sample/arc2/test1/
$ cat rel.cfg
DB_NAME=sample
DB_PATH=/db1/db2inst1/sample
INSTANCE=db2inst1
LOGARCHMETH1=DISK:/db1/db2inst1/sample/arc1/test2/
LOGARCHMETH2=DISK:/db1/db2inst1/sample/arc2/test2/
$ db2 terminate
$ db2relocatedb -f rel.cfg
Files and control structures were changed successfully.
DBT1000I The tool completed successfully.
$ db2 get db cfg | grep LOGARCHMETH
First log archive method (LOGARCHMETH1) =
DISK:/db1/db2inst1/sample/arc2/test2/
Second log archive method (LOGARCHMETH2) =
DISK:/db1/db2inst1/sample/arc2/test1/ |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using db2relocatedb command *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 10 or higher. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 9.7 Fix Pack 10. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.05.2014
01.12.2014
01.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.10
|
 |
