728x90
Question
How can I avoid my users connecting to my databases, when I am running db2dart on an offline databases?
Answer
Several options are available to stop users from connecting to the database when you run db2dart:
Only one of these options should be used.
- The most common simple way is doing a port change.
- Revoke connect privilege either for the group/user's is another option.
For Example :
REVOKE CONNECT on DATABASE FROM PUBLIC
Review the related URL below for examples on how to REVOKE database authorities.
Note : Revoking the CONNECT authority from a user does not affect any privileges that were granted to that user on objects in the database. If the user is subsequently granted the CONNECT authority again, all previously held privileges are still valid, assuming they were not explicitly revoked.
The CONNECT authority cannot be revoked from an authorization-name holding DBADM authority without also revoking the DBADM authority (SQLSTATE 42504). - Unset DB2COMM registry variable (which is set to TCPIP), by using the command:
db2 set DB2COMM=
db2stop
db2start
Review the related URL below for examples on how to set the DB2COMM variable.
Note: This option blocks users from connecting to the instance's databases remotely. You must also ensure that there are no other local connections. This will make all databases on the instance to become inaccessible. - Quiesce the database. A user with SYSADM authority must connect to the database and issue the following commands:
CONNECT TO database-alias
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
728x90
'Db2 > Db2 reference' 카테고리의 다른 글
db2pd 명령을 사용하여 모니터링 및 문제점 해결 (9.7) (0) | 2012.08.09 |
---|---|
Kernel parameter tuning on HP-UX, Oracle Solaris and Linux (0) | 2012.07.21 |
DB2 ODBC CLI driver Installation (0) | 2012.07.04 |
Setting up the ODBC environment (Linux and UNIX) (0) | 2012.05.06 |
Setting up the unixODBC driver manager (0) | 2012.05.06 |