There is no new fixpack & not sure about recently changed
permissions on DB2 critical files such as db2ckpw.
Any problem if I run db2iupdt just like that. Looks risky.

From SSH terminal client. Server control center is not opening
since GUI is disabled. telnet to server is also failing. Are
these linked with this connection problem.
get dbm cfg
AUTHENTICATION = SERVER

DB2INSATNCE = /home/db2inst1/db2inst1 & db2 is not recognized
(just yesterday this was working fine)

ENV & SET commands: What does their output show and what is the
difference between the two?

First created user as it is, then its group got added as a db2
group to database on giving connect privilege. Trying to add
user from client control center, then not listing users in drop
down after warning that das may not have been started. I checked
& it is active. So, I manually typed user name, checked connect
checkbox but not connecting now also.

Now created user assigning it to group db2grp1 & it is added
properly in client control center with connect check box already
checked but even now not connecting.

Popular White Paper On This Topic

If its a new user created, Please log into the server manually with the new
user ID, as when a new user logs in, it will ask you to change the passwor
d. If you don't do this and try to connect thru the application then you w
ill get this error and the account/ID will get locked.
-Arun.

Yes I can. But on using SSH client terminal login first time it is not
asking to change password. telnet is not working from my windows client i.e.
it is jumping out. I did not try to login from within server itself. GUI is
not working in the linux server.

Instance is showing as DB2INSTANCE = /home/db2inst1/db2inst1 & db2 is not
recognized even when making db2profile with path entry in users profile. But
when manually run at shell prompt, then everything sets right but on trying
to connect from terminal client:

If I keep . {INSTHOME}/sqllib/db2profile in users .bash_profile it is not
working. Maybe ${INSTHOME?}/sqllib/db2profile will work. Am I configuring in
the correct profile file?

But when I use . {INSTHOME}/sqllib/db2profile at shell prompt itself
temporarily, db2 is recognized.

Also, with instance user db2inst1 the instance is showing correctly using
ENV or SET commands i.e. DB2INSTANCE = db2inst1. Any other user including
root it is showing as /home/db2inst1/db2inst1. Is this correct & if not how
do set it right? What is difference between ENV and SET?

From linux server also, on creating user with password or setting it with
passwd using root, on logging out and logging in for first time it is not
asking to reset password i.e. it is logging in successfully. If we just
create user using useradd or adduser command without mentioning password
what password gets set? In this case I maybe prompted to change password on
first login and the whole thing may work. Please help. Thank you.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.