First of all, this is a good reason to use the "one database per
instance" paradigm.
Secondly, there is some granular control of who can access a database
using the DB2 QUIESCE DATABASE command. Don't know, however, if you can
prevent a DBA from accessing it.
From the DB2 pubs:
"After QUIESCE DATABASE, users with sysadm, sysmaint, sysctrl, or dbadm
authority, and GRANT/REVOKE privileges can designate who will be able to
connect. This information will be stored permanently in the database
catalog tables.
For example,
grant quiesce_connect on database to <username/groupname>
revoke quiesce_connect on database from <username/groupname>"
Larry Edelstein
Serge Rielau wrote:
Serge Rielau wrote:
>ra*******@gmail.com wrote:
>>Hi
I am an Oracle DBA and now trying to get hands-on "DB2" databases. I
have small query...could anyone pls clarify???...
************************
In DB2 I have an instance with 5 databases in it. I now want to
completely "shutdown" 1 database and the rest 4 databases should be
avaialable...the database should not be avaialable to anyone and
including the DBA...is there a way of achieving this??
************************
A bit of an odd request. The DBA is all about managing databases...
Anyway here is one idea that may work:
Create a second DB2 instance for which only "you" have access.
To lock a database from the regular instance, simply activate it using
your special instance.
On second thought. I'm not sure if/how you can lock other DBA's out
throught the instance. After all DBA privilege is a _database_ privilege..
Maybe soemone else has a better idea or a way to finish my thought.
Of course you could always simply revoke DBADM from your DBAs....
Cheers
Serge