Managing Serviceguard Extension for SAP Version B.05.10, December 2012

If environment files exist in the home directory of the Sybase database user for the primary node,
create additional links on the secondary nodes.
Example:
su - syb<sid>
ln -s .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln -s .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
Sybase Database Step: SY1120
Adapt network information to reflect the virtual hostname/IP address used by the package; Adept
network for hostname changes with Sybase
Adapt network information to reflect the virtual hostname/IP address used by the package;
If the database was installed using the physical hostname or another virtual hostname in the
package, the server hostname settings must be adapted. In rare cases (usually only when the DB
was copied over from another host), the port information also needs to be changed.
In a SAP installation based on Sybase ASE network, information is stored in various places:
• User profile: User <dbsid> adm profile environment variables: dbs_syb_server and
dbs_syb_port.
Used by ABAP clients.
• SAP profiles: dbs/syb/server, dbs/syb/port
• JDBC connect string in config store (Java DBs only).
Used by Java clients.
• Interface file in /sybase/<DBSID>, master, and query entries
The master entry is used by the database server, the query entry by native DB clients based
on OCS. The database server binds only to the address of the (virtual) hostname specified
and not to the other addresses configured on the server.
NOTE: Keep the values in sync, otherwise clients may not be able to connect to the database
.
SAP Application Server Configuration
This section describes some required configuration steps that are necessary for SAP to become
compatible to a cluster environment. The following configuration steps do not need to be performed
if the SAP System was installed using virtual IPs. The steps are only required to make a non-clustered
installation usable for clustering.
• SAP ABAP Engine specific configuration steps
• SAP J2EE Engine specific configuration steps
SAP ABAP Engine specific configuration steps
Logon as <sid>adm on the primary node on which the Central Instance or the System Central
Services have been installed. The appropriate Serviceguard package should run on this host in
debug mode.
Installation Step: IS1100
For SAP Central Instance virtualization, change into the profile directory by typing the alias:
cdpro
In the DEFAULT.PFL change the following entries and replace the hostname with the relocatable
name if the ci component is going to be clustered. Example:
112 Step-by-Step Cluster Conversion