Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as program error.
Error description
If there was communication problem, such as SQL1229N, between the catalog node and a remote node which resides on a different physical machine than the catalog node, then in some cases the crash recovery on the remote node may fail with SQL1471N. In db2diag.log, the probe point "sqlpLogSync, probe:100" could be seen. For example, 2007-02-01-14.03.36.501553-300 I35252E285 LEVEL: Error PID : 14114 TID : 183041116640PROC : db2fcmr 12 INSTANCE: nytxt190 NODE : 012 FUNCTION: DB2 UDB, fast comm manager, sqkfRecvConduit::HandleAuthentEvent, probe:95 MESSAGE : Re-conn n:3; ls:1 data protection services, sqlpLogSync, probe:100 MESSAGE : Mismatch of record (19, 1170207457) from node 9 with record (15, 1170120694) on catalog node 1 or 2007-02-01-14.03.48.872692-300 I69837E449 LEVEL: Error PID : 19418 TID : 183041116640PROC : db2agntp (ADMIN) 1 INSTANCE: nytxt190 NODE : 001 APPHDL : 1-61 APPID: *N1.nytxt190.070201190352 AUTHID : MSDB2 FUNCTION: DB2 UDB, data protection services, sqlpLogSync, probe:100 MESSAGE : Mismatch of record (19, 1170207476) from node 15 with record (15, 1170120939) on catalog node 1 One way to avoid this problem is to put all the paritions in one physical manchine only, if that is acceptable
Local fix
There is no local fix for the issue, except, DB2 support team could be contacted for necessary patching.
Problem summary
Users affected: Users using multipartition environment as described in the APAR Problem Description: Please see the APAR details Problem Summary: CRASH RECOVERY MAY FAIL WITH SQL1471N WHEN THERE WAS COMMUNICATION PROBLEM BETWEEN THE CATALOG NODE AND A REMOTE NODE
Problem conclusion
First fixed in DB2 UDB Version V9.1, FixPak 5 (CQ defect#wsdbu00120579)
Temporary fix
Comments
APAR Information
APAR number
IY94721
Reported component name
DB2 DPF
Reported component ID
5724N7400
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-02-11
Closed date
2008-07-09
Last modified date
2008-07-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 DPF
Fixed component ID
5724N7400
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
09 July 2008