|
Problem IC76236
|
Status: Geschlossen |
ACTIVATION OF THE TRANSPORTABLE SCHEMA FEATURE ON A DATABASE WIT H NON-CONSECUTIVE TABLESPACE NUMBERS MIGHT CAUSE SQL2590N RC=17S |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
The result of the "db2 restore database .... transport " would
be :
SQL2590N The requested RESTORE operation cannot be completed
because a schema
transport error has occurred. Reason Code: "17".
and in db2diag.log would show up messages :
2011-04-19-15.56.09.595217-240 I6724E480 LEVEL: Warning
PID : 24311 TID : 47772069783872PROC :
db2sysc
INSTANCE: dmitryh NODE : 000
EDUID : 1703 EDUNAME: db2bm.1441.0 (STAGEDB)
FUNCTION: DB2 UDB, database utilities,
sqludSetTransportStagingDBInfo, probe:6700
MESSAGE : WARNING: Cannot find matching tablespace on staging
database for a
reserved tablespace on target database.
DATA #1 : String, 5 bytes
TBSP1
and
2011-04-19-15.56.17.580009-240 I27478E837 LEVEL: Error
PID : 24311 TID : 47772497602880PROC :
db2sysc
INSTANCE: dmitryh NODE : 000 DB : STAGEDB
APPHDL : 0-221 APPID:
*LOCAL.dmitryh.110419195616
AUTHID : DMITRYH
EDUID : 1709 EDUNAME: db2agent (STAGEDB)
FUNCTION: DB2 UDB, database utilities,
sqludPrepareDDLForTransport, probe:1259
MESSAGE :
ZRC=0x80B00475=-2135948171=SQLUD_TRANSPORT_TABLESPACE_MAP_ERROR
"An error occurred when mapping table spaces names or
IDs between those of staging database and of target database.
Schema transport stopped."
DATA #1 : String, 74 bytes
ERROR: restore client provides an invalid staging database table
space ID.
DATA #2 : String, 5 bytes
TBSP1
DATA #3 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes
65535 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* The result of the "db2 restore database .... transport " *
* would be : *
* SQL2590N The requested RESTORE operation cannot be *
* completed because a schema *
* transport error has occurred. Reason Code: "17". *
* *
* and in db2diag.log would show up messages : *
* 2011-04-19-15.56.09.595217-240 I6724E480 LEVEL: *
* Warning *
* PID : 24311 TID : 47772069783872PROC : *
* db2sysc *
* INSTANCE: dmitryh NODE : 000 *
* EDUID : 1703 EDUNAME: db2bm.1441.0 (STAGEDB) *
* FUNCTION: DB2 UDB, database utilities, *
* sqludSetTransportStagingDBInfo, probe:6700 *
* MESSAGE : WARNING: Cannot find matching tablespace on *
* staging database for a *
* reserved tablespace on target database. *
* DATA #1 : String, 5 bytes *
* TBSP1 *
* and *
* *
* 2011-04-19-15.56.17.580009-240 I27478E837 LEVEL: *
* Error *
* PID : 24311 TID : 47772497602880PROC : *
* db2sysc *
* INSTANCE: dmitryh NODE : 000 DB : *
* STAGEDB *
* APPHDL : 0-221 APPID: *
* *LOCAL.dmitryh.110419195616 *
* AUTHID : DMITRYH *
* EDUID : 1709 EDUNAME: db2agent (STAGEDB) *
* FUNCTION: DB2 UDB, database utilities, *
* sqludPrepareDDLForTransport, probe:1259 *
* MESSAGE : *
* ZRC=0x80B00475=-2135948171=SQLUD_TRANSPORT_TABLESPACE_MAP_ER *
* ROR *
* "An error occurred when mapping table spaces names *
* or IDs between those of staging database and of target *
* database. Schema transport stopped." *
* DATA #1 : String, 74 bytes *
* ERROR: restore client provides an invalid staging database *
* table space ID. *
* DATA #2 : String, 5 bytes *
* TBSP1 *
* DATA #3 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes *
* 65535 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V97FP5 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
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
|
| Lösung |
DB2 V97FP5 would contain a fix |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 06.05.2011
01.02.2012
01.02.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
