Just to recap, I was trying to get WS Portal 5.1.0.1 running on Red Hat
Enterprise Linux 3 (Update 5) with DB2.


-- PRE-CONDITIONS: INSTALL NEEDED RHEL PACKAGES --

Before you start, be sure to go to this URL, as pointed out gdaswani, in a
previous post.

http://publib.boulder.ibm.com/infoc...f/inst_req.html

Click on the Section "Supported hardware and Software", then "WebSphere
Portal 5.1.0.1 requirements".  Navigate to "Supported Operating Systems
(required on Portal Machine)"

On RHEL - it will refer you to "Tech Note 1164634".  I believe you have to
perform those steps before installing the Portal Server.

http://www-1.ibm.com/support/docvie...uid=swg21164634

You want to make sure you have the packages installed recommended by this
tech note.

Also, make especially sure you have installed sharutils and
compat-libstdc++, to avoid this startup problem with server1:

http://www-128.ibm.com/developerwor...ead=27660&cat=9


-- RE-INSTALL DB2 CLEANLY --

Now, bite the bullet and completely re-install DB2. To de-install, first
do this:

- run the db2_deinstall script from the DB2 install CD/directory (where
you originally installed DB2 from)
- remove /opt/IBM/db2 dir completely
- remove the DB2 users (dasusr1, db2inst1, db2fenc1) from /etc/passwd and
/etc/shadow files
- remove home directories for these users - remove DB2 groups (dasadm1,
db2grp1, db2fgrp1) from /etc/group and /etc/gshadow - remove the line
beginning "fmc:2345" from /etc/inittab (if it exists) - remove all the db2
additions from the bottom of /etc/services - remove the directory /var/db2
- stop all DB2 processes (run ps -e | grep db2, remove all these processes)

The DB2 version I had previously installed was 8.2. Now I installed DB2
again, but this time from the WS Portal 5.1.0.1 release - it is cd9-3 for
Linux on Intel.

I installed using the command db2setup, which is graphical and a real pain
in the ASCII if you're trying to set it up remotely like I was. (You may
need to set up your ssh session to do X forwarding - reply to this post,
or email me on colin.macleod@ivata.com, if you need help with this.)

I left almost all default settings in the DB2 setup, and accepted the
"typical" install option.


-- RE-INSTALL WEBSPHERE PORTAL CLEANLY --

After installing DB2, I stopped my WebSphere_Portal and server1
application servers.

Just to be safe, I completely re-installed WS Portal 5.1.0.1, using the
default path settings (/opt/WebSphere...). Now, I know this is a pain and
takes ages, but it worked for me, so it was worth it.

After installing WS Portal, I was careful not to change any data in the
new install - this may be signficant, I don't know. I stopped the newly
created WebSphere_Portal and server1 application servers before going
further.


-- CREATE DATABASES --

Next, edit the file
/opt/WebSphere/PortalServer/config/helpers/transfer_db2.properties. I've
included mine here:

http://www.ivata.org/static/forums/migrateCSDB2

Just change the password token YOUR_PASSWORD_HERE to the password you used
when installing db2.

Then, and I think this may be the IMPORTANT part, I switched to csh as
root (I normally use zsh or bash) and ran the following (one line is
long, so watch for broken lines - I've added an extra newline after that
step):

source ~db2inst1/sqllib/db2cshrc
cd /opt/WebSphere/Portal/config
# long line ahead!
./WPSconfig.sh -DparentProperties=/opt/WebSphere/PortalServer/config/helper
s/transfer_db2.properties -DSaveParentProperties=true

./WPSconfig.sh create-local-database-db2


I then checked the DBs were installed by running each of these in
turn (still in csh):

./WPSconfig.sh validate-database-connection-wps
./WPSconfig.sh validate-database-connection-wmm
./WPSconfig.sh validate-database-connection-jcr
./WPSconfig.sh validate-database-connection-feedback
./WPSconfig.sh validate-database-connection-likeminds

They were all OK, apart from the jcr database - see the previous post at
the following URL to fix this problem:

http://www-106.ibm.com/developerwor...um=168#13726435


-- TRANSFER DATA --

So, once all of the validate-database-connection commands above were happy
(returning SUCCESSFUL), I ran the transfer command, still from csh:

./WPSconfig.sh database-transfer


After this, when I started WebSphere_Portal, it just worked.

If you're having trouble installing DB2 on WS Portal 5.1.0.1 on RH Linux -
It can work for you too. Be careful to follow the steps exactly - in my
case, I think it was either the c-shell (csh, instead of bash/zsh) that
fixed it, or the different version of DB2 (the one from the WS Portal
disks, not necessarily the latest version).

I'm so happy I could scream! Hope someone else finds this helpful :-)

--
Colin MacLeod
http://www.ivata.com

[ Post a follow-up to this message ]