No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


N2000 database failed to start normally due to change of hostname caused mismatch the hostname defined in database.

Publication Date:  2012-07-25 Views:  99 Downloads:  0
Issue Description
The requirement was submitted by customer to change the hostname of N2000 server, so when we changed the server name according to guide from support website, and restart the server but after that database failed to start normally. The version of N2000 BMS is as follows,

V200R010C02 installed with Solaris OS and database is SYBASE.
Alarm Information
Starting database prompt appeared that 00:00000:00008:2012/05/04 17:30:54.31 kernel  ninit: cannot find host N2000Server.
Handling Process
1.Change the hostname need to change  three files:  
  • /etc/hostname.ce0  “ce0” is the network card name  
  • /etc/hosts change the hostname in this file ,behind the name is exist loghost
  • /etc/nodename   this file don’t have any space  ,it will lead server can’t restart  
Example :change the hostname from MT122 to SiteAA.(ce0:the name of the network card)
  1. #echo “SiteAA” > /etc/hostname.ce0
#vi /etc/hosts
Change “MT122”in MT122 loghost to SiteAA
#echo “SiteAA” > /etc/nodename
All changed you can input the command will see:
a.  root@MT122 # more hostname.ce0
b.  root@MT122 # more /etc/hosts SiteAA loghost
c.  root@MT122 # more /etc/nodename

After this we should also change the file /opt/Sybase /interfaces     change the parameter as mentioned  bellow ,replace MT122 to the new server’s name as SiteAA.

#cd /opt/sybase/ 

 # vi interfaces

        master tcp ether MT122 4100
        query tcp ether MT122 4100

        master tcp ether MT122 4200
        query tcp ether MT122 4200

After all these changes restart the server.
#shutdown -y -g0 -i6

Root Cause
During hostname change operation, the complete procedure and risk involved was not cleared. These are some other parameters in database "interfaces" also need to be changed which was not changed before causing this problem.