Db2 – creating 2 database at the same time in db2

db2linux

Do you know whether it is safe to have in one shell user db2inst1 creating a database A and having another shell the same user creating at the same time database B?

create database A # shell 1
create database B # shell 2

I am using Linux/ Cent os with DB2 V 9.7 installed.

Best Answer

I'm also not quite sure why you are posting this without just attempting it, but yes, this will work without problem.

The only issues you might have are:

If the NUMDB database manager configuration parameter is small enough that you can't activate both databases at the same time (in addition to whatever other databases are activated within the DB2 instance).
If you use the AUTOCONFIGURE option for CREATE DATABASE with some silly default values so you exhaust system memory
System resource contention (disk, CPU) slowing the process down.

This is really an odd question – it's hard to image a scenario where you would need to create multiple databases simultaneously. Are you coming from a different DBMS (like MySQL or SQL Server), where the concept of a database is more like a schema in DB2?

Related Solutions

Db2 – Adding User access to DB2

My gut feeling is that you did not update user "john's" profile to invoke the DB2 profile setup. If you do not do this, then you won't have "access" to DB2 per say, even though the binaries are there.

So what you want to do is write a script that checks for your DB2 instance "home" profile script in your case it would be /home/db2inst1/sqllib/db2profile and if it is there, to invoke it.

if [ -f /home/db2inst1/sqllib/db2profile ] ; then
     . /home/db2inst1/sqllib/db2profile
     if [ ! $? = 0 ] ; then
          echo "Error setting up DB2 instance access"
     else
          echo "DB2 instance access set up"
     fi
fi

DB2 to require password each time

I believe you want the following

AUTHENTICATION = CLIENT
TRUST_ALLCLNTS = NO
TRUST_CLNTAUTH = SERVER

As you have changed above, the AUTHENTICATION=CLIENT, will force the client to authenticate. (Which can still use the OS as noted above.)

TRUST_CLNTAUTH = SERVER will cause the client to send the user id and password to the server for authentication when they are provided in the connect statement. This still does not force the client to require the user name and password as it can get them from the OS.

This is because DB2 will assume TRUST_ALLCLNTS as YES by default. This causes the server to assume all clients can be trusted and allow them to check against their respective OS's. So from what I know, to force the client to require a user name and password with the connect statement requires TRUST_ALLCLNTS to be set to NO. This will cause the server to not trust them and force them to send the user id and password to the server to authenticate against it.

Best Answer

Related Solutions

Db2 – Adding User access to DB2

DB2 to require password each time

Related Question