Error SQL30082N Reason Code 15 or 24 or 36

Technote (troubleshooting)


Problem(Abstract)

When trying to connect to a database or run any db2 commands I'm receiving one or both of the following errors:

Symptom

SQL30082N Security processing failed with Reason Code 15
"Security processing at the server failed "

Or

SQL30082N Security processing failed with Reason Code 24
"USERNAME AND/OR PASSWORD INVALID "

OR


SQL30082N Security processing failed with reason "36" ("UNEXPECTED
CLIENT ERROR"). SQLSTATE=08001

The following message may also be seen in the db2diag.log:
secGetGroups failed with rc = -2146499506



Resolving the problem

Perform the following steps to resolve this issue:

1.) Please make sure your user id used to connect to the database is following the naming rules for DB2:


User, user ID and group naming rules

Objects
Guidelines
  • Group names
  • User names
  • User IDs
  • Group names must be less than or equal to the group name length listed in SQL and XML limits.
  • User IDs on Linux and UNIX operating systems can contain up to 8 characters.
  • User names on Windows can contain up to 30 characters.
  • When not using Client authentication, non-Windows 32-bit clients connecting to Windows with user names longer than the user name length listed in SQL and XML limits are supported when the user name and password are specified explicitly.
  • Names and IDs cannot:
  • Be USERS, ADMINS, GUESTS, PUBLIC, LOCAL or any SQL reserved word
  • Begin with IBM, SQL or SYS.

If the user id in question is following the correct naming rules listed above, and the error is still occurring please follow the below steps:

2.) Check the permission's on the following files in the instance ~/sqllib/security/ directory:

ls -l /usr/db2inst1/sqllib/security
-r-s--x--x 1 root db2inst1 20374 Apr 14 2008 db2ckpw*
-r-s--x--x 1 root db2inst1 14387 Apr 14 2008 db2chpw*

3.) Stop the instance by running:

  • db2stop

4.) Log in as a user id that has root authority.

5.) Issue the following command to update the instance:

  • DB2DIR/instance/db2iupdt InstanceName

where

DB2DIR/instance directory, where DB2DIR is the location where the current version of the DB2 database product is installed.

InstanceName put the name of your instance you want to update.

6.) Then start the instance by running:

  • db2start

Then try to reproduce the SQL30082 error, if you still see the error please proceed onto the next step:

7.) Make sure the catalog information on the client is correct.

8.) Please try restarting the nscd daemon if you are on Linux or Unix:
    The nscd daemon is a caching daemon which is found under the /etc/init.d/. It provides caching services for hosts,passwd,group,ipnodes databases using various nameservice lookups like hosts file, DNS, NIS,NIS+ and more.

    To stop and start this demon you must be root:

    /etc/init.d/nscd stop
    Stopping nscd: /usr/sbin/nscd: Only root is allowed to use this option! [FAILED]

    Ran as root:

    /etc/init.d/nscd stop
    Stopping nscd: [ OK ]

    /etc/init.d/nscd start
    Starting nscd: [ OK ]

9.) If you are getting SQL30082 rc=15 and using an encryption algorithms please see the following tech doc:

SQL30082 RC=24 or RC=15 returned when connecting to database on Server when pwd_algorithm is Crypt, MD5, SHA1, SHA256, SHA512, Blowfish



For further discussion on this topic, visit this developerWorks forum thread:
https://www.ibm.com/developerworks/community/forums/html/topic?id=6de76b51-351d-4dec-a77f-f96d18e30e20

Related information

SQL30082N
Common DB2 Connect problems
db2iupdt - Update instances command
User ID and group naming rules

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

9.5, 9.7

Operating system(s):

AIX, HP-UX, Linux, Solaris

Software edition:

Enterprise Server, Personal, Workgroup Server

Reference #:

1416382

Modified date:

2013-06-13

Translate my page

Machine Translation

Content navigation