Sorry, there's an incomplete sentence below; it should read:
I've noticed in this respect that db2taskd and db2stmm in list applications
output appear to be associated with the first user that connects to the
database, rather than the instance owner. This may be benign, but I've
amended startup scripts so that the instance owner establishes the first
connection. Secondly, RESTRICTIVE may be too restrictive! Consider instead
revoking just implicit schema and createtab authorities; the userspace1
tablespace privilege; and, in production environments, select privilege on
any of the authorisation catalog views, e.g. syscat.dbauth.
-----Original Message-----
From: Alex Levy
[mailto:db2udbdba-ezmlmshield-x58643566.[Email address protected]
Sent: 17 March 2008 11:19
To: LazyDBA Discussion
Subject: RE: Preparing for exam and totally lost
Hi Martin
I'm swotting for the advanced certified upgrade exams from V8 to V9 at the
moment and feel your pain!
Hope this helps:
A) You can quiesce an entire database if you have QUIESCE_CONNECT authority;
or you can connect to it in exclusive mode if no one else is already
connected; this is the equivalent of 'locking' the database but I think the
term 'lock' may have been used rather loosely here. For example, an
exclusive connection is not going to involve the lock manager, locklist,
maxlocks or any of that. I think.
B) When a lock is promoted, the old lock is replaced by the higher level
lock.
C) by default, PUBLIC are granted quite a number of authorities when you
first create a database (connect, implicit_schema,createtab,bindadd); plus
privileges for use of userspace1, select on system catalog tables, execute
on sysibm procedures, execute with grant on all sysfn functions, and bind
and execute for each successfully bound utility. Too many, Benny. If you
create the database with the RESTRICTIVE clause, all this will be taken
away, and will be reflected in the RESTRICT_ACCESS db cfg. I've noticed in
this respect that db2taskd and db2stmmd If you're migrating a database from
V8 to V9, check out the db2undgp command.
Good luck with the exams! Gulp - mine are Thursday week.
Alex Levy
Sustainable Software Ltd.
-----Original Message-----
From: Martin Metzker
[mailto:db2udbdba-ezmlmshield-x75325806.[Email address protected]
Sent: 16 March 2008 20:33
To: LazyDBA Discussion
Subject: Preparing for exam and totally lost
Hello world!
I'm preparing for the 730 and 731 tests and even though I spent quite a
while with DB2 I feel like I don't know anything. And I hope I can get a few
answers here.
There are the slides from the classes I attended which state that entire
databases can be locked exclusively. On the other hand, there is
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db29.do
c.perf/db2z_sizeoflock.htm where it says "A table space lock (the largest
size) controls ...". So what should I believe?
But there are more problems than simple contradictions. I'm also having
difficulties understanding the text. When promoting a lock, say from S to U,
am I releasing the S lock?
When I don't understand parts of the text I set up 1-2 testing tables to
play around a little. What's the deal with the group PUBLIC? I can grant
whatever privileges I want to PUBLIC and thus granting privileges to users I
don't know (yet). If I don't explicitly grant privileges, PUBLIC will only
be able to connect to databases and nothing more, or am I missing something?
The group PUBLIC is mentioned quite often even though it hasn't got any
rights, has it?
Thanks in advance, for any reply.
Cheers
Martin
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a dba
job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com To
unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a dba
job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com To
unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page