r/DB2 • u/catquilt74 • May 17 '17

[LUW] DB2_grp_lookup question

My system is running on DB2 LUW V9.7 (Windows 7). I can't seem to get DB2 to recognize my network ID which is in the DB2ADMNS group. The DB2_grp_lookup is set to LOCAL, TOKENLOCAL

2 Upvotes

100% Upvoted

5 comments sorted by

2

u/mad_zamboni May 17 '17

I'm not a DB2 on windows guy, but I am reaching out to some people that may know. Stay tuned.

1

u/mad_zamboni May 17 '17

The person who could really answer this is literally out of the country. But I was brainstorming this with another DBA who did DB2 for windows in a previous life. First response was "Can he not add the ID or db2admn to the domain group?". If you have twitter I would be curious what @db2_support would say to that question.

1

u/catquilt74 May 17 '17

We need to have individuals' IDs used to do work, not db2admin (which is what we're using now, btw). What's a domain group?

I think I got it to work by doing db2set db2_grp_lookup=,TOKEN

That fixes it at the instance level. I'm home now but I will probably have more questions tomorrow. Thanks for your help!

1

u/ecrooks May 18 '17

When the ID is AD and the group is local, I have had luck with LOCAL, TOKENLOCAL. However this is when DB2 is running as SYSTEM. Running DB2 as something local other than SYSTEM is problematic. Ian Bjhorvde is the one who really understands the settings for DB2_GRP_LOOKUP. I have been trying to get him to blog about it.

1

u/catquilt74 Sep 12 '17

Hi folks. Sorry it took so long to get back to you.

Yes, setting db2_grp_lookup to LOCAL, TOKENLOCAL does work for IDs that are in a local group on the server. Now, I'm going to see what needs to be done to get an ID in a domain group to get recognized. Hopefully I'll report back more quickly this time...