Lost/compromise db2admin password

[DonLi]

Hi IBMers,

I haven't used the db2 v8.1 on my win OS for a while, now, all of a
sudden, it became a stranger to me or vice versa, to start with, db2
db server can no longer starts, it complained about logon failure, I
managed to find the db2admin logon pwd, however, to no avail; searched
the NG for clue, got something like "get dbm cfg", it won't help,
minic "get dbm db2admin", "get dbm pwd|pasword" neither helped.

So, help, I'm "drowning", TIA.

Don

[Dave Hughes]

On 2004-04-08, DonLi scribbled:

Hi IBMers,

I haven't used the db2 v8.1 on my win OS for a while, now, all of a
sudden, it became a stranger to me or vice versa, to start with, db2
db server can no longer starts, it complained about logon failure, I
managed to find the db2admin logon pwd, however, to no avail; searched
the NG for clue, got something like "get dbm cfg", it won't help,
minic "get dbm db2admin", "get dbm pwd|pasword" neither helped.

So, help, I'm "drowning", TIA.

Don

On Windows NT/2000/XP, DB2 usually uses Windows itself to handle
authentication. Hence, there is no way to ask DB2 "what is the password
for user X?" (just as you cannot ask Windows "what is the password for
user X?"). Which is not to say that Windows passwords are 100% safe and
couldn't be cracked - they can be, and this _may_ be what has happened
in your case.

However, you may also have password policies set, such as "passwords
expire after 180 days" or similar. In this case, it may be that the
password for the db2admin user has now expired and the DB2 services are
no longer capable of logging on using the password they have. If this
is the case, you can probably get around it by setting the "Password
never expires" option for the db2admin user.

Otherwise, you'll need to reset the password for the db2admin user (I'd
recommend doing this anyway just to assuage any paranoia), and set all
the DB2 services that logon using db2admin to use the new password.

Note that, to change the password (and optionally userid) used by the
DB2 administrator server (usually the service called "DB2 - DB2DAS00"),
you should use the following command line instead of changing it
manually in the Services console:

db2admin SETID <username> <password>

I seem to remember this avoids some problem that can occur with the
manual method - but can't remember exactly what or where I read it.

HTH, Dave.

--
Dave
Remove "_nospam" for valid e-mail address

"Never underestimate the bandwidth of a station wagon full of CDs doing
a ton down the highway" -- Anon.

[DonLi]

Thank you very much for the explanation and the remedy. Executing
db2admin SETID <username> <password>
at Command Window was successful, and I tried to start the DB2-DB2
service and then DB2DAS service, also reversed the sequence, also
tried to started all other DB2 related services first, however, both
of these two services failed to start, respective err msgs: 8000 and
22204. Just searched the NG for clue to these two errors respectively
to no avail. Would appreciate your further assistance in this
important matter very much.
"Dave Hughes" <da*********@wa veform.plus.com > wrote in message news:<xn******* *********@usene t.plus.net>...

On 2004-04-08, DonLi scribbled:

Hi IBMers,

I haven't used the db2 v8.1 on my win OS for a while, now, all of a
sudden, it became a stranger to me or vice versa, to start with, db2
db server can no longer starts, it complained about logon failure, I
managed to find the db2admin logon pwd, however, to no avail; searched
the NG for clue, got something like "get dbm cfg", it won't help,
minic "get dbm db2admin", "get dbm pwd|pasword" neither helped.

So, help, I'm "drowning", TIA.

Don

On Windows NT/2000/XP, DB2 usually uses Windows itself to handle
authentication. Hence, there is no way to ask DB2 "what is the password
for user X?" (just as you cannot ask Windows "what is the password for
user X?"). Which is not to say that Windows passwords are 100% safe and
couldn't be cracked - they can be, and this _may_ be what has happened
in your case.

However, you may also have password policies set, such as "passwords
expire after 180 days" or similar. In this case, it may be that the
password for the db2admin user has now expired and the DB2 services are
no longer capable of logging on using the password they have. If this
is the case, you can probably get around it by setting the "Password
never expires" option for the db2admin user.

