By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,282 Members | 1,615 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,282 IT Pros & Developers. It's quick & easy.

Getting SQL30082N resaon 19 on DB2 9

P: n/a
I have installed DB2 9 Enterprise Edition on my laptop (Windows xp prof.
ed.). But when I try to connect to any of my local databases I get this
error:

SQL30082N Security processing failed with reason "19" ("USERID DISABLED or
RESTRICTED"). SQLSTATE=08001

I am quite certain that this user is valid, I have used it to log on to the
pc. The properties of the user also looks fine -password never expires, and
the disabled checkbox is NOT checked. And it's the same user the db2 service
uses. I have further checked that the user is member of these groups:
Administrators, DB2ADMNS, DB2SYADM (which is the group I use as
SYSADM_GROUP). So I will not accept that this user has any restrictions as
to access db2 :-)

If I logon without applying the username and password from a Command
window, I can connect : 'db2 connect to sample' works fine. But if I connect
with ' db2 connect to sample user db2admin using xxxxxx' I get the error
message.

I can connect to remote databases ( all on version 8) without problems. It's
the local databases that gives med the headache.....

I suspect there have been changes in security policy in version 9, but I
cannot find anything in the documentation.

Anyone have the solution to this?

Regards
Odd B Andersen
ErgoGroup AS, Oslo, Norway

Oct 4 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Not sure this is still applicable to V9. But in V8 these are the
solutions....
You can try

Ask the Windows administrator (someone with Administrator privileges)
to add the "Access this computer from the network" privilege to the
accounts of users who are connecting to the database. This can be done
through "Computer Configuration\Windows Settings\Security
Settings\Local Policies\User Rights Assignment" setting. If server
authentication is being used, then the userid must have this access on
the DB2 UDB server. If client authentication is being used, then the
userid must have this privilege on the DB2 UDB client.

Alternatively:
Add the user to DB2ADMIN or DB2USERS group. During the installation of
DB2 UDB, "Access this computer from the network" privilege is
automatically granted to these groups if the Extended Security is
enabled (that is, the DB2_EXTSECURITY registry variable is set to YES).
cheers..
Shashi Mannepalli
Odd Bjørn Andersen wrote:
I have installed DB2 9 Enterprise Edition on my laptop (Windows xp prof.
ed.). But when I try to connect to any of my local databases I get this
error:

SQL30082N Security processing failed with reason "19" ("USERID DISABLED or
RESTRICTED"). SQLSTATE=08001

I am quite certain that this user is valid, I have used it to log on to the
pc. The properties of the user also looks fine -password never expires, and
the disabled checkbox is NOT checked. And it's the same user the db2 service
uses. I have further checked that the user is member of these groups:
Administrators, DB2ADMNS, DB2SYADM (which is the group I use as
SYSADM_GROUP). So I will not accept that this user has any restrictions as
to access db2 :-)

If I logon without applying the username and password from a Command
window, I can connect : 'db2 connect to sample' works fine. But if I connect
with ' db2 connect to sample user db2admin using xxxxxx' I get the error
message.

I can connect to remote databases ( all on version 8) without problems. It's
the local databases that gives med the headache.....

I suspect there have been changes in security policy in version 9, but I
cannot find anything in the documentation.

Anyone have the solution to this?

Regards
Odd B Andersen
ErgoGroup AS, Oslo, Norway
Oct 4 '06 #2

P: n/a
If you are running in a Windows domain, you might try logging in as a
domain user, i.e. DOMAIN\user instead of user. I have a PMR open with a
very similar security problem. I would be curious to know if this works
for you.

Harold Trammel

Odd Bjørn Andersen wrote:
I have installed DB2 9 Enterprise Edition on my laptop (Windows xp prof.
ed.). But when I try to connect to any of my local databases I get this
error:

SQL30082N Security processing failed with reason "19" ("USERID DISABLED or
RESTRICTED"). SQLSTATE=08001

I am quite certain that this user is valid, I have used it to log on to the
pc. The properties of the user also looks fine -password never expires, and
the disabled checkbox is NOT checked. And it's the same user the db2 service
uses. I have further checked that the user is member of these groups:
Administrators, DB2ADMNS, DB2SYADM (which is the group I use as
SYSADM_GROUP). So I will not accept that this user has any restrictions as
to access db2 :-)

If I logon without applying the username and password from a Command
window, I can connect : 'db2 connect to sample' works fine. But if I connect
with ' db2 connect to sample user db2admin using xxxxxx' I get the error
message.

I can connect to remote databases ( all on version 8) without problems. It's
the local databases that gives med the headache.....

I suspect there have been changes in security policy in version 9, but I
cannot find anything in the documentation.

Anyone have the solution to this?

Regards
Odd B Andersen
ErgoGroup AS, Oslo, Norway
Oct 5 '06 #3

P: n/a
In article <45***********************@news.sunsite.dk>, ob****@online.no
says...
I have installed DB2 9 Enterprise Edition on my laptop (Windows xp prof.
ed.). But when I try to connect to any of my local databases I get this
error:
Officially DB2 EE isn't supported on Windows XP.
Oct 5 '06 #4

P: n/a
That solved my problem! Adding 'Access this computer from the network'
privilege to the proper group was the solution to this.

Thank you all for your help.

Regards
Odd B.

"Shashi Mannepalli" <sh********@yahoo.comwrote in message
news:11**********************@m7g2000cwm.googlegro ups.com...
Not sure this is still applicable to V9. But in V8 these are the
solutions....
You can try

Ask the Windows administrator (someone with Administrator privileges)
to add the "Access this computer from the network" privilege to the
accounts of users who are connecting to the database. This can be done
through "Computer Configuration\Windows Settings\Security
Settings\Local Policies\User Rights Assignment" setting. If server
authentication is being used, then the userid must have this access on
the DB2 UDB server. If client authentication is being used, then the
userid must have this privilege on the DB2 UDB client.

Alternatively:
Add the user to DB2ADMIN or DB2USERS group. During the installation of
DB2 UDB, "Access this computer from the network" privilege is
automatically granted to these groups if the Extended Security is
enabled (that is, the DB2_EXTSECURITY registry variable is set to YES).
cheers..
Shashi Mannepalli
Odd Bjørn Andersen wrote:
I have installed DB2 9 Enterprise Edition on my laptop (Windows xp prof.
ed.). But when I try to connect to any of my local databases I get this
error:

SQL30082N Security processing failed with reason "19" ("USERID DISABLED
or
RESTRICTED"). SQLSTATE=08001

I am quite certain that this user is valid, I have used it to log on to
the
pc. The properties of the user also looks fine -password never expires,
and
the disabled checkbox is NOT checked. And it's the same user the db2
service
uses. I have further checked that the user is member of these groups:
Administrators, DB2ADMNS, DB2SYADM (which is the group I use as
SYSADM_GROUP). So I will not accept that this user has any restrictions as
to access db2 :-)

If I logon without applying the username and password from a Command
window, I can connect : 'db2 connect to sample' works fine. But if I
connect
with ' db2 connect to sample user db2admin using xxxxxx' I get the error
message.

I can connect to remote databases ( all on version 8) without problems.
It's
the local databases that gives med the headache.....

I suspect there have been changes in security policy in version 9, but I
cannot find anything in the documentation.

Anyone have the solution to this?

Regards
Odd B Andersen
ErgoGroup AS, Oslo, Norway

Oct 9 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.