SEO

I'm having big problems with the Development Center right now - see other
thread - so I'm hand-coding a UDF. I've managed to get the UDF fully
prepared without any errors but now I'm getting a runtime error I don't
understand.

When I execute a query that tries to use my UDF, I get SQL30082N, Reason 19
("USERID DISABLED or RESTRICTED"). I don't understand why DB2 has a problem
with my ID; I'm sure that the Userid and Password are correct. Also, when I
look at the User and Group Objects for this database in the Control Center,
it acknowledges that the ID is fully authorized to execute the UDF in
question; in fact it has the EXECUTE privilege with the ability to GRANT it
to others. The ID also has all privileges on the database and on the table
that I'm querying with the UDF.

However, there is one confirmation for the SQL30082N:

2005-03-08-20.52.00.650000-300 I165519H257 LEVEL: Severe
PID : 1600 TID : 3068
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 44 bytes
check password failed with rc = -2146500483

Can anyone tell me what I need to do to make DB2 accept my ID?

--
Henry

Henry Reardon wrote:
> I'm having big problems with the Development Center right now - see other
> thread - so I'm hand-coding a UDF. I've managed to get the UDF fully
> prepared without any errors but now I'm getting a runtime error I don't
> understand.
>
> When I execute a query that tries to use my UDF, I get SQL30082N, Reason 19
> ("USERID DISABLED or RESTRICTED"). I don't understand why DB2 has a problem
> with my ID; I'm sure that the Userid and Password are correct. Also, when I
> look at the User and Group Objects for this database in the Control Center,
> it acknowledges that the ID is fully authorized to execute the UDF in
> question; in fact it has the EXECUTE privilege with the ability to GRANT it
> to others. The ID also has all privileges on the database and on the table
> that I'm querying with the UDF.
>
> However, there is one confirmation for the SQL30082N:
>
> 2005-03-08-20.52.00.650000-300 I165519H257 LEVEL: Severe
> PID : 1600 TID : 3068
> FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
> DATA #1 : String, 44 bytes
> check password failed with rc = -2146500483
>
> Can anyone tell me what I need to do to make DB2 accept my ID?
>

-2146500483 = 0x800F007D = USERID SUSPENDED

Check whether userid you are using is suspended or not.

Jan M. Nelken

Hi Henry

Check the userid has been disabled,or the userid has been
restricted from accessing the operating
environment at this time.

Cheers
Guru

Henry Reardon wrote:
> I'm having big problems with the Development Center right now - see
other
> thread - so I'm hand-coding a UDF. I've managed to get the UDF fully
> prepared without any errors but now I'm getting a runtime error I
don't
> understand.
>
> When I execute a query that tries to use my UDF, I get SQL30082N,
Reason 19
> ("USERID DISABLED or RESTRICTED"). I don't understand why DB2 has a
problem
> with my ID; I'm sure that the Userid and Password are correct. Also,
when I
> look at the User and Group Objects for this database in the Control
Center,
> it acknowledges that the ID is fully authorized to execute the UDF in

> question; in fact it has the EXECUTE privilege with the ability to
GRANT it
> to others. The ID also has all privileges on the database and on the
table
> that I'm querying with the UDF.
>
> However, there is one confirmation for the SQL30082N:
>
> 2005-03-08-20.52.00.650000-300 I165519H257 LEVEL: Severe
> PID : 1600 TID : 3068
> FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage,
probe:20
> DATA #1 : String, 44 bytes
> check password failed with rc = -2146500483
>
> Can anyone tell me what I need to do to make DB2 accept my ID?
>
> --
> Henry

Hi Henry,
Are you able to login to system(OS) using that username and
password??

Thiru.
WantedToBeDBA.

"Jan M. Nelken" <Unknown.User@Invalid.Domain> wrote in
news:yqmdnY5AuqjtELPfRVn-gg@rogers.com:

> Henry Reardon wrote:
>> I'm having big problems with the Development Center right now - see
>> other thread - so I'm hand-coding a UDF. I've managed to get the UDF
>> fully prepared without any errors but now I'm getting a runtime error
>> I don't understand.
>>
>> When I execute a query that tries to use my UDF, I get SQL30082N,
>> Reason 19 ("USERID DISABLED or RESTRICTED"). I don't understand why
>> DB2 has a problem with my ID; I'm sure that the Userid and Password
>> are correct. Also, when I look at the User and Group Objects for this
>> database in the Control Center, it acknowledges that the ID is fully
>> authorized to execute the UDF in question; in fact it has the EXECUTE
>> privilege with the ability to GRANT it to others. The ID also has all
>> privileges on the database and on the table that I'm querying with
>> the UDF.
>>
>> However, there is one confirmation for the SQL30082N:
>>
>> 2005-03-08-20.52.00.650000-300 I165519H257 LEVEL: Severe
>> PID : 1600 TID : 3068
>> FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage,
>> probe:20 DATA #1 : String, 44 bytes
>> check password failed with rc = -2146500483
>>
>> Can anyone tell me what I need to do to make DB2 accept my ID?
>>
>
> -2146500483 = 0x800F007D = USERID SUSPENDED
>
> Check whether userid you are using is suspended or not.
>
According to Windows, the ID in question is set to "Password never
expires". The "Account is disabled" checkbox is NOT checked. That means
it's not suspended, right? (I've never had to do much with Windows
userid management. I set up the ID in question 3 years ago and it has
worked fine ever since without having to do anything with it.)

