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
When connecting to the database from the DB2 CLP with a password longer than 8 characters the following behavior will occur. $ db2 connect to SAMPLE user db2inst1 using 123456789 Database Connection Information Database server = DB2/HP64 9.1.3 SQL authorization ID = db2inst1 Local database alias = SAMPLE $ db2 connect to SAMPLE user db2inst1 Enter current password for db2inst1: SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 This is due to the HP-UX API getpass() which only reads up to a maximum of 8 characters. The DB2 behavior will be changed to read more than 8 characters for password entry. If DB2 operating-system security plugins are used, the operating system determines the valid password length. If DB2 LDAP security plugins are used, the LDAP server determines the valid password length.
Local fix
Problem summary
When connecting to the database from the DB2 CLP with a password longer than 8 characters the following behavior will occur. $ db2 connect to SAMPLE user db2inst1 using 123456789 Database Connection Information Database server = DB2/HP64 9.1.3 SQL authorization ID = db2inst1 Local database alias = SAMPLE $ db2 connect to SAMPLE user db2inst1 Enter current password for db2inst1: SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 This is due to the HP-UX API getpass() which only reads up to a maximum of 8 characters. The DB2 behavior will be changed to read more than 8 characters for password entry. If DB2 operating-system security plugins are used, the operating system determines the valid password length. If DB2 LDAP security plugins are used, the LDAP server determines the valid password length.
Problem conclusion
First fixed in DB2 UDB Version 9.1, FixPak 7
Temporary fix
Comments
APAR Information
APAR number
IZ39035
Reported component name
DB2 UDB ESE HP-
Reported component ID
5765F4103
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-02
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 HP-
Fixed component ID
5765F4103
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