Hi,

I have some problems understanding how to configure db2 on a microsoft
cluster (MSCS).
I have installed db2 on the two nodes (node a, node b)
I have launched the db2mscs utility to migrate the db2 instance on the
cluster (it creates the db2group correctly).
I restore a db into DB2 instance from a backup image.
Everything seems to be ok. (...i have configured a client to connect
to the db using the network name of the cluster and the connection is
ok...when i "move group" everything it's working)

But...

I have some questions:

1) From a generic client i want to connect to db2 server for db-
administration. I must specify the network name of the cluster or the
ip of the active node?

2) The scheduler (task manager) ask me the name of the Db2 server. ( i
want to set some tasks like runstats and backup) When i specify the
network name of the cluster the task manager answers with an error (it
doesn't find the network resource).

3)I don't know how to configure the tools catalog and the
administration server for working in a MSCS scenario.

I look into HADR documentation and other manuals but i don't find
anything useful.

Can you help me?
(sorry for bad english... )

JH

On 8 Okt., 17:43, John Hopfield <Hopfi... (AT) freemail (DOT) it> wrote:
hi,
which DB2-Version ? (i'm running v8, v9 may be different)

did you migrate the Admin-Instance also:
something like:
DAS_INSTANCE = DB2DAS00
in the db2mscs.cfg file you used for running db2mscs ?

the doku for db2 in mscs is pretty nonexistent (last week i was in a
ibm-course "High Availability and Desaster Recovery" and still i have
pretty the same questions as you!!)

On 10 Ott, 13:16, jammann... (AT) gmail (DOT) com wrote:

I have db2 v8.2 Workgroup Server (fixpack 14).

Yes. I migrate the DAS_INSTANCE after migrating the DB2 instance
with a .cfg configuration file like this:

DAS_INSTANCE=DB2DAS00
CLUSTER_NAME=DB2CLS
DB2_LOGON_USERNAME=db2adm
DB2_LOGON_PASSWORD=****
GROUP_NAME=DB2 Group
DISK_NAME=Disk X:

But something seem to be incorrect...

For example: when i go into "Task center" and i specify the cluster
name
(or the IP of the cluster) , Task center don't find the TOOLS0
(TOOLS1...TOOLS2...ecc..)
database. (...after that error, it implicitly catalog a NODE of the
cluster....es: NODEA)
But i have created the tools catalog with the name TOOLSDB.
I don't know why "Task center" want to use TOOLS0....

So i don't know if my scheduled tasks will run correctly...

Maybe i MUST specify two times the scheduled tasks? (for NodeA *and*
for NodeB)?

Oh mamma...

Tnx
JH

On 10 Okt., 15:34, John Hopfield <Hopfi... (AT) freemail (DOT) it> wrote:

yeah its a mess!
whats your admin cfg ?

mine is (shorted):

db2 get admin cfg

Admin Server Configuration

Name of the DB2 Server System (DB2SYSTEM) = DB2CLS
Scheduler Mode (SCHED_ENABLE) = ON
Tools Catalog Database (TOOLSCAT_DB) = toolsdb
Tools Catalog Database Instance (TOOLSCAT_INST) = DB2
Tools Catalog Database Schema (TOOLSCAT_SCHEMA) = TOOLSCAT
Scheduler User ID = XXXX (the
db2user)
--------------------------------------------------------
in task center i always select "NODEA" (because the instance was -
befor the migration - created there) as scheduler-system (okay ist
illlogical) even when the Cluster is physical on NODEB and that works!
as runsystem i have to take "DB2CLS"

thats all trial-an-error, maybe i'm also doing something wrong but i
got the impression that db2 is not very well adapted do mscs (at least
in how the tools works / have to be configured)



No. the setup above works (at least for me)

On 10 Ott, 16:02, jammann... (AT) gmail (DOT) com wrote:
thanks a lot! it works.
i can create a scheduled task from "task center" directly on the
active node
specifying DB2CLUSTER as "runsystem".
After the failover i find the same scheduled task into NODEB and it
works.

i think that DB2 works well...but the documentation is sometime too
much complex for me.

Saluti
JH