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 / May 2006

Tip: Looking for answers? Try searching our database.

changed machine name - unable to work in DB2

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Baski - 27 Apr 2006 08:39 GMT
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???
Gert van der Kooij - 27 Apr 2006 08:52 GMT
> 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.
situ - 27 Apr 2006 09:22 GMT
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
Larry - 27 Apr 2006 13:41 GMT
> 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
Baski - 27 Apr 2006 13:55 GMT
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.
stefan.albert - 27 Apr 2006 15:30 GMT
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)
Baski - 28 Apr 2006 10:38 GMT
Oh. Is this the only way to do even in a production environment?????
Pierre Saint-Jacques - 01 May 2006 21:26 GMT
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.

Signature

Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515

> Oh. Is this the only way to do even in a production environment?????
 
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



©2009 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.