Home

Latest versions	fixlist
11.1.0.7
10.5.0.9
10.1.0.6
9.8.0.5
9.7.0.11
9.5.0.10
9.1.0.12

Have problems? - contact us.
Register for free
Contact form

DB2 - Problem description

Problem IC64022	Status: Closed
ROLLFORWARD AFTER A RESTORE WITH LOAD COPY FAILS WHEN PROCESSING LOAD FILE.THIS HAPPENS WHEN DB2LOADREC IS POINTING T0 EMPTY FILE
product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Problem Description: RF after restore with load copy fails when trying to process load copy file. Entries in db2diag.log look like the following: 2008-09-08-15.57.08.878811-240 I1825398E392 LEVEL: Warning PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, database utilities, sqludcpy, probe:1128 MESSAGE : Load copy restore terminated. 2008-09-08-15.57.08.879032-240 E1825791E429 LEVEL: Warning PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : Sample APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:8180 MESSAGE : ADM1611W The rollforward recovery phase has been completed. 2008-09-08-15.57.09.323714-240 E1826221E418 LEVEL: Warning PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:980 MESSAGE : ADM1602W Rollforward recovery has been initiated. ......... 2008-09-08-15.57.38.331618-240 E1852238E418 LEVEL: Warning PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:980 MESSAGE : ADM1602W Rollforward recovery has been initiated. 2008-09-08-15.57.38.331800-240 I1852657E446 LEVEL: Severe PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, database utilities, sqludcpy, probe:491 MESSAGE : DIA0001E An internal error occurred. Report the following error code : "". ....... 2008-09-08-15.57.38.334580-240 I1874155E419 LEVEL: Warning PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, database utilities, sqludcpy, probe:906 MESSAGE : Terminating EDUs - load copy restore terminated by caller 2008-09-08-15.57.38.334674-240 I1874575E387 LEVEL: Warning PID : 31378 TID : 183046802080PROC : db2agent (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, database utilities, sqludcpy, probe:914 MESSAGE : Load copy restore failed. ............. 2008-09-08-15.57.38.347673-240 I1875774E416 LEVEL: Warning PID : 10577 TID : 183046802080PROC : db2redom (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, recovery manager, sqlpRFWppl, probe:870 MESSAGE : Tablespaces taken offline due to failed load recovery. 2008-09-08-15.57.38.348534-240 I1876191E415 LEVEL: Warning PID : 10577 TID : 183046802080PROC : db2redom (ADAENG) 0 INSTANCE: test NODE : 000 DB : SAMPLE APPHDL : 0-912 APPID: *LOCAL.nytit024.080908195325 AUTHID : MSDB2 FUNCTION: DB2 UDB, recovery manager, sqlpRFWppl, probe:870 DATA #1 : <preformatted> Tablespace 5 in restore pending state. =============================================== The reason of the issue is because DB2LOADREC points to an empty file. Found in db2 v9.1 fp5
Problem Summary:
ROLLFORWARD AFTER A RESTORE WITH LOAD COPY FAILS WHEN PROCESSING LOAD FILE.THIS HAPPENS WHEN DB2LOADREC IS POINTING T0 EMPTY FILE
Local Fix:
The workaround is to unset DB2LOADREC.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows 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 7 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
Solution
Fixed in DB2 V9.7 FP1
Workaround
not known / see Local fix
Timestamps
Date - problem reported : Date - problem closed : Date - last modified :	22.10.2009 10.03.2010 10.03.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1