sysadm_group dilemma

Randy Perry

sysadm_group dilemma
Hi folks,

I work for an educational institute, and we're in the middle of teaching a course in database administration with DB2. Some of our students have encountered what appears to be a catch-22 regarding the sysadm_group parameter, which they've accidentally set to an NT group (when they were supposed to be setting the sysctrl_group parameter). (Oh, we're using DB2 V7.1 on WinNT.)

Our dilemma is this: how can we change the sysadm_group parameter, once it's been set to an NT group? We've logged in as a member of that group, but it tells us we don't have the correct authority to change that parameter. (Which struck us as being rather odd.) We've tried deleting the NT group, but that didn't help.

Any ideas? Or is this really a quintessential catch-22?

Thanks, in advance, for any help!
Randy



Stacey L Waters

Re: sysadm_group dilemma
(in response to Randy Perry)
Randy,
If you set the SYSADM_GROUP to a local NT group read on if not
disregard....

Create a NT domain global group, name the same as the local NT group, and
add it to the Administrators group on the Domain Controller. Drop the
local NT group. Add the new NT to the local Administrators group. DB2
will reference the NT domain group for security. Then you will have the
authority to change the parameter. If you still have issues check the
parameter DB2_GRP_LOOKUP.

Hope this helps!
Stacey





Randy Perry <[login to unmask email]>@RYCI.COM> on 01/12/2001 01:48:43 PM

From: Randy Perry <[login to unmask email]>@RYCI.COM on 01/12/2001 01:48 PM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc:
Subject: sysadm_group dilemma

Hi folks,

I work for an educational institute, and we're in the middle of teaching a
course in database administration with DB2. Some of our students have
encountered what appears to be a catch-22 regarding the sysadm_group
parameter, which they've accidentally set to an NT group (when they were
supposed to be setting the sysctrl_group parameter). (Oh, we're using DB2
V7.1 on WinNT.)

Our dilemma is this: how can we change the sysadm_group parameter, once
it's been set to an NT group? We've logged in as a member of that group,
but it tells us we don't have the correct authority to change that
parameter. (Which struck us as being rather odd.) We've tried deleting
the NT group, but that didn't help.

Any ideas? Or is this really a quintessential catch-22?

Thanks, in advance, for any help!
Randy



http://www.ryci.com/db2-l. The owners of the list can be reached at
[login to unmask email]



Philip Gunning

Re: sysadm_group dilemma
(in response to Stacey L Waters)
Randy, Make sure that the id that you are using is part of the sysadm group
and that the group has Domain or local admin authority. You can look at
this via user manager for domains. If that doesn't work, try using a domain
admin id. That should work. HTH Phil

-----Original Message-----
From: Randy Perry
To: [login to unmask email]
Sent: 1/12/01 11:48 AM
Subject: sysadm_group dilemma

Hi folks,

I work for an educational institute, and we're in the middle of teaching
a course in database administration with DB2. Some of our students have
encountered what appears to be a catch-22 regarding the sysadm_group
parameter, which they've accidentally set to an NT group (when they were
supposed to be setting the sysctrl_group parameter). (Oh, we're using
DB2 V7.1 on WinNT.)

Our dilemma is this: how can we change the sysadm_group parameter, once
it's been set to an NT group? We've logged in as a member of that
group, but it tells us we don't have the correct authority to change
that parameter. (Which struck us as being rather odd.) We've tried
deleting the NT group, but that didn't help.

Any ideas? Or is this really a quintessential catch-22?

Thanks, in advance, for any help!
Randy

=======================To change your
subscription options or to cancel your subscription visit the DB2-L
webpage at http://www.ryci.com/db2-l. The owners of the list can be

Michael McCarthy

Re: sysadm_group dilemma
(in response to Philip Gunning)
Hi Randy,

That parameter change does not take effect until db2 is stopped and started
via the db2stop/db2start commands. If this hasn't happened yet, the old
sysadm_group should still be in effect.

-Mike.





Randy Perry <[login to unmask email]> on 01/12/2001 02:48:43 PM

Please respond to DB2 Data Base Discussion List <[login to unmask email]>

To: [login to unmask email]
cc: (bcc: Michael McCarthy/DTC)
Subject: [DB2-L] sysadm_group dilemma




Hi folks,

I work for an educational institute, and we're in the middle of teaching a
course in database administration with DB2. Some of our students have
encountered what appears to be a catch-22 regarding the sysadm_group parameter,
which they've accidentally set to an NT group (when they were supposed to be
setting the sysctrl_group parameter). (Oh, we're using DB2 V7.1 on WinNT.)

Our dilemma is this: how can we change the sysadm_group parameter, once it's
been set to an NT group? We've logged in as a member of that group, but it
tells us we don't have the correct authority to change that parameter. (Which
struck us as being rather odd.) We've tried deleting the NT group, but that
didn't help.

Any ideas? Or is this really a quintessential catch-22?

Thanks, in advance, for any help!
Randy








paul martin

Re: sysadm_group dilemma
(in response to Michael McCarthy)
To change it back to null/spaces enter:
Db2 update dbm cfg using sysadm_group ''



-----Original Message-----
From: Randy Perry [mailto:[login to unmask email]
Sent: Friday, January 12, 2001 1:49 PM
To: [login to unmask email]
Subject: sysadm_group dilemma

Hi folks,

I work for an educational institute, and we're in the middle of teaching a
course in database administration with DB2. Some of our students have
encountered what appears to be a catch-22 regarding the sysadm_group
parameter, which they've accidentally set to an NT group (when they were
supposed to be setting the sysctrl_group parameter). (Oh, we're using DB2
V7.1 on WinNT.)

Our dilemma is this: how can we change the sysadm_group parameter, once it's
been set to an NT group? We've logged in as a member of that group, but it
tells us we don't have the correct authority to change that parameter.
(Which struck us as being rather odd.) We've tried deleting the NT group,
but that didn't help.

Any ideas? Or is this really a quintessential catch-22?

Thanks, in advance, for any help!
Randy



http://www.ryci.com/db2-l. The owners of the list can be reached at
[login to unmask email]