home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT00940 Status: Closed

DATABASE SCHEMA TRANSPORT FAILS ON LINUX390 WITH SQL0293N ERROR ACCESSING A
TABLE SPACE CONTAINER.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Transport expects the block size for a DMS tablespace to be 512 
but this generally mismatches the block size on disk.  In this 
case db2 will not allow users to create a tablespace that does 
not use file system cashing.  Transport ignores this and when it 
tries to perform an unaligned read it fails and does not update 
the tablespace container flags. This leads to BPS reporting that 
the container does not belong to the current database and sets 
the tablespace as inaccessible. 
 
Here is how to reproduce on Linux390: 
 
db2 create db IBMblue 
db2 create db IBMred 
db2 update db cfg for IBMblue using logarchmeth1 
disk:/home/dbguest9/IBM_blue_logarch 
db2 update db cfg for IBMred using logarchmeth1 
disk:/home/dbguest9/IBM_red_logarch 
db2 backup db IBMblue to /home/dbguest9 
db2 backup db IBMred to /home/dbguest9 
db2 connect to IBMblue 
db2 create tablespace ts1 
db2 create schema schema1 
db2 "create table schema1.table1(c1 int, c2 varchar(256)) in 
ts1" 
db2 "insert into schema1.table1(c1,c2) 
values(1,'blue'),(2,'green'),(3,'red'),(4,'yellow')" 
db2 terminate 
db2 backup db IBMblue online include logs 
db2 "restore db IBMblue tablespace (ts1) schema(schema1) 
transport into IBMred LOGTARGET /home/dbguest9/IBM_red_logarch" 
SQL0293N  Error accessing a table space container. 
SQLSTATE=57048 
 
Messages you will see in the db2diag.log: 
 
2014-04-08-14.31.23.870565-240 I1144973A929         LEVEL: Error 
PID     : 2091                 TID : 2199074781936  PROC : db2bp 
INSTANCE: dbguest9             NODE : 000           DB   : RED 
 
APPID   : *LOCAL.dbguest9.140408183103 
HOSTNAME: fragola 
FUNCTION: DB2 UDB, database utilities, 
sqludTransportSetupTargetDB, probe:1381 
MESSAGE : 
ZRC=0x80B00475=-2135948171=SQLUD_TRANSPORT_TARGETDB_ERROR 
          "An error occurred on target database while 
transporting table spaces.  Schema transport stopped." 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -293   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL10012 
 sqlerrd : (1) 0x8402001E      (2) 0x0000001E      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 57048 
 
2014-04-08-14.31.23.870719-240 E1145903A918         LEVEL: 
Severe 
PID     : 2091                 TID : 2199074781936  PROC : db2bp 
INSTANCE: dbguest9             NODE : 000           DB   : RED 
 
APPID   : *LOCAL.dbguest9.140408183103 
HOSTNAME: fragola 
FUNCTION: DB2 UDB, database utilities, 
sqludTransportSetupTargetDB, probe:1395 
MESSAGE : ZRC=0xFFFFFEDB=-293 
          SQL0293N  Error accessing a table space container.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 5.                              * 
****************************************************************
Local Fix:
N/A
Solution
First fixed in DB2 10.1 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.04.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList