SQL30082N - reason code 24 UDB Linux

Dawn Kastelic

SQL30082N - reason code 24 UDB Linux
I am running DB2 V 8.1.6 on Linux. I have 2 instances with several
databases catalogued on each instance.
I am able to connect to a database using the following:

chln088|/home/lidxpbb> db2 connect to sasite

Database Connection Information

Database server = DB2/LINUX 8.1.6
SQL authorization ID = LIDXPBB
Local database alias = SASITE

When I try to connect with the user and password, I get the following:

chln088|/home/lidxpbb> db2 connect to sasite user lidxpbb
Enter current password for lidxpbb:
SQL30082N Attempt to establish connection failed with security reason
"24"
("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

I am able to connect with the user and password while using the instance
owner:

chln088|/home/lidxpbb> db2 connect to sasite user db2inst8
Enter current password for db2inst8:

Database Connection Information

Database server = DB2/LINUX 8.1.6
SQL authorization ID = DB2INST8
Local database alias = SASITE


My database manager configuration is set as follows:


(AUTHENTICATION) = CLIENT
(CATALOG_NOAUTH) = NO
(TRUST_ALLCLNTS) = YES
(TRUST_CLNTAUTH) = CLIENT
(FED_NOAUTH) = NO

I originally had the AUTHENTICATION set to SERVER and was receiving the
same sql30082n error.
I am able to log on to the server with the user and password so I know the
user and passwords are valid.

Also, I checked the authorations on the db2chkau program and they are set
as follows:

lrwxrwxrwx 1 root root 35 Dec 29 14:23 db2chkau ->
/opt/IBM/db2
/V8.1/security/db2chkau


This is my first time working with Linux and am wondering if this is
something Linux specific because I haven't encountered
anything like this on AIX or Solaris. Has anybody encountered this? Any
ideas?

Thank you.

Dawn Kastelic
DB2 Database Administrator
Highmark Blue Cross Blue Shield

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Glenn mackey

Re: SQL30082N - reason code 24 UDB Linux
(in response to Dawn Kastelic)
I had a similar issue recently.
In my case, the Linux password had expired or something.
I used root and reset/changed the password. (passwd)
That solved my problem.

So to begin with, try to logon to the linux instance with the user id
and see if that sheds any light.

Just a thought.



________________________________

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Dawn Kastelic
Sent: Tuesday, January 18, 2005 9:21 AM
To: [login to unmask email]
Subject: [DB2-L] SQL30082N - reason code 24 UDB Linux



I am running DB2 V 8.1.6 on Linux. I have 2 instances with several
databases catalogued on each instance.
I am able to connect to a database using the following:

chln088|/home/lidxpbb> db2 connect to sasite

Database Connection Information

Database server = DB2/LINUX 8.1.6
SQL authorization ID = LIDXPBB
Local database alias = SASITE

When I try to connect with the user and password, I get the following:

chln088|/home/lidxpbb> db2 connect to sasite user lidxpbb
Enter current password for lidxpbb:
SQL30082N Attempt to establish connection failed with security reason
"24"
("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

I am able to connect with the user and password while using the instance
owner:

chln088|/home/lidxpbb> db2 connect to sasite user db2inst8
Enter current password for db2inst8:

Database Connection Information

Database server = DB2/LINUX 8.1.6
SQL authorization ID = DB2INST8
Local database alias = SASITE


My database manager configuration is set as follows:


(AUTHENTICATION) = CLIENT
(CATALOG_NOAUTH) = NO
(TRUST_ALLCLNTS) = YES
(TRUST_CLNTAUTH) = CLIENT
(FED_NOAUTH) = NO

I originally had the AUTHENTICATION set to SERVER and was receiving the
same sql30082n error.
I am able to log on to the server with the user and password so I know
the user and passwords are valid.

Also, I checked the authorations on the db2chkau program and they are
set as follows:

lrwxrwxrwx 1 root root 35 Dec 29 14:23 db2chkau ->
/opt/IBM/db2
/V8.1/security/db2chkau


This is my first time working with Linux and am wondering if this is
something Linux specific because I haven't encountered
anything like this on AIX or Solaris. Has anybody encountered this?
Any ideas?

Thank you.

Dawn Kastelic
DB2 Database Administrator
Highmark Blue Cross Blue Shield
------------------------------------------------------------------------
--------- Welcome to the IDUG DB2-L list. To unsubscribe, go to the
archives and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Dawn Kastelic

Re: SQL30082N - reason code 24 UDB Linux
(in response to Glenn mackey)
Thanks for the tip, however, I am able to successfully logon to the
instance with that user id
so it's not a password issue.





"Mackey, Glenn" <[login to unmask email]>
Sent by: "DB2 Data Base Discussion List" <[login to unmask email]>
01/18/2005 11:34 AM
Please respond to
"DB2 Database Discussion list at IDUG" <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: [DB2-L] SQL30082N - reason code 24 UDB Linux






I had a similar issue recently.
In my case, the Linux password had expired or something.
I used root and reset/changed the password. (passwd)
That solved my problem.

So to begin with, try to logon to the linux instance with the user id and
see if that sheds any light.

Just a thought.



From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Dawn Kastelic
Sent: Tuesday, January 18, 2005 9:21 AM
To: [login to unmask email]
Subject: [DB2-L] SQL30082N - reason code 24 UDB Linux


I am running DB2 V 8.1.6 on Linux. I have 2 instances with several
databases catalogued on each instance.
I am able to connect to a database using the following:

chln088|/home/lidxpbb> db2 connect to sasite

Database Connection Information

Database server = DB2/LINUX 8.1.6
SQL authorization ID = LIDXPBB
Local database alias = SASITE

When I try to connect with the user and password, I get the following:

chln088|/home/lidxpbb> db2 connect to sasite user lidxpbb
Enter current password for lidxpbb:
SQL30082N Attempt to establish connection failed with security reason
"24"
("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001

I am able to connect with the user and password while using the instance
owner:

chln088|/home/lidxpbb> db2 connect to sasite user db2inst8
Enter current password for db2inst8:

Database Connection Information

Database server = DB2/LINUX 8.1.6
SQL authorization ID = DB2INST8
Local database alias = SASITE


My database manager configuration is set as follows:


(AUTHENTICATION) = CLIENT
(CATALOG_NOAUTH) = NO
(TRUST_ALLCLNTS) = YES
(TRUST_CLNTAUTH) = CLIENT
(FED_NOAUTH) = NO

I originally had the AUTHENTICATION set to SERVER and was receiving the
same sql30082n error.
I am able to log on to the server with the user and password so I know the
user and passwords are valid.

Also, I checked the authorations on the db2chkau program and they are set
as follows:

lrwxrwxrwx 1 root root 35 Dec 29 14:23 db2chkau ->
/opt/IBM/db2
/V8.1/security/db2chkau


This is my first time working with Linux and am wondering if this is
something Linux specific because I haven't encountered
anything like this on AIX or Solaris. Has anybody encountered this? Any
ideas?

Thank you.

Dawn Kastelic
DB2 Database Administrator
Highmark Blue Cross Blue Shield
---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm
---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm