DB2 - Problem description
Problem IC69049 | Status: Closed |
DB2LOGMGR EDU CRASH IN SPRINTF CALLED FROM SQLPGRETRIEVELOGDISK ON HADR STANDBY REINTEGRATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
When both LOGARCHMETH1 and/or LOGARCHMETH2/FAILARCHPATH are set, a standby server will attempt to search each location for a later version of the log file after seeing this message in the db2diag.log : FUNCTION: DB2 UDB, recovery manager, sqlplfrFMOpenLog, probe:600 MESSAGE : Extent 203822 in log path may be stale. Trying archive. It's possible that after searching the 1st location ( pointed to by LOGARCHMETH1 ), the retrieve request used by the db2logmgr gets freed. This then can potentially lead to a crash in the db2logmgr edu upon trying the 2nd location ( e.g. pointed to by FAILARCHPATH ). A trap file may show the following list of functions : strlen _doprnt sprintf sqlpgRetrieveLogDisk sqlpgRetrieveLogFile sqlpgHandleLogMgrPost ... | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Environment using HADR * **************************************************************** * PROBLEM DESCRIPTION: * * A standby database server may abend in the db2logmgr * * eduunder specific circumstances, detailed in the * * apardescription. * **************************************************************** * RECOMMENDATION: * * Upgrade the database server to V9.5 Fixpak 7 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
This problem was first fixed in V9.5 Fixpak 7 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC70590 IC70591 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.06.2010 15.11.2010 15.11.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.7 | |
9.5.0.7 |