Fixes are available
DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
When you ROLLFORWARD online recovery to the point-in-time on the table space, the ROLLFORWARD operation may fail in the BACKWARD phase because its process fails to re-call asynchronous log reader for next logs loading while asynchronous log reader requests to reload for split logs at end of load buffer. In the In the db2diag.log, the message "sqlptudo, probe:880, ZRC=0x00100000" is dumped. This probe point is the eye-catcher for this APAR. For example, you may get the following db2diag.log messages during Rollforward 2007-06-05-19.39.19.932950+540 E14700A422 LEVEL: Warning PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:980 MESSAGE : ADM1602W Rollforward recovery has been initiated. 2007-06-05-19.39.19.933487+540 E15123A468 LEVEL: Warning PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:1820 MESSAGE : ADM1604I DB2 is invoking the forward phase of the table space rollforward recovery. 2007-06-05-19.39.20.072233+540 I15592A476 LEVEL: Warning PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, recovery manager, sqlpForwardRecoveryTblSpace, probe:20 DATA #1 : String, 77 bytes Start LSN 00000000014C9601 Stop LSN 0000000001BAD603 Tablespace set : 4 3 2007-06-05-19.39.22.359901+540 I16069A556 LEVEL: Warning PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, recovery manager, sqlprfwdt, probe:13760 MESSAGE : Number of active or indoubt transactions for tablespace point-in-time rollforward: DATA #1 : Hexdump, 4 bytes 0x0FFFFFFFFFFEACA4 : 0000 0001 .... 2007-06-05-19.39.25.703259+540 E16626A465 LEVEL: Warning PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, data protection services, sqlufrol, probe:2670 MESSAGE : ADM1606I DB2 is invoking the backward phase of table space rollforward recovery. 2007-06-05-19.39.25.726554+540 I17092A422 LEVEL: Warning PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, data protection services, sqlptudo, probe:880 RETCODE : ZRC=0x00100000=1048576=PSM_OK, SQLT_SQLP "Unknown" 2007-06-05-19.39.25.727181+540 I17515A554 LEVEL: Error PID : 3211500 TID : 1 PROC : db2agent (TESTDB) 0 INSTANCE: dbguest1 NODE : 000 DB : TESTDB APPHDL : 0-27 APPID: *LOCAL.dbguest1.070605103919 AUTHID : DBGUEST1 FUNCTION: DB2 UDB, data protection services, sqlptudo, probe:910 RETCODE : ZRC=0x80100078=-2146434952=SQLP_TRECOVF "Recovery process failed. used by BSU only. Active cursor on drop table" DIA8131C Roll forward recovery failed, LSN was "". This is more likely to occur when the database is activated. i.e, db2 activate db DBNAME
Local fix
Reduce the records volume of a transaction to be made rollback for Rollforward point-in-time recovery.
Problem summary
see problem description
Problem conclusion
First fixed in DB2 UDB Version 9.5, FixPak 1
Temporary fix
Comments
APAR Information
APAR number
IZ08072
Reported component name
DB2 UDB ESE SOL
Reported component ID
5765F4102
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-11-06
Closed date
2008-05-30
Last modified date
2008-05-30
APAR is sysrouted FROM one or more of the following:
IZ00034
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 UDB ESE SOL
Fixed component ID
5765F4102
Applicable component levels
R910 PSY
UP
R950 PSY
UP
Document Information
Modified date:
01 October 2021