DB2 FOR LUW / DB2FORLUW / 970 - DB2

Starting with DB2 Version 9.7 Fix Pack 2, table spaces and SQL 
schemas can be restored as a set from one database to another 
using transportable sets. 
 
By using the RESTORE command with the TRANSPORT option, you can 
restore data in a set of table spaces from a backup image 
into another existing database. 
You can re-create database objects in the SQL schemas that 
reference the data in the restored table spaces. 
The restored table spaces and SQL schemas can function as part 
of the new database. 
 
But there is currently a restriction for system-created 
tablespaces like SYSCATSPACE and USERSPACE1. 
We might lower this restriction in later releases. 
 
 
Currently the following command example will return success: 
 
db2 "RESTORE DB source TABLESPACE (userspace1) SCHEMA (db2v973) 
from /tmp TRANSPORT INTO target" 
 
But it was not successful. 
 
db2diag.log shows: 
 
2010-11-12-13.57.34.036512+060 I148734E1080        LEVEL: Error 
PID     : 2843                 TID  : 140710376368464PROC : 
db2sysc 0 
INSTANCE: db2v973              NODE : 000          DB   : TARGET 
APPHDL  : 0-180                APPID: 
*LOCAL.db2v973.101112125716 
AUTHID  : DB2V973 
EDUID   : 337                  EDUNAME: db2agent (TARGET) 0 
FUNCTION: DB2 UDB, database application extension for utili, 
transport_replayFailedStatements, probe:4604 
DATA #1 : String, 70 bytes 
Transport:Error during replaying of DDL statement. Object not 
created. 
DATA #2 : String, 76 bytes 
 
CREATE TABLE "DB2V973 "."T1"  ( 
                  "F1" INTEGER ) 
                 IN "USERSPACE1" 
DATA #3 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -204   sqlerrml: 10 
 sqlerrmc: USERSPACE1 
 sqlerrp : SQL09073 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 4270 
 
 
This APAR is to avoid that a user can issue a SCHEMA TRANSPORT 
against system-created tablespaces. 
 
Documentation will also be updated accordingly.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP4 or Subsequent Fix Pack                * 
****************************************************************

n/a

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem First Fixed in DB2 Version 9.8 Fix Pack 3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.12.2010
14.12.2012
14.12.2012

9.7.FP4,
9.8.FP3