Otherwise, you'll need to reset the password for the db2admin user (I'd
recommend doing this anyway just to assuage any paranoia), and set all
the DB2 services that logon using db2admin to use the new password.

Note that, to change the password (and optionally userid) used by the
DB2 administrator server (usually the service called "DB2 - DB2DAS00"),
you should use the following command line instead of changing it
manually in the Services console:

db2admin SETID <username> <password>

I seem to remember this avoids some problem that can occur with the
manual method - but can't remember exactly what or where I read it.

HTH, Dave.

[Amar]

DB2 doesn't store any information on your user db2admin or any other
users. It's useless to ask DB2 for password. Check if you can login
with db2admin user and password on your OS or you can reset your
password on OS if you have system
admin previlege. This might solve your problem.

I hope this helps.

Amar.

do***@yahoo.com (DonLi) wrote in message news:<9a******* *************** ****@posting.go ogle.com>...

Thank you very much for the explanation and the remedy. Executing
db2admin SETID <username> <password>
at Command Window was successful, and I tried to start the DB2-DB2
service and then DB2DAS service, also reversed the sequence, also
tried to started all other DB2 related services first, however, both
of these two services failed to start, respective err msgs: 8000 and
22204. Just searched the NG for clue to these two errors respectively
to no avail. Would appreciate your further assistance in this
important matter very much.
"Dave Hughes" <da*********@wa veform.plus.com > wrote in message news:<xn******* *********@usene t.plus.net>...

On 2004-04-08, DonLi scribbled:

Hi IBMers,

I haven't used the db2 v8.1 on my win OS for a while, now, all of a
sudden, it became a stranger to me or vice versa, to start with, db2
db server can no longer starts, it complained about logon failure, I
managed to find the db2admin logon pwd, however, to no avail; searched
the NG for clue, got something like "get dbm cfg", it won't help,
minic "get dbm db2admin", "get dbm pwd|pasword" neither helped.

So, help, I'm "drowning", TIA.

Don

On Windows NT/2000/XP, DB2 usually uses Windows itself to handle
authentication. Hence, there is no way to ask DB2 "what is the password
for user X?" (just as you cannot ask Windows "what is the password for
user X?"). Which is not to say that Windows passwords are 100% safe and
couldn't be cracked - they can be, and this _may_ be what has happened
in your case.

However, you may also have password policies set, such as "passwords
expire after 180 days" or similar. In this case, it may be that the
password for the db2admin user has now expired and the DB2 services are
no longer capable of logging on using the password they have. If this
is the case, you can probably get around it by setting the "Password
never expires" option for the db2admin user.

Otherwise, you'll need to reset the password for the db2admin user (I'd
recommend doing this anyway just to assuage any paranoia), and set all
the DB2 services that logon using db2admin to use the new password.

Note that, to change the password (and optionally userid) used by the
DB2 administrator server (usually the service called "DB2 - DB2DAS00"),
you should use the following command line instead of changing it
manually in the Services console:

db2admin SETID <username> <password>

I seem to remember this avoids some problem that can occur with the
manual method - but can't remember exactly what or where I read it.

HTH, Dave.

[DonLi]

Yeah, I'm able to log on as db2Admin from OS, however, this same user
failed to start DB2 - DB2 service, though this user belongs to sys
admin group. Oh, forget it, DB2 is not my priority for now. Thanks
though.

he*******@yahoo .com (Amar) wrote in message news:<47******* *************** ****@posting.go ogle.com>...

DB2 doesn't store any information on your user db2admin or any other
users. It's useless to ask DB2 for password. Check if you can login
with db2admin user and password on your OS or you can reset your
password on OS if you have system
admin previlege. This might solve your problem.

I hope this helps.

Amar.

do***@yahoo.com (DonLi) wrote in message news:<9a******* *************** ****@posting.go ogle.com>...

