Prev: Spam
Next: Single System View (SSV) with DB2 9.7 DPF
From: Thomas Kellerer on 4 Nov 2009 05:10
Frederik Engelen, 04.11.2009 10:15:
> Normally, you shouldn't have to set the SYSADM_GROUP parameter, as
> Administrators would be used anyway. Did you enable extended security?
> Is the DB2_GRP_LOOKUP variable useful in your case?

What I find really confusing is that according to the manual:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.sec.doc/doc/c0005375.html

db2admin should already have all those privileges (because it was the user created during installation and that was used to create the database)

Do you think if I remove and re-install DB2 this would be fixed?

Regards
Thomas

From: Thomas Kellerer on 4 Nov 2009 05:22
Frederik Engelen, 03.11.2009 21:08:
> I guess you are on v9.7? Since this version SYSADM no longer has
> implicit DBADM.

OK, I decided to drop the database I created and recreate it (as I did not have anything stored in it anyway)

Apparently when I created the initial database I was using my regular Windows account and that apparently messed things up.

I ran a new commandline (using my db2admin Windows user) dropped the existing database, and created a new one

With that database db2admin *does* have dbadm authority (directly, as shown by db2 get authorizations) and I could grant the connect privilege to my regular user.

Thanks for your help

Thomas
First  |  Prev  | 
Pages: 1 2
Prev: Spam
Next: Single System View (SSV) with DB2 9.7 DPF