Case study 14: Sybase do not want to start after machine change name
  • Platform: HP-UNIX 11, Tru64 , Windows
  • Sybase ASE version: 12.5.x
  • Background story: I am receiving this complaint from the people who are working on notebooks which are used by many people. If some of them change the name of computer, Sybase do not want to start.
  • Task: Start Sybase after computer name has been changed.
  • Solution: I am going to describe how this problem has to be solved on Windows example. The main reason for such behavior lies in sql.ini file. When Sybase starts, it goes to sql.ini file and try to find out on which machine it works and on which port it has to listen. Here is one example of sql.ini:

    [DBSERVER_XP]
    master=NLWNSCK,dbserver,5004
    query=NLWNSCK,dbserver,5004

    [DBSERVER]
    master=NLWNSCK,dbserver,5001
    query=NLWNSCK,dbserver,5001

    [DBSERVER_BS]
    master=NLWNSCK,dbserver,5002
    query=NLWNSCK,dbserver,5002

    [DBSERVER_MS]
    master=NLWNSCK,dbserver,5003
    query=NLWNSCK,dbserver,5003


    In this example, computer name on which Sybase ASE is installed is dbserver. Names in the brackets are the names of Sybase servers(dataserver, backup server, monitoring server and extended procedures server).
    In case that computer name is changed to dbserver_new, sql.ini must be modified too, so Sybase could start. So, new sql.ini should look like as shown below:

    [DBSERVER_XP]
    master=NLWNSCK,dbserver_new,5004
    query=NLWNSCK,dbserver_new,5004

    [DBSERVER]
    master=NLWNSCK,dbserver_new,5001
    query=NLWNSCK,dbserver_new,5001

    [DBSERVER_BS]
    master=NLWNSCK,dbserver_new,5002
    query=NLWNSCK,dbserver_new,5002

    [DBSERVER_MS]
    master=NLWNSCK,dbserver_new,5003
    query=NLWNSCK,dbserver_new,5003


  • Remark: Do not change Sybase ASE servers names. The same procedure can be used on UNIX machines, but instead of sql.ini file, file interfaces has to be used.


Locations of visitors to this page
   
  powered by myself. DBA-Sybase 2006