Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / December 2007

Tip: Looking for answers? Try searching our database.

Help with DB2 V8 on MSCS

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Scav - 19 Dec 2007 15:25 GMT
Helpful folks,

I have run into a glitch with a DB2 V8 single-partition install on a
new MSCS two-node hot standby cluster. After many stumbling blocks,
the instance and a test DB I have created on it can be successfully
failed over and back. However, I seem unable to connect to the DB2
test database from a windows client.

How is the CATALOG TCPIP NODE command specified on a client when you
are dealing with a cluster? I have tried specifying the REMOTE
<hostname> parameter by plugging in the DNS network name of the
cluster itself, and also tried the network name specified in the
Network Name resource of the DB2 group defined in Cluster
Administrator, but neither seems to work. I always get the generic
SQL30081N TCPIP connectivity error, the same error I receive when a
server is down or undefined to the network. I can successfully ping
both network names mentioned above, however. Do I need to specify the
SYSTEM parameter of the CATALOG command as well? If so, which value
would I use?

Any help or suggestions would be greatly appreciated.

Sean
dot.yet@gmail.com - 19 Dec 2007 18:06 GMT
from what i remember, all you need to do is to catalog against the
cluster ip.

so if your cluster ip is 192.168.10.25 and your DB2 service port is
50010, then you will issue the following command from the client
machines:

db2 "catalog tcpip node DB2CLS1 remote 192.168.10.25 server 50010"

db2 "catalog database testdb as testdb at node DB2CLS1"

db2 "terminate"

One thing though, make sure your database instance(s) is/are set for
communication over TCP/IP protocol

db2set DB2COMM=TCPIP

db2stop

db2start

Apart from that you should have specified the DB2 service port in the
services file and also in the database manager configuration
parameters.

db2 "update dbm cfg using SVCENAME db2cdb2_instance1"

db2cdb2_instance1 defined in the services file as follows:

db2c_instance1    50010/tcp

hth,
dotyet

> Helpful folks,
>
[quoted text clipped - 19 lines]
>
> Sean
Scav - 19 Dec 2007 18:44 GMT
dotyet,

Thanks very much for the quick reply.
Yes, I already verified that the services file contains entries that
are in sync with the DBM CFG parameters.
I think the problem may lie with what exactly is considered the
correct cluster.

In Cluster Administrator, the high-level name of the cluster is CLU02.
Under that are two groups, one for windows resources, and  another for
DB2 resources. My sysadmin tells me that these two groups represent
two separate clusters, which can be failed over independently. The
group associated with the Windows cluster has a network name resource
which has a name identical to the highest level in the tre-diagram on
the left of the tool :CLU02

Whereas, the DB2 group has a network name resource which has a name
value of DB201. The only doc I have which describes how to set this
( a redbook)  indicates that when using the db2iclus command to
migrate the instance into the cluster, the cluster name used in that
command is the name of the windows cluster, not the DB2 cluster. I
believe this command also sets the db2 enviroment variable DB2CLUSTER.

If anyone could shed some light on the relationships between all of
these aspects, or some doc that has more detail, I woudl be very
grateful.

Sean
The Boss - 19 Dec 2007 19:38 GMT
> dotyet,
>
[quoted text clipped - 24 lines]
>
> Sean

Disclaimer: I haven't any experience with MSCS, let alone combined with DB2.

That being said, I found a 42-page whitepaper by IBM on the subject that
might be useful:
"Implementing IBM DB2 Universal Database Workgroup Server Edition V8.2 with
Microsoft Cluster Server", to be found at:
ftp://ftp.software.ibm.com/software/data/pubs/papers/mscs_wse_82-ed.pdf

A similar but older 65-page paper for Enterprise Edition V8.1 can be found
here:
ftp://ftp.software.ibm.com/software/data/pubs/papers/esemcs.pdf

HTH

Signature

Jeroen

Scav - 19 Dec 2007 19:54 GMT
Jeroen,

I've studied the older one extensively, but never saw that newer doc.
Thanks for the tip.

Sean
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.