suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT23052 Status: Closed

RESTORE TRANSPORT MAY RESULT IN SQL0601N

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Running restore transport might fail when the partition group of 
the tablespaces to be transported and the partition group in 
which the tablespace will be imported have the same name: 
 
db2 " 
restore db JKL tablespace(JKL#DBD, JKL#DBI) 
schema(SAPJKLDB) from /backup2/JKL 
taken at 20170913091230 
transport into JKL" 
 
SQL0601N  The name of the object to be created is identical to 
the existing 
name "SAPNODEGRP_MKL" of type "DATABASE PARTITION GROUP". 
SQLSTATE=42710
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fixpack 3.                         * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
See Problem Description above.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.11.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)