APAR status
Closed as program error.
Error description
When using the db2rbind tool to rebind DB2 packages it may fail with a "Memory Fault" violation, possibly producing a coredump file as well. . This fails on the Linux 32-bit platform. A call stack from the coredump file would like like this: . (gdb) where #0 0x0804c354 in revalidate_package(char*, sqlosfh**, int, int, short*, int*, int*, int*) () at eval.c:41 #1 0x202e646e in ?? () at eval.c:41 Error accessing memory address 0x69626572: No such process.
Local fix
When using "db2rbind" if possible run it from a 64-bit instance, as the problem is not likely to happen with the 64-bit version of the tool.
Problem summary
Users Affected: Users issuing db2rbind command on Linux 32-bit systems. Problem Description: db2rbind may fail with a memory fault error, and possibly producing a core file if executed on a Linux 32-bit instance.
Problem conclusion
First fixed in DB2 UDB Version 8, FixPak 17
Temporary fix
Use a 64-bit instance to issue db2rbind instead.
Comments
APAR Information
APAR number
LI73005
Reported component name
DB2 UDB WSUE LI
Reported component ID
5765F4304
Reported release
820
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-01-10
Closed date
2008-09-23
Last modified date
2008-09-23
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 UDB WSUE LI
Fixed component ID
5765F4304
Applicable component levels
R820 PSN
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
23 September 2008