Thank you very much for the explanation and the remedy. Executing
db2admin SETID <username> <password>
at Command Window was successful, and I tried to start the DB2-DB2
service and then DB2DAS service, also reversed the sequence, also
tried to started all other DB2 related services first, however, both
of these two services failed to start, respective err msgs: 8000 and
22204. Just searched the NG for clue to these two errors respectively
to no avail. Would appreciate your further assistance in this
important matter very much.
"Dave Hughes" <da*********@wa veform.plus.com > wrote in message news:<xn******* *********@usene t.plus.net>...

On 2004-04-08, DonLi scribbled:

> Hi IBMers,
>
> I haven't used the db2 v8.1 on my win OS for a while, now, all of a
> sudden, it became a stranger to me or vice versa, to start with, db2
> db server can no longer starts, it complained about logon failure, I
> managed to find the db2admin logon pwd, however, to no avail; searched
> the NG for clue, got something like "get dbm cfg", it won't help,
> minic "get dbm db2admin", "get dbm pwd|pasword" neither helped.
>
> So, help, I'm "drowning", TIA.
>
> Don

On Windows NT/2000/XP, DB2 usually uses Windows itself to handle
authentication. Hence, there is no way to ask DB2 "what is the password
for user X?" (just as you cannot ask Windows "what is the password for
user X?"). Which is not to say that Windows passwords are 100% safe and
couldn't be cracked - they can be, and this _may_ be what has happened
in your case.

However, you may also have password policies set, such as "passwords
expire after 180 days" or similar. In this case, it may be that the
password for the db2admin user has now expired and the DB2 services are
no longer capable of logging on using the password they have. If this
is the case, you can probably get around it by setting the "Password
never expires" option for the db2admin user.

Otherwise, you'll need to reset the password for the db2admin user (I'd
recommend doing this anyway just to assuage any paranoia), and set all
the DB2 services that logon using db2admin to use the new password.

Note that, to change the password (and optionally userid) used by the
DB2 administrator server (usually the service called "DB2 - DB2DAS00"),
you should use the following command line instead of changing it
manually in the Services console:

db2admin SETID <username> <password>

I seem to remember this avoids some problem that can occur with the
manual method - but can't remember exactly what or where I read it.

HTH, Dave.

[Dave Hughes]

On 2004-04-09, DonLi scribbled:

Thank you very much for the explanation and the remedy. Executing
db2admin SETID <username> <password>
at Command Window was successful, and I tried to start the DB2-DB2
service and then DB2DAS service, also reversed the sequence, also
tried to started all other DB2 related services first, however, both
of these two services failed to start, respective err msgs: 8000 and
22204. Just searched the NG for clue to these two errors respectively
to no avail. Would appreciate your further assistance in this
important matter very much.

[snip]

Just looked up SQL8000 in the DB2 Message Reference, Volume 2 which
reads:

"Explanatio n: A valid license key could not be found and the evaluation
period has expired.

User Response: Install a license key for the fully entitled version of
the product. You can obtain a license key for the product by contacting
your IBM representative or authorized dealer."

So, assuming you do actually have a license, and that you don't have a
expired try-and-buy installation, the problem could be that the "DB2
Licensing Server" service isn't started, or is failing to start. Take a
look in the services control panel to check whether it's started, and
try and start it if not.

Failing that, there's an application you can start which allows you to
list and maintain the licenses for DB2 - unfortunately, I can't
remember it off-hand right now - but it should be somewhere under the
Start menu group containing the other DB2 apps like Control Center, etc.

Also, I couldn't find any information on message SQL22204 (assuming it
is an SQL error message - could you post any other output you got with
this message?)

HTH, Dave.
--
Dave
Remove "_nospam" for valid e-mail address

"Never underestimate the bandwidth of a station wagon full of CDs doing
a ton down the highway" -- Anon.

[Eric Diamond]

DonLi wrote:

Yeah, I'm able to log on as db2Admin from OS, however, this same user
failed to start DB2 - DB2 service, though this user belongs to sys
admin group. Oh, forget it, DB2 is not my priority for now. Thanks
though.

You have to use the Windows "Services" application
to update the password that is used when the
service is started.

Start -- Run -- services.msc
The userid & pwd entry fields are located on the LogOn tab.

--
Eric Diamond/New York

e-mail address brought to you by
http://whois.ibm.com and the letter "J"