Switching SGeSAP Off and On

This section provides a brief description of how to switch off SGeSAP. Your individual setup may require additional steps that are not included in this document. Contact your HP consultant for additional information.

Switching off the SGeSAP Integration means that the SAP R/3 system will not run on the relocatable IP address. If you are performing anSAP R/3 upgrade, make sure that your SAP R/3 does not require any relocatable IP addresses. Switching off the SGeSAP Integration is the first step in SAP R/3 upgrade related work. This ensures full support from SAP R/3 during the upgrade procedure.

Switch Off SGeSAP

Refer to the following sections for descriptions of how to switch of SGeSAP.

Switching off SGeSAP starts with the following processes. Perform the steps described no matter which database you are using:

Perform the steps in one of these two sections, selecting the additional steps for ORACLE or INFORMIX as appropriate to your database.

Follow the steps in these sections to set up SAP R/3 internally. Follow these steps no matter which database your system has. They are always the same, independent from the underlying database:

Halt Packages

If the SGeSAPpackages are still running, halt them using:

cmhaltpkg <package>

If you use the two package concept, stopping the database package also brings down the Central Instance package. If you use an additional package that contains the transport directory, you do not need to stop that package. This allows any other SAP R/3 system that shares the transport directory to not be affected and continue running.

Turn on Debug Mode

Turn on the debug mode of the SGeSAP Integration. Then MC/ServiceGuard can provide all the filesystems and relocatable IP addresses, but the scripts do not start the database or SAP R/3. If a file named debug exists in /etc/cmcluster SGeSAP Integration packages start and no SAP R/3 specific script starts. For example:

You must create a debug-file on all nodes of the cluster:

touch /etc/cmcluster/debug

Using this command prevents the SAP R/3 system from starting up on the other host as the result of a failure. This ensures that SAP R/3 does not run with incorrect profiles.

If you have more than one SAP R/3 system within the cluster you can also turn on debug mode for specific systems. If the file /etc/cmcluster/<SID>/debug exists, the additional scripts (start and stop SAP R/3) for this system are not started. Other systems are controlled as usual by MC/ServiceGuard.

Start Packages

Start the packages with:

cmrunpkg <package>

Remember that with the debug mode turned on, the Central Instance package of the two package concept is not triggered by the database package. You have to start it manually.

Additional steps for ORACLE

Additional steps for switching off SAP R/3 with an ORACLE database include:

Backup Files
Save the configuration files so you can switch on the SGeSAP Integration again. Save the files as user <sid>adm. This list of files you have to save include:
listener.ora /usr/sap/trans/bin/TPPARAM tnsnames.ora /usr/sap/<SID>/SYS/profile/DEFAULT.PFL /usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<INSTNR>
Stop Listener
If you have an oracle database check to see if the listener is running. If it is, stop it as user ora<SID> with:
lsnrctl stop
If you have configured names for the listeners, which allows you to have more than one listener running, make sure to specify the correct name:
lsnrctl start <LISTENERNAME>
Change Profiles
The references of the relocatable name must be changed to the real hostname in the following files:
listener.ora tnsnames.ora /usr/sap/<SID>/SYS/profile/DEFAULT.PFL /usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<INSTNR> /usr/sap/trans/bin/TPPARAM
NOTE: /usr/sap/trans/listener.ora is a link to /etc/listener.ora.
Start Listener
Start oracle listener as oracle user with:
lsnrctl start <LISTENERNAME>

Additional steps for INFORMIX

Additional steps for switching off SAP R/3 with an INFORMIX database include:

Rename Customer Shell Scripts
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.

Backup Files

Save the configuration files so you can switch the SGeSAP Integration on again. The list of files you have to save includes:

/informix/<SID>/etc/onconfig.<rel-IP_name_of_db>.<DBID>
/informix/<SID>/etc/sqlhosts.soc
/usr/sap/trans/bin/TPPARAM
/usr/sap/<SID>/SYS/profile/DEFAULT.PFL 
/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<INSTNR>

Change Profiles

Replace any reference to the relocatable IP address(es) in the files you previously saved. Insert the local hostname of your machine. This is the name you get when you use the hostname command.

As informix user go to /informix/<SID>/etc. In the onconfig file replace the:

<rel-IP_name_of_DB><INFORMIX_DBID><shm|tcp>

entries with:

<local_hostname><INFORMIX_DBID><shm|tcp>

entries, for example:

DBSERVERNAME <local_hostname><sid>shm 
     # Name of default database server
DBSERVERALIASES <local_hostname><sid>tcp 
     # List of alternate dbservernames

Afterwards rename the file:

mv onconfig.<rel-IP_name_db>.<DBID> \
onconfig.<local_hostname>.<DBID>

In the same way replace the appropriate entries:

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

in sqlhosts.soc with:

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

As user <sid>adm replace any occurrence of:

<rel-IP_name_of_db> or <rel-IP_name_of_ci>

with:

<local_hostname>

in:

/usr/sap/trans/bin/TPPARAM
/usr/sap/<SID>/SYS/profile/DEFAULT.PFL 
/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<INSTNR>

Check SAP R/3

To check SAP R/3:

Start all SAP R/3 Instances as <SID>adm.
NOTE: The automounter is still using the relocatable IP-addresses. You do not need to turn off the automounter. MC/ServiceGuard and the packages remain running and provide all necessary resources.
Import the profiles within SAP R/3. Transaction code: RZ10.
Check SAP R/3 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 R/3 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 R/3. You must setup new operation modes for the new hostname. Transaction code: RZ04
Do all testing described in the document SAP BC High Availability.

Backup Files Again

After successfully finishing all tests, take another copy of the files you saved in the Sections "“Additional steps for ORACLE”" or "“Additional steps for INFORMIX”". Refer to this step for a list of the files.

You previously renamed the onconfig file if you have an INFORMIX database. You might need this second backup for reference. If you plan to switch on the SGeSAP Integration again at a later point in time, make sure that no additional changes in the files occurred in the between times. Any changes would be lost if you replaced the altered files with the backup of the originals.

Use the backup created in this step, the backup of the altered files, later on for comparison with current active versions.

Switch On SGeSAP

Refer to the following sections for descriptions of how to switch on SGeSAP.

Stop SAP R/3

Stop the database and SAP R/3 manually on all hosts in and outside of the cluster with:

stopsap all

For ORACLE Database

Restore Profiles:

Check to see if the listener is running. Stop the listener process as ora<SID>:
lsnrctl stop <LISTENERNAME>
Restore all profiles with the versions that use relocatable addresses. You saved these versions when you switched off the SGeSAP. If appropriate, incorporate any changes that occurred to these files during the switch off process. You can use diff and the second backup you took to easily find out if anything changed.

Restore the following files together with their destination paths:

listener.ora 
/usr/sap/trans/bin/TPPARAM 
tnsnames.ora 
/usr/sap/<SID>/SYS/profile/DEFAULT.PFL 
/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<INSTNR>

Restart the listener as oracle user:
lsnrctl start <LISTENERNAME>

For INFORMIX Database

Restore Profiles

Restore all profiles with the versions that use relocatable addresses. You saved these versions when you switched off the SGeSAP. If appropriate, incorporate any changes that occurred to these files during the switch off process. You can use diff and the second backup you took to easily find out if anything changed.

Restore the following files together with their destination paths:

/informix/<SID>/etc/onconfig.<rel-IP_name_of_db>.<DBID>
/informix/<SID>/etc/sqlhosts.soc/usr/sap/trans/bin/TPPARAM 
/usr/sap/<SID>/SYS/profile/DEFAULT.PFL 
/usr/sap/<SID>/SYS/profile/<SID>_DVEBMGS<INSTNR>

Rename Customized Files

As informix user perform the following from your home directory:

rm  /informix/<SID>/etc/onconfig.<local_hostname>.<DBID>
mv .customer.csh.off .customer.sh
mv .customer.csh.off .customer.csh

As <sid>adm in home directory:

mv .customer.csh.off .customer.sh
mv .customer.csh.off .customer.csh

Start SAP R/3

Start SAP R/3 as <SID>adm using:

startsap all

Turn Off Debugging Mode

Delete /etc/cmcluster/debug and/or /etc/cmcluster/<SID>/debug if they exist.

Reconfigure SAP R/3

To reconfigure SAP R/3:

Import the profiles within SAP R/3. Transaction code: RZ10.
Check SAP R/3 setup. Try to ping(1M) to all application servers from the Central Instance and the other way round. Transaction code: SM59.
Check that the batch jobs in SAP R/3 are scheduled to run on the relocatable IP address not on the local hostname. Transaction code: SM36
Relocate printers to the relocatable name. Transaction code: SPAD
Check operational modes within SAP R/3. You must setup operation modes for the relocatable name.
Do all the testing as described in the document SAP High Availability.