Urs Meli

Short tipp: If you plan to enable db2 on a remote server, don't start the local DB2 command center.

I did it to test the connection between my domino server and the db2 server. Afterwards I was not able to enable the db2 on the domino server.
I got a strange communication error. And some hint about the catalog.

So I started the command center, removed my db2 node from the list. Tada! Now I could enable  the db2 on my domino.

Seems that Installpump is back in business.

see:

Here the link to the Homepage Softquest

DB2 integration is quite tricky. Converting a notes database to DB2 is simple. But the impacts can be horrible :-)
I tried it with a simple database, no problem.
A more advanced database with 350 views didn't work as expected. I was able to open the database but some views won't display.
I got a "index is corrupt...." message when I've tried to open it. Compact, fixup, updall nothing worked. I tried it with 3 different copies, all with the same result.

Either google nor the notes forum had a solution for that problem. Tomorrow I have to test it with some other databases...

Today I tested the NSFDB2. The installation was *cough* easy. The hardes part, was to find the Tutorial from last years course :-)

After 4h I got eveything up and running on my VMWare server. Setup looks like:

1 Domain Controller Win2003

1 Domino 8.0.2 Server

1 DB2 Enterprise 9.5 Server

Impressions so far:

• My first database got corrupted, when I transfered it to the DB2.
• When I transfered the second database, my db2 server ran out of hd space
• After expanding the disksize, I encountered several errors 1042c, 1065n
  It turned out that my db2 server lost the connection to my domain controller, therefor the db2 service account was not able to start.
  Rebooting the whole VMWare server, and checking all the network configurations, everything is now ok.

I hope it works all fine now.