Fixes are available
DB2 Version 9.1 Fix Pack 7 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
The following trap will occur when connecting to the database if the encrypted password contained in /etc/shadow file is corrupted. For example, if the encrypted password within /etc/shadow has a $ in the salt. <StackTrace> ##### Object: /lib/libc.so.1 strlen(0xffbfe251,0xffbfe1d8,0x0,0xffffffff,0x8001,0x0) + 0x50 ##### Object: /u02/db2ptx02/sqllib/adm/db2syscr sqlo_validate_pwd(0xffbfe251,0xffbfe1d8,0x0,0xffffffff,0x8001,0x 0) + 0xdc __1cVsqlockpw_daemon_check6Fpkc1pi_i_(0x1,0x0,0x0,0x10028040,0x0 ,0x870f0 000) + 0x4f4 __1cUsqlockpw_daemon_init6F_i_(0x2775400,0x41,0x0,0x10028040,0x1 0028040, 0x1ffd400) + 0x290 sqloRunInstance(0x1f7e04,0x28159ec,0x0,0x0,0x3800,0x272e180) + 0x6e8 DB2main(0x0,0xffbffb44,0xfffff7ff,0x200,0x10029440,0x0) + 0x7ac main(0x1,0xffbffb44,0xffbffb4c,0x26eec00,0xfe0603c0,0x0) + 0x8 _start(0x0,0x0,0x0,0x0,0x0,0x0) + 0x108 </StackTrace>
Local fix
Ensure the /etc/shadow file is valid.
Problem summary
The following trap will occur when connecting to the database if the encrypted password contained in /etc/shadow file is corrupted. For example, if the encrypted password within /etc/shadow has a $ in the salt. <StackTrace> ##### Object: /lib/libc.so.1 strlen(0xffbfe251,0xffbfe1d8,0x0,0xffffffff,0x8001,0x0) + 0x50 ##### Object: /u02/db2ptx02/sqllib/adm/db2syscr sqlo_validate_pwd(0xffbfe251,0xffbfe1d8,0x0,0xffffffff,0x8001,0x 0) + 0xdc __1cVsqlockpw_daemon_check6Fpkc1pi_i_(0x1,0x0,0x0,0x10028040,0x0 ,0x870f0 000) + 0x4f4 __1cUsqlockpw_daemon_init6F_i_(0x2775400,0x41,0x0,0x10028040,0x1 0028040, 0x1ffd400) + 0x290 sqloRunInstance(0x1f7e04,0x28159ec,0x0,0x0,0x3800,0x272e180) + 0x6e8 DB2main(0x0,0xffbffb44,0xfffff7ff,0x200,0x10029440,0x0) + 0x7ac main(0x1,0xffbffb44,0xffbffb4c,0x26eec00,0xfe0603c0,0x0) + 0x8 _start(0x0,0x0,0x0,0x0,0x0,0x0) + 0x108 </StackTrace>
Problem conclusion
First fixed in DB2 UDB Version 9.1, FixPak 7
Temporary fix
Comments
APAR Information
APAR number
IZ39511
Reported component name
DB2 UDB ESE SOL
Reported component ID
5765F4102
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-08
Closed date
2009-04-17
Last modified date
2009-04-17
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 ESE SOL
Fixed component ID
5765F4102
Applicable component levels
R910 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":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
17 April 2009