Password Validation Rc = -2146500507
For example, db2 "select * from my_tbl". I have tried all the suggestions made here and they made exactly no difference. Re "Shelby", what is that? I found some other articles on this same problem. weblink
We were using NIS and we had to "push" the user IDs to the server - to make it local. Going through the installation script and comparing it with online db2 installation tutorials made it clear to me. I have tried all the suggestions made here and they made exactly no difference. I am still getting "Password Invalid" with all new users I define on my linux box. his explanation
Password Validation Rc = -2146500507
I have all the same groups for the new user as the one that works. There might be something interesting there regarding the connection. DB2 uses so-called "security plugins" for the authentication. In the meantime, any advice/guidance on the 'new' db2diag.log message (Bad User) would be most welcome.
I have tried simpler passwords as wellas the password of a working account. Which linux distro, and is it 32 or 64-bit, and is the db2-instance 32-bit or 64-bit ? Reply With Quote 07-20-12,16:34 #2 Marcus_A View Profile View Forum Posts Registered User Join Date May 2003 Location USA Posts 5,737 Yes, someone tried to use that id. Password Validation For User Failed With Rc = 2146500316 PCMag Digital Group AdChoices unused
Have I missed something at the server end with regards to his DB2 authorities? When he tries to connect to DB2, he gets: > > SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). Related information Support for passwords greater than 8 characters on AIX /etc/security/login.cfg SQL1046N error on ITDS server start Error SQL30082N Reason Code 15 or 24 or 36 Document information More support http://www-01.ibm.com/support/docview.wss?uid=swg21470246 Like you, I don't care to remain mystified wombat53 Top This thread has been closed due to inactivity.
To check what encryption algorithm is being used the login.cfg file will contain something like: usw: shells = /bin/sh,/bin/bsh,/bin/csh,/bin/ksh,/bin/tsh,/bin/ksh93,/usr/bin /sh,/usr/bin/bsh,/usr/bin/csh,/usr/bin/ksh,/usr/bin/tsh,/usr/bin/ksh93,/usr/sbin /sliplogin,/usr/sbin/uucp/uucico,/usr/sbin/snappd,/bin/false maxlogins = 32767 logintimeout = 60 pwd_algorithm = sha256 auth_type Sql30082n Reason 24 There is an underscore "_" in the password, and so there is an opportunity to get this changed/removed so that the contents are alphanumeric only. operating systems, your password can be a maximum of eight (8) characters." This has also been my own understanding for many years. You imply you have confirmation from the Linux sysadmins that the current password meets all rules, e.g.
Db2 Rc = -2146500502
will be gratefully accepted. Check that password has not expired. Password Validation Rc = -2146500507 I am at my wits end. Password Validation For User Failed With "rc = -2146500502" I can login to the server with SSH using the password I assigned.
It's quick & easy. Evolution of End User Computing--Evolving to Better Meet ... Reply With Quote Quick Navigation DB2 Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Non-SQL Forums MongoDB Database Server Software Adabas DB2 Informix Microsoft SQL One would have expected more than one stanza from the log at diaglevel 4, and in any event you have given no indication you followed those steps in that sequence. Db2_num_ckpw_daemons
I have tried all the suggestions made here and they made exactly no difference. Fedora: vi /etc/pam.d/system-auth and modify the following line: # here are the per-package modules (the "Primary" block) password [success=1 default=ignore] pam_unix.so obscure sha512 Edit this line changing the word sha512 to If this doesn't resolve it, I have a bunch of other suggestions. check over here I've read about Michael Elleby's similar problems and the 32-bit instance in a 64-bit environment issue (see "Issue with Remote connections into DB2" from July 2011) but I don't think that
I am still getting "Password Invalid" with all new users I define on my linux box. Sql30082n Security Processing Failed With Reason "15" ("processing Failure"). Sqlstate=08001 Alex Levy replied Mar 22, 2009 Toolbox db2-l Final observations: There is a method in all things. I believe that DB2 Connect V8.2 had issues with some special characters such as #. > > Jeff > _________________________________________ > Jeffrey Schade > Systems Consultant, Technology Engineering > > ISO
Have I missed something at the server end with regards to his DB2 authorities?
Forum New Posts Today's Posts FAQ Calendar Forum Actions Mark Forums Read Quick Links View Site Leaders dBforums Database Server Software DB2 Password validation for user If this is your first If authentication is server, are the specific userids referenced in the /etc/passwd file? Reset if it has expired. -2146500507 2 The password is not valid for the specified user id -2146500290 3 Password missing -2146500504 15, 24, 26, 36 Password length is greater than Have you logged in as one such problematic user at the database server and changed the password manually?
I've got other errors in the db2diag than the ones mentioned there. We were using NIS and we had to "push" the user IDs to the server - to make it local. SQLSTATE=08001 I have DBM CFG : Database manager authentication (AUTHENTICATION) = SERVER This has further ramifications, as in Perl scripts, DB access requires supplying userid and password and I get the All the other messages at or near the same time had to do with loading a security plugin.
A. To gather a trace, just do this: on the server: $ db2trc on -f trc on the client: $ db2 connect to ... The user can log onto the box, connect to the database and select the data that he wants. SQLSTATE=08001 [[email protected] perl]$ wombat53 Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving...
password both fail? I don't think applies tous in this instance: -r-s--x--x 1 root deulb019 2040872 Sep 22 2010 db2ckpw I noticed that there was no entry in /etc/passwd for the user, but The other ID I mentioned is the userid for WebSphere application that connects to the database (Which works). This becomes more intriguing, since the DB2 Info Center says: "When choosing a password, be aware that: * On Linux?
Regards Alex _____ Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... M. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. I have no immediate idea what might be amiss now.
But there's obviously something up with the password. Regards Alex _____ Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving...