Managing HP Serviceguard Extension for SAP for Linux, December 2013

system to the newly generated ones. This step is usually straight-forward and is not covered
here.
Adapting each occurrence of the old instance hostname with the new instance virtual hostname.
This concerns filenames as well as configuration values containing hostname strings in the
files. For a Java based instances, this will also require the use of the SAP configtool”.
The cluster conversion of a central instance (DVEBMGS with Message and Enqueue Server) into
a System Central Services (ASCS) instance and Enqueue Replication Service (ERS) Instance is not
covered here. SAP Note 821904 has details on how to accomplish such a conversion and/or the
reinstallation of instances using the High Availability installation option of the SAP sapinst
command.
5.6.1 Converting an existing SAP instance
Adapt the SAP instance profile names by renaming SID_Instance_oldhost to
SID_Instance_newvirthost
SAP profile names will also referenced in the SAP start profile of the instance. In the SAP start
profile look for _PF = or _PFL = entries and change the right hand side accordingly.
Adapt all SAP profile entries referencing the old hostname of the converted instance. These
depend on the type of instance. Possible profile entries might be:
SCSHOST
j2ee/scs/host
enque/serverhost
rdisp/mshost
The SAPGUI also contains connect strings referencing oldhost. These must be converted to
the newvirthost names.
Change properties Java instance referencing the old host using the configtool.
5.6.2 Converting an existing database
Adapt entries in the database configuration files listed in the Table 19 (page 68) table
Adapt all SAP profile entries referring to the DB (not all entries below need to exist).
SAPDBHOST
j2ee/dbhost
Other DB specific entries with a dbs/<dbtype>prefix
For example, dbs/syb/server
Java DB connect URL configuration properties (to be modified using the SAP configtool)
For additional information related to this hostname conversion process can be found in SAP
notes 8307, 757692, 1275273 and 1033993.
5.6 Cluster conversion for existing instances 87