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 IC71210 Status: Closed

RESTORE USING THE TRANSPORT OPTION WILL FAIL WITH SQL2590N RC=19 DUE TO
INVALID OBJECTS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Restore using the TRANSPORT option will fail with SQL2590N rc=19 
due to invalid objects eg. a view in which one or more of the 
tables referenced in the view no longer exists. 
 
 
SQL2590N  The requested RESTORE operation cannot be completed 
because a schema 
transport error has occurred. Reason Code: "19". 
 
This also results in no object being restored.  The db2daig.log 
will show the Transport messages and a SQL -204, as the base 
table(s) will not exist when we try to create the view. 
 
db2daig.log: 
 
2010-09-09-04.25.52.739314-240 I440040A375        LEVEL: Info 
PID     : 30232582             TID  : 10854       PROC : db2sysc 
INSTANCE: mjohnson             NODE : 000         DB   : TRANSP 
EDUID   : 10854                EDUNAME: db2agent (TRANSP) 
FUNCTION: DB2 UDB, database application extension for utili, 
transport, probe:7593 
MESSAGE : Transport:Begin Replay DDL phase 
 
2010-09-09-04.25.52.955682-240 I440416A956        LEVEL: Error 
PID     : 30232582             TID  : 10854       PROC : db2sysc 
INSTANCE: mjohnson             NODE : 000         DB   : TRANSP 
EDUID   : 10854                EDUNAME: db2agent (TRANSP) 
FUNCTION: DB2 UDB, database application extension for utili, 
transport_replayFailedStatements, probe:4603 
DATA #1 : String, 70 bytes 
Transport:Error during replaying of DDL statement. Object not 
created. 
DATA #2 : String, 42 bytes 
create view hugo2v as select * from hugo2 
DATA #3 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -204   sqlerrml: 14 
 sqlerrmc: MJOHNSON.HUGO2 
 sqlerrp : SQL09072 
 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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* RESTORE USING THE TRANSPORT OPTION WILL FAIL WITH SQL2590N   * 
* RC=19                                                        * 
* DUE TO INVALID OBJECTS.                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v9.7 Fixpack 4 or higher.                         * 
****************************************************************
Local Fix:
WORKAROUND: 
 
Set the AUTO_REVAL to DEFERRED_FORCE before starting the restore 
TRANSPORT: 
db2 update db cfg for transp using AUTO_REVAL DEFERRED_FORCE
available fix packs:
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

Solution
First fixed in DB2 v9.7 Fixpack 4 or higher.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73120 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.09.2010
09.05.2011
09.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.