Remote DB2 Setup Error

HCL Domino Domino Forum
1

I have been testing Domino 8.5 with DB2 for a few weeks now, with both installed and running on the same Windows machine. This has worked well.

I have now moved on to testing with a remote Domino installation and am having issues.

Once Domino has been configured to access the remote DB2 installation and then started, I get the following error:

–CLI ERROR--------------

cliRC= -1, line=400, file=db2grp.c

08/04/2009 15:33:25 <> Error managing DB2 groups

on violation.: 42S02 - [IBM][CLI Driver][DB2/NT] SQL0204N “GRP1”

name. SQLSTATE=42704 - 192.0.0.132.24069.090408143325(nevent)

I have ensured that the Windows accounts are correct and the remote Domino machine is configured in the same way as was the other one, and has DB2 runtime client correctly installed.

Any help would be much appreciated

Thanks

2

Subject: New server?

When you set up the remote configuration, did you start with a new Domino server, or just redirect the existing server to point to the remote DB2?

There are some initialization steps that Domino goes through (creating tables and groups) when you first set it up, and it sounds like you might have skipped that part.

3

Subject: Yes and No…

It wasn’t a new server, in the sense that it was a new install using an existing ID and therefore existing configuration.

Upon starting Domino, I did notice that it tried to recreate the DB2 database. I changed the settings so that it created a new DB2 database and then ran the DB2 commands to grant correct access to the new database.

4

Subject: Init problem

I think what is happening is that the old configuration info in the server doc does not agree with what is in the notes.ini of the new install, and that is causing confusion. In order for the init to work properly, Domino needs to create the DB2 database and do some initial setup inside it. It sounds like that process didn’t quite work properly, since you said you tried to help it along by doing some manual steps.

Try this:

  1. I’m assuming that there is no valuable data involved here, back up anything you need first…

  2. Make sure all the DB2 userid permission changes are properly set up as per the doc. permissions, group membership, etc.

  3. Make sure that the server doc contains the information (DB2 server name, db2 database name, etc) that is correct for your remote DB2 configuration.

  4. Shut down the new domino server

  5. Delete the new Domino server’s DB2 database on the remote DB2 server. you may need to do an uncatalog also.

  6. Start up the DB2 CLP on the domino server machine and connect to the remote DB2 server using the Domino server’s DB2 userid. issue a ‘create database ’ and verify that it completes correctly. If it does, then issue a ‘drop database <desired database name.’ to get rid of it. This verifies the connectivity to the DB2 server, and the permissions for Domino’s db2 userid. If you can’t do this step without errors, stop and correct the problems before continuing. Problems could include ‘database already exists’, permission issues, connectivity issues, etc.

  7. Edit the notes.ini for the new domino server, and change the DB2INIT value to CREATE, and verify that the other DB2-related values agree with what you put in the server doc.

  8. Start Domino, and it should create the database and initialize it

5

Subject: Working - My Fault!

Just to update, I was unable to connect to the DB2 server using the instructions provided in the last post, but this turned out to be due to me having Domino/DB2 runtime running on a Windows 2000 Server install, which is not actually compatible…

Reinstalled on a Windows 2003 Server and everything ran perfectly.

So, lesson is to always check requirements :slight_smile: