This is a discussion on DB2 Client within the DB2 forums, part of the Database Server Software category; --> - - - What is needed to give an End User access to some tables with an interactive tool. ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| - - - What is needed to give an End User access to some tables with an interactive tool. Why isn't this DB2 Client enough? - - - When I run a DB2 Connect Personal Edition 7.2 - everthing works fine. But this is much more, than an End User ought to see. Then I found this DB2 Client (runtime - dk version). I installed it, and it works as long as I use the db2admin or an Administrator to connect to the db. (I only installed the RunTime, not Administration nor Development.) But I cannot make it work for ordinary EndUsers. I get an 'SQL0551' - execute permissions. If I try to bind using the Client Configuration Assistant. It seems that it cannot find what's needed. Connection is okay - but no selects can be done. I have setup a ODBC DataSource for the database needed.. I have grantet connect auth to the user(s), and granted select, insert, delete, update to them. On the database menu I've tried to give them connect and bind. (I hate this bind thing.) Thans for any help. /Jep |
| |||
| Jep <dontspam_jep@jepweb.dk> wrote: > What is needed to give an End User access to some tables with an > interactive tool. Why isn't this DB2 Client enough? Why do you think it is not enough? > Then I found this DB2 Client (runtime - dk version). I installed it, > and it works as long as I use the db2admin or an Administrator to > connect to the db. > > (I only installed the RunTime, not Administration nor Development.) > > But I cannot make it work for ordinary EndUsers. > > I get an 'SQL0551' - execute permissions. > If I try to bind using the Client Configuration Assistant. It seems > that it cannot find what's needed. Connection is okay - but no selects > can be done. Have a look at authorization and privileges in the docmuntation. The GRANT statement is used to allow users to access or execute certain operations. It seems that you (as the database administrator) did not give the user in question the privilege to perform a SELECT against the table. > I have grantet connect auth to the user(s), and granted select, > insert, delete, update to them. Maybe you should statem exactly what you did, how you did the GRANT, how you connected to the database and so on. -- Knut Stolze Information Integration IBM Germany / University of Jena |
| |||
| On Wed, 15 Oct 2003 13:29:55 +0200, Knut Stolze <stolze@de.ibm.com> wrote: > The GRANT >statement is used to allow users to access or execute certain operations. >It seems that you (as the database administrator) did not give the user in >question the privilege to perform a SELECT against the table. > The users have SELECT, INSERT, UPDATE, DELETE rights. They have been granted CONNECT and BIND. Do you mean that I have to know every build in package to 'GRANT EXECUTE' on ex. SQLC2D04, SQLC3D09, etc. ... ??? - - - If the problem is on the DB Server side (Authorisations), why does it work, when I install the full DB2 Connect Pers Edition ?? And not when I run the simple DB2Client ??? Auth's were not changed . /Jep |
| ||||
| Jep wrote: > On Wed, 15 Oct 2003 13:29:55 +0200, Knut Stolze <stolze@de.ibm.com> > wrote: > > >> The GRANT >>statement is used to allow users to access or execute certain operations. >>It seems that you (as the database administrator) did not give the user in >>question the privilege to perform a SELECT against the table. >> > > > The users have SELECT, INSERT, UPDATE, DELETE rights. > > They have been granted CONNECT and BIND. > > Do you mean that I have to know every build in package to 'GRANT > EXECUTE' on ex. SQLC2D04, SQLC3D09, etc. ... ??? Jep, You need to bind the client code to the database(s) that your users will connect to. This is a one time exercise (for a particular client fixpack level), and should be done by a user with BINDADD authority (i.e. db2admin ). In the Configuration Assistant, choose the database, and then choose 'Selected ... Bind' in the menu. You should select all utilities, and in the Bind Options, set "BLOCKING ALL" and "GRANT PUBLIC" Then all of your client machines will be able to connect and use the database. Good luck, -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! -----== Over 100,000 Newsgroups - 19 Different Servers! =----- |