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??
************************

Pls advise.

Reg
Ram

ramana.gh@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.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

WAIUG Conference
http://www.iiug.org/waiug/present/Fo...Forum2006.html

Serge Rielau wrote:

ramana.gh@gmail.com wrote:

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
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

WAIUG Conference
http://www.iiug.org/waiug/present/Fo...Forum2006.html

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:
>

>
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

Hi,
the only thing I can think about is to uncatalog the DB.
If you want to use this DB again, you'll have to catalog it again (with
the same arguments - like the ones in the earilier catalog/create DB).

quiesce and connect in exclusive mode wont prevent a DBA to access the
DB...

ramana.gh@gmail.com schrieb:

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??
************************
>
Pls advise.
>
Reg
Ram

"DACTIVATE DB db_name" might work for you. Else, uncataloging would be
a solution, as mentioned in another reply.

Cheers,


ramana.gh@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??
************************
>
Pls advise.
>
Reg
Ram

If one does:
db2 connect to <dbnamein exclusive mode
I think trhat only that id can connect to the db and no one else, unless
they have the same id and pw.

This will mean that the db is activated but only that user can use it.

HTH, Pierre.



--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Larry" <larry@nospam.neta écrit dans le message de news:
t508h.3414$w%7.2958@newsfe11.lga...

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: