Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration

Switching SGeSAP Off and On

Chapter 6 313

<rel-IP_name_of_db><DBID><shm|tcp> on.. <rel-IP_name_db>

in sqlhosts.soc with:

<local_hostname><DBID><shm|tcp> on.. <local_hostname>

SO060: Switch off step (Informix database only):

In the home directories of the users Informix and <sid>adm you can find

two files called .customer.sh and .customer.csh. Rename them to

prevent them from being executed the next time the database starts. For

example:

mv .customer.csh .customer.sh.off

mv .customer.csh .customer.csh.off

Execute these lines in both directories. Make sure not to change owner or

permissions of the files. Even though the home directory of <sid>adm is

usually local, it is enough to do this on only one machine of the cluster.

Choose the machine where you want to run the database later.

SO070: Switch off step:

Start all SAP Instances and the database as <sid>adm.

NOTE The automounter is still using the relocatable IP-addresses. You do not

need to turn off the automounter. Serviceguard and the packages remain

running and provide all necessary resources.

• Import the profiles with SAP ABAP Engine transaction code: RZ10.

• Check SAP setup. Ping(1M) to all application servers from the

Central Instance and the other way round. Transaction code: SM59

• Check that batch jobs in SAP are not scheduled to run on the

relocatable IP address. Transaction code: SM37

• Relocate printers to the real hostname. Transaction code: SPAD

• Check operational modes within SAP. You must setup new operation

modes for the new hostname. Transaction code: RZ04

• Do all testing described in the document SAP BC High Availability.