The problem you are experiencing is that the name you choose DBADB2UDB is 9 characters long and the DB2 only recognizes only up to 8 character names. You need to reset it to an a 8 character name.
Ron Draper
Computer Information Technology Specialist I
Missouri Department of Natural Resources
MIS Program
526-1077
[EMAIL PROTECTED]
Microsoft Certified Professional
| "McLeod, Scott" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 04/06/2001 09:26 AM
|
To: [EMAIL PROTECTED] cc: (bcc: Ronald Draper/MIS/DAS/MODNR) Subject: DB2EUG: Assigning a New SYSADM |
I update issued the following command:
db2 update dbm cfg using SYSADM_GROUP DBADB2UDB
db2stop
db2start
When I try to issue a "list applications" command I get a not authorized
message. Yet when I run a "net user {myid} /DOMAIN" it shows me I am a
meber of the domain global group DBADB2UDB. When running this
DB2_GRP_LOOKUP is set to null (via "db2set DB2_GRP_LOOPUP -null" command) so
at this point I should be sysadm using that domain group.
Anyone experience something like this before?
> TTFN and Hold Fast!
> Scott McLeod of MacLeod
> Best Buy, Inc.
> Sr. Database Architect
> 7750 Flying Cloud Dr.
> Eden Prairie, MN 55344
>
> (612) 324-0031 (voice)
> (612) 324-0828 (fax)
>
> [EMAIL PROTECTED]
>
>
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
