Fixes are available
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
APAR status
Closed as fixed if next.
Error description
S4 CRM: 90251,100,838 Spanish message needs to be corrected to match with English source as follow from DB955 and DB971 shipment. When checking for the meaning of error SQL30082N RC=24 ================================================================ ==== 24 (USERNAME AND/OR PASSWORD INVALID) El nombre de usuario especificado, la contrase a especificada o ambos no son v lidos. Algunas causas espec ficas son: 1. Si recientemente ha cambiado permisos para archivos cr ticos de DB2, tales como db2ckpw, o ha migrado a un nuevo Fixpak, puede que no se haya ejecutado el mandato db2iupdt por el que se actualiza la instancia. 2. Puede que el nombre de usuario utilizado tenga un formato no v lido. Por ejemplo, en las plataformas UNIX y Linux, los nombres de usuario deben estar escritos completamente en may sculas. 3. Se puede haber producido un error al especificar la informaci n de cat logo. Por ejemplo, puede que no se haya especificado el tipo de autenticaci n correcto o, si corresponde, puede que el servidor remoto no est catalogado en el sistema local. Para obtener m s informaci n sobre la autenticaci n, consulte el Centro de informaci n de DB2 (http://publib.boulder.ibm.com/infocenter/db2luw/v9) utilizando t rminos tales como "authentication" como t rminos de b squeda. ================================================================ == When checking the error in English in the AIX Server ================================================================ == 24 (USERNAME AND/OR PASSWORD INVALID) The username specified, password specified, or both, are invalid. Some specific causes are: 1. If you have recently changed permissions on DB2 critical files such as db2ckpw or moved to a new Fixpak, the db2iupdt command which updates the instance might not have been run. 2. The username being used might be in an invalid format. For example, on UNIX and Linux platforms, usernames must be all be lowercase. 3. An error might have been made in specifying the catalog information. For example, the correct authentication type might not have been specified or, if applicable, the remote server might not have been cataloged on the local system. For more information on authentication, search the DB2 Information Center (http://publib.boulder.ibm.com/infocenter/db2luw/v9) using terms such as "authentication". =============================================================== The description on 2. is complete oposite, UNIX users need to be defined in lowercase, while in Spanish this is translate as "mayusculas" (that is uppercase. No business impact, but an error in Spanish messages.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Problem is common across all environments running this * * version of DB2. * **************************************************************** * PROBLEM DESCRIPTION: * * When checking for the meaning of error SQL30082N RC=24 * * * * ============================================================== * ==== * * 24 (USERNAME AND/OR PASSWORD INVALID) * * * * * * El nombre de usuario especificado, la contrase a * * especificada o * * ambos no son v lidos. Algunas causas espec ficas son: * * 1. Si recientemente ha cambiado permisos para archivos * * cr ticos * * de DB2, tales como db2ckpw, o ha migrado a un nuevo * * Fixpak, * * puede que no se haya ejecutado el mandato db2iupdt * * por el * * que se actualiza la instancia. * * 2. Puede que el nombre de usuario utilizado tenga un * * formato no * * v lido. Por ejemplo, en las plataformas UNIX y * * Linux, los * * nombres de usuario deben estar escritos * * completamente en * * may sculas. * * 3. Se puede haber producido un error al especificar la * * informaci n de cat logo. Por ejemplo, puede que no * * se haya * * especificado el tipo de autenticaci n correcto o, si * * corresponde, puede que el servidor remoto no est * * catalogado * * en el sistema local. Para obtener m s informaci n * * sobre la * * autenticaci n, consulte el Centro de informaci n de * * DB2 * * (http://publib.boulder.ibm.com/infocenter/db2luw/v9) * * utilizando t rminos tales como "authentication" como * * t rminos de b squeda. * * ============================================================== * == * * * * When checking the error in English in the AIX Server * * * * ============================================================== * == * * 24 (USERNAME AND/OR PASSWORD INVALID) * * * * * * The username specified, password specified, or both, * * are * * invalid. Some specific causes are: * * 1. If you have recently changed permissions on DB2 * * critical * * files such as db2ckpw or moved to a new Fixpak, the * * db2iupdt * * command which updates the instance might not have * * been run. * * 2. The username being used might be in an invalid * * format. For * * example, on UNIX and Linux platforms, usernames must * * be all * * be lowercase. * * 3. An error might have been made in specifying the * * catalog * * information. For example, the correct authentication * * type * * might not have been specified or, if applicable, the * * remote * * server might not have been cataloged on the local * * system. * * For more information on authentication, search the * * DB2 * * Information Center * * (http://publib.boulder.ibm.com/infocenter/db2luw/v9) * * using * * terms such as "authentication". * * ============================================================== * * * The description on 2. is complete oposite, UNIX users need * * to be * * defined * * in lowercase, while in Spanish this is translate as * * "mayusculas" * * (that * * is uppercase. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.5.6 * * Upgrade to DB2 version 9.7.2 * ****************************************************************
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IZ65908
Reported component name
DB2 UDB PREM SU
Reported component ID
5724I9800
Reported release
100
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-26
Closed date
2009-12-08
Last modified date
2009-12-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R100 PSN
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100"}]
Document Information
Modified date:
06 October 2021