ESE 8.1 install on Linux

[JasonFriedman80238]

I'm following the instructions from "Up and Running With DB2 for
Linux". I created these users/groups:

db2inst1:x:201:101::/home/db2inst1:/bin/bash
db2fenc1:x:202:102::/home/db2fenc1:/bin/bash
dasusr1:x:203:103::/home/dasusr1:/bin/bash

db2iadm1:x:101:db2inst1
db2fadm1:x:102:db2fenc1
db2asgrp:x:103:dasusr1

I untarred db2-udb-ee-8.1-linux-x86.tar, changed to the
009_ESE_LNX_32_NLV directory, and ran db2_install. I got a bunch of
output like this:

Preparing...
##################################################
IBM_db2msen81
##################################################
IBM_db2cliv81...

and no errors.

I executed:
/opt/IBM/db2/V8.1/instance/db2icrt -u db2fenc1 db2inst1
and it says that the instance already exists (someone attempted an
install earlier).
db2iset -l shows the instance "db2inst1" exists.

I execute:
/opt/IBM/db2/V8.1/cfg/db2ln

I configure TCP/IP.

The next instruction is to execute sqllib/db2profile as the instance
owner, but there is no sqllib directory anywhere on the machine.

Where is that directory, or what can I do next?

[JasonFriedman80238]

Okay, realized that sqlilib was manually deleted.
So, I dropped the db2inst1 instance and re-created it, and now I have
my sqllib directory.

Now I try:
../sqllib/db2profile
db2 update dbm cfg using SVCENAME db2c_db2inst1

and receive:
SQL10007N Message "-1390" could not be retrieved. Reason code: "1".

echo $DB2INSTANCE
db2inst1

[Harlin]

I am somewhat new on the job and have been put into the position to
have to learn DB2 and learn it more so on Linux. I tried running that
same method of install and it gave me headaches. The very best way for
me to do it was like this:

Run ./db2setup
If no suitable JVM was found, then I went into the 'java' dir and
installed the IBMJava SDK RPM. After this, I ran ./db2setup

After this, an IBM DB2 start-up screen showed and then I simply
installed it as I would on a Windows machine.

I found it better to not create the users and groups and just let the
setup program do all of that. It was much easier and gave me just as
much functionality and flexibility as if I would have done it myself.
However, if you're the type who likes to bang their head and learn the
hard way, do the individual rpm installs (nothing wrong with that
method if you like it).

After this, log into your db2 instance user's account on VNC, SSH or
directly on the box if you like, and you'll be able to run db2cc (DB2
Control Center) rather easily. If you don't allow DB2 setup to do this,
you'll have to set all the paths and Java class paths yourself to get
it run properly.

Any other questions, please come back or feel free to email me
directly. I can use some help and don't mind providing it as we are in
the middle of converting Windows Websphere applications over to Linux.
This of course includes DB2 and IDS as we are an exclusive IBM shop.

Good Luck!

Harlin Seritt

[Dan Scott]

Hi Jason:

Try:

.. ./sqllib/db2profile

(yes, dot, space, dot/sqllib/db2profile -- the first dot says "apply
all of the environment changes to the current shell"; if you leave that
dot out, then the environment changes apply only for the duration that
the db2profile script runs and therefore none of the settings are
applied).

source /home/db2inst1/sqllib/db2profile also seems to work.

Dan

[JasonFriedman80238]

Thanks everyone for their replies.
.. ./sqllib/db2profile
worked.

Then, I did:
/opt/IBM/db2/V8.1/instance/dascrt -u dasusr1
DBI1103E The Administration Server already exists.

and:
db2 create tools catalog toolscat create new database toolsdb
SQL22205C The DB2 Administration Server encountered an unexpected
error while
executing a request.

[Darin McBride]

JasonFriedman80238 wrote:

Thanks everyone for their replies.
. ./sqllib/db2profile
worked.
Note that you should not do this as root - only as a non-root user. Running
db2 commands as root can cause weird side effects (such as files being
created with the wrong permissions, basically preventing anyone else,
including the instance owner, from doing anything with that file).
Then, I did:
/opt/IBM/db2/V8.1/instance/dascrt -u dasusr1
DBI1103E The Administration Server already exists.
Same issue as your regular instance - you probably removed the ~dasusr1/das
directory. I think dasdrop will clear that out.
and:
db2 create tools catalog toolscat create new database toolsdb
SQL22205C The DB2 Administration Server encountered an unexpected
error while
executing a request.

Run this last command as your instance owner, or someone with sufficient
permissions (sysadm), not as root.