DOMINO AND DB2
If the DB2 server is remote, the computer on which the Domino server is installed must have at least the DB2 Run-Time Client installed on it.
Note It could also have ESE installed.
Example of a remote configuration
In this example there are two computers:
On computer A we are using a db2instance named: db2inst2
On computer B we are using a db2instance named: db2inst5 (port 50003 )
The Domino server is started with transaction logging enabled.
During server enablement, the Domino Administrator client creates a DB2 node on computer A, using the information supplied to the Domino Administrator client.
Manually cataloging the DB2 database that the Domino server will use
Complete these steps to ensure that the Domino server uses a db2node to get to the db2database.
1. To catalog a node, enter the following:
db2 catalog tcpip node nodename remote machine.notesdev.ibm.com server 50003
Note This <node name> is in the Domino server's NOTES.INI setting DB2INSTANCE=nodename.
In the DB2INSTANCE db2inst2 on computer A, you will see the following information indicating that the DB2 node has been created:
$ id
uid=5102(db2inst2) ...
$ db2 list node directory
Node Directory
Number of entries in the directory = 1
Node 1 entry:
Node name = NODEAA
Comment = nodeAA
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = p5viper.notesdev.ibm.com
Service name = 50003
db2 catalog database adomino as Domino at node nodename authentication server
uid=5105(db2inst5) ...
$ db2 list database directory
System Database Directory
Database 1 entry:
Database alias = ADOMINO
Database name = ADOMINO
Local database directory = /local1/db2inst5
Database release level = b.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
Database alias = DOMINO
Directory entry type = Remote
Authentication = SERVER
Catalog database partition number = -1