setting up non-root DB2 instance on RHEL5
I am trying to setup RTC server and DB2 Express on a RHEL5 machine. I am trying to complete the installation as a non-root user and have run into a snag.
I used the Install Manager to install the packages from the downloaded zip file of RTC Standard. Following the instructions, I used the launchpad to start db2setup to install DB2 Express.
The instructions mention to take note of the userID, password, and port. The only information I received from the installation was the port number. I can only assume that the userID is my own, db2admin, or db2inst1.
The steps for setting up the DB2 database, say that I should use an account that have sysadmin authority on the DB2 database. The is a tip that says to sudo to db2fenc1.
I do not have access to sudo on this machine. Should it matter if I am trying to do a non-root install? Is there a way around this by configuring the database?
In any case, I proceeded to run the "db2 create" command without problems. Afterwards, I run into problems trying to run the "repotools.sh -createTables" command. It complains about not being able to connect to the database without root access.
Any help would be appreciated.
Thanks,
Jeff Taylor
I used the Install Manager to install the packages from the downloaded zip file of RTC Standard. Following the instructions, I used the launchpad to start db2setup to install DB2 Express.
The instructions mention to take note of the userID, password, and port. The only information I received from the installation was the port number. I can only assume that the userID is my own, db2admin, or db2inst1.
The steps for setting up the DB2 database, say that I should use an account that have sysadmin authority on the DB2 database. The is a tip that says to sudo to db2fenc1.
I do not have access to sudo on this machine. Should it matter if I am trying to do a non-root install? Is there a way around this by configuring the database?
In any case, I proceeded to run the "db2 create" command without problems. Afterwards, I run into problems trying to run the "repotools.sh -createTables" command. It complains about not being able to connect to the database without root access.
Any help would be appreciated.
Thanks,
Jeff Taylor
One answer
jmtaylor wrote:
Yes, the userID is your own.
That tip is applicable when DB/2 is installed as root. You will not
need to use sudo when doing a non-root install.
Unfortunately, there is still one step that has to happen as a root
user. A root user has to run the db2rfe command to enable
authentication. If you're able to do this, the steps are:
1. Edit /home/<userid>/sqlllib/instance/db2rfe.cfg
Set ENABLE_OS_AUTHENTICATION=YES
2. As a root user:
cd /home/<userid>/sqlllib/instance
./db2rfe -f db2rfe.cfg
Thanks,
Craig Chaney
Jazz Server team
I am trying to setup RTC server and DB2 Express on a RHEL5 machine. I
am trying to complete the installation as a non-root user and have
run into a snag.
I used the Install Manager to install the packages from the downloaded
zip file of RTC Standard. Following the instructions, I used the
launchpad to start db2setup to install DB2 Express.
The instructions mention to take note of the userID, password, and
port. The only information I received from the installation was the
port number. I can only assume that the userID is my own, db2admin,
or db2inst1.
Yes, the userID is your own.
The steps for setting up the DB2 database, say that I should use an
account that have sysadmin authority on the DB2 database. The is a
tip that says to sudo to db2fenc1.
I do not have access to sudo on this machine. Should it matter if I am
trying to do a non-root install? Is there a way around this by
configuring the database?
That tip is applicable when DB/2 is installed as root. You will not
need to use sudo when doing a non-root install.
In any case, I proceeded to run the "db2 create" command
without problems. Afterwards, I run into problems trying to run the
"repotools.sh -createTables" command. It complains about
not being able to connect to the database without root access.
Unfortunately, there is still one step that has to happen as a root
user. A root user has to run the db2rfe command to enable
authentication. If you're able to do this, the steps are:
1. Edit /home/<userid>/sqlllib/instance/db2rfe.cfg
Set ENABLE_OS_AUTHENTICATION=YES
2. As a root user:
cd /home/<userid>/sqlllib/instance
./db2rfe -f db2rfe.cfg
Thanks,
Craig Chaney
Jazz Server team
Any help would be appreciated.
Thanks,
Jeff Taylor