changed machine name - unable to work in DB2

Baski

HI,

I have been using DB2 v8.2 on my windows 2000 machine. For some
reasons I changed my machine name. After that non of the services
(control center, CLP etc) are starting. When I try to invoke control
center, I am getting the following error:

----------------------------------------------------------
CLI0647E Error allocating DB2 environment handle, rc=-1.

Explanation:

This message is for your information only.

User Response:

No action is required.
-----------------------------------------------------------
When went through the IBM web site, some solution was suggested to be
done with the CLP, like UNCATALOG NODE GENERATE......
but i could not start the CLP itself. Probably they were for the
older/other versions.

Is there a way out???

Apr 27 '06 #1

Gert van der Kooij

In article <11**********************@g10g2000cwb.googlegroups .com>,
ma*********@gmail.com says...

HI,

I have been using DB2 v8.2 on my windows 2000 machine. For some
reasons I changed my machine name. After that non of the services
(control center, CLP etc) are starting. When I try to invoke control
center, I am getting the following error:

You might have a windows security problem. Check the directory security
settings for the DB2 installation directory.

Apr 27 '06 #2

situ

CHECK OUT WITH THIS I AM NOT SURE
IN DBM_CFG FILE THERE IS PARAMETER CALLED
"spm_name"
PUT YOUR NEW SYSTEM NAME FOR THIS PARAMETER

Apr 27 '06 #3

Larry

situ wrote:

CHECK OUT WITH THIS I AM NOT SURE
IN DBM_CFG FILE THERE IS PARAMETER CALLED
"spm_name"
PUT YOUR NEW SYSTEM NAME FOR THIS PARAMETER

I believe "spm_name" relates to sync point manager and may result in
unpredictable application behavior ... not sure.

Larry Edelstein

Apr 27 '06 #4

Baski

thanks...... any way for time being I have reverted back to the old
machine name and the DB2 is working fine. Need to find a proper
procedure beofre I do the name change again.

Apr 27 '06 #5

stefan.albert

DB2 grabs the machine name and stores it in more files (for the
instance/s).
You have to edit these files - but this can cause problems...
A secure way to do this (I think) is to drop the instances, change the
machine name and recreate the instances.
Then you catalog your databases again and it should work...
(This would also be the way to change the hardware for a DB2
environment)

Apr 27 '06 #6

Baski

Oh. Is this the only way to do even in a production environment?????

Apr 28 '06 #7

Pierre Saint-Jacques

You could Google this but I think that for Windowa there is a requirement
that the machine name be equal to the host name which is also equal to the
Windows system name. Thus the DB2SYSTEM name should also equal this but
that one I don't think is a requirement.
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Baski" <ma*********@gmail.com> a écrit dans le message de news:
11*********************@i39g2000cwa.googlegroups.c om...

Oh. Is this the only way to do even in a production environment?????

May 1 '06 #8