DB2 v8.2 on Linux - suddenly can not connect to any DB and Admin Server won't start. HELP PLEASE!!

[j***@us.ibm.com]

Of course I have a deadline! demo Monday am!
Have 1 instance, 10 dbs, changed NUMDB from 8 to 12, stopped db2, started db2.
Came up ok... but now the Admin Server won't start AND can't connect to any db remotely. Was able to do all this perfectly until stop/start db2.
From client, via CLP, getting SQL30082N - reason code 24, sqlstate 08001.
Using same id/pw that I've always used.
Can anyone help???? Please???
Thanks for any assistance.
J

[Willy Unger]

Hi, J

The possible causes for this are listed as:


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.

THIS WOULD BE TYPICAL OF A NEW FIXPAK. HAVE YOU INSTALLED A DB2 FIXPAK RECENTLY? IF SO, CAREFULLY REVIEW THE WHOLE EADME DOCUMENT, YOU MAY BE MISSING THE DB2IUPDT, OR MAYBE YOU DIDN'T REBIND? THIS ALSO APPLIES IF YOU APPLIED MAINTENANCE AT THE CLIENT.

2. Ensure that the username created is valid. Review the DB2
General Naming Rules.

HAVE YOU BEEN PLAYING AROUND WITH AUTHENTICATION? REMEMBER DB2 DEFERS USER ID/PWD TO THE OPERATING SYSTEM. AS A QUICK FIX, SUGGEST YOU DEFINE THE USER ID LOCALLY AT THE MACHINE WHERE DB2 RUNS, THEN FIND OUT WHAT MAY BE MISSING IN TERMS OF DOMAIN, ETC. AUTHENTICATION.

3. Ensure that catalog information is correct.,

SELF EXPLANATORY. ALTHOUGH HIGHLY IMPROBABLE, YOUR CATALOG ENTRIES MAY BE CORRUPT. TRY CATALOGING THE NODE AND THE DB AGAIN, PERHAPS WITH A DIFFERENT INSTANCE, AND SEE IF YOU CAN CONNECT.

GOOD LUCK,

WILLY



Best Regards,

Willy Unger

DB2 Certified Specialist
***@yahoo.com

[j***@us.ibm.com]

Thank you for the reply Willy. I didn't install any fixpaks, but when I did a few months ago, I ran the dasiupt and db2iupdt commands. I saw a post regarding this yesterday in my search and it suggested running the dasiupdt, which I did and that allowd me to start the admin server, but still could not connect.
Then on a hunch, ran db2iupdt and that allowed me to connect.
After getting through that, db2stop would not complete. Tried all the things I knew (list applications, force applications all, db2stop force, etc) nothing worked. Another post suggested db2_kill and that worked finally..
but..
after that, needed to drop a db - worked ok.
Needed to re-create db with same name - db2 says db exists!
I guess by db directory was corrupt, but could not clean it up.
Tried uncatalog - said db does not exist
Tried catalog - said db already exists.
Do you know of any way around that?
Really appreciate your help!
J