Is there anything else that would explain this error, especially
something that would get set during the installation of DB2, like the
authentication values?

---

By the way, where did you look up -2146500483 (or x800F007D) to
determine that it meant 'USERID SUSPENDED'? I searched on both values
and didn't see anything that translated them to 'USERID SUSPENDED'. I
can imagine getting more such codes in db2diag.log so it would be handy
to know how to translate them to meaningful values.

Henry



--
Henry

"Guru" <gururajan.n@gmail.com> wrote in news:1110348052.530177.196660
@z14g2000cwz.googlegroups.com:

> Hi Henry
>
> Check the userid has been disabled,or the userid has been
> restricted from accessing the operating
> environment at this time.
>
> Cheers
> Guru
>
> Henry Reardon wrote:
>> I'm having big problems with the Development Center right now - see
> other
>> thread - so I'm hand-coding a UDF. I've managed to get the UDF fully
>> prepared without any errors but now I'm getting a runtime error I
> don't
>> understand.
>>
>> When I execute a query that tries to use my UDF, I get SQL30082N,
> Reason 19
>> ("USERID DISABLED or RESTRICTED"). I don't understand why DB2 has a
> problem
>> with my ID; I'm sure that the Userid and Password are correct. Also,
> when I
>> look at the User and Group Objects for this database in the Control
> Center,
>> it acknowledges that the ID is fully authorized to execute the UDF in
>
>> question; in fact it has the EXECUTE privilege with the ability to
> GRANT it
>> to others. The ID also has all privileges on the database and on the
> table
>> that I'm querying with the UDF.
>>
>> However, there is one confirmation for the SQL30082N:
>>
>> 2005-03-08-20.52.00.650000-300 I165519H257 LEVEL: Severe
>> PID : 1600 TID : 3068
>> FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage,
> probe:20
>> DATA #1 : String, 44 bytes
>> check password failed with rc = -2146500483
>>
>> Can anyone tell me what I need to do to make DB2 accept my ID?
>>
>> --
>> Henry
>
>

See my reply to Jan Nelken. The ID appears to be fine (not suspended) if
I'm reading the panel in Windows correctly.




--
Henry

Henry Reardon wrote:

> By the way, where did you look up -2146500483 (or x800F007D) to
> determine that it meant 'USERID SUSPENDED'? I searched on both values
> and didn't see anything that translated them to 'USERID SUSPENDED'. I
> can imagine getting more such codes in db2diag.log so it would be handy
> to know how to translate them to meaningful values.

http://www-306.ibm.com/software/data...eturncodes.pdf


If you claim uour userid is clean and innocent - just reset it and change
password. If the problem still persissts take a trace and either try to attract
my attention or open a PMR with IBM Support

Jan M. Nelken

(jasinek at attglobal dot net)

"Jan M. Nelken" <Unknown.User@Invalid.Domain> wrote in
news:vrGdnSo056gVgbLfRVn-qA@rogers.com:

> Henry Reardon wrote:
>
>> By the way, where did you look up -2146500483 (or x800F007D) to
>> determine that it meant 'USERID SUSPENDED'? I searched on both values
>> and didn't see anything that translated them to 'USERID SUSPENDED'. I
>> can imagine getting more such codes in db2diag.log so it would be
>> handy to know how to translate them to meaningful values.
>
> http://www-306.ibm.com/software/data...upport/techatt
> /returncodes.pdf
>
Thank you, that could be very useful for debugging problems!

>
> If you claim uour userid is clean and innocent - just reset it and
> change password. If the problem still persissts take a trace and
> either try to attract my attention or open a PMR with IBM Support
>
Okay, I'll try that in a while; I'm working on other things for the moment.

I appreciate your help!

--
Henry

Just to followup on this series of posts - someone may find this handy in a
Google search some day - my problem has now been resolved.

If I'm understanding this correctly - and I'm not terribly strong on
Windows administration stuff so I could be wrong - the problem was that my
ID, which worked perfectly well in DB2 Version 7, would not work in DB2
Version 8 because it had no password. (The password on the ID was set to
never expire and the ID had never actually had a password.)

I created a password for the ID and found that my script ran fine as soon
as I had done that. I had to supply the right password to the script and
then everything worked as it had in Version 7.

Does that make sense to people who understand Windows administration and
how it interacts with DB2 Version 8? Unless I hear otherwise, I'll assume
it does and consider the issue resolved.

The only thing that bothers me is that I thought DB2 objected to things
like blank passwords back around Version 5, if not Version 2, which makes
me wonder how I got away with this blank password through Version 6 and 7.
(This ID has existed since I bought this computer 3 years ago back when I
was still running DB2 Version 6.)

--
Henry