Best Practices for Deploying HP-UX Secure Resource Partitions (SRP) for SAP Whitepaper

18
Best practices for configuring SRP for de-installing an SAP system
In the life cycle of an SAP system, the last step is the de-installation of the system. With respect to SRP,
the de-installation can be accomplished in one of two ways.
1. De-install SRP compartment first.
If it is not necessary to have a high isolation level during the de-installation of the SAP system,
the easiest way is to delete the SRP compartment for the respective SAP system and start the
SAP de-installation from the INIT compartment.
2. De-install SAP system first:
For a successful de-installation of an SAP system within an SRP compartment, the rule file for
the installation (SAP_INST.h) is used. As de-installing an SAP system requires the same
privileges as an installation, call the script add_new_sap.h with the option INST.
The directories /sapmnt/<SID> and /usr/sap/ccms will not be removed by the sapinst.
The directory /sapmnt does not have full privileges to delete the directory <SID>. If there are
still other systems running on the host, the directory /sapmnt/<SID> has to be deleted
manually after sapinst finishes. For this deletion, full access to /sapmnt has to be given for
the SRP compartment and revised afterwards if the SRP compartment will not be deleted.
The CCMS directory /usr/sap/ccms may not be removed, if another SAP system is still using
this directory, so this error message can be ignored.
Directories created manually for using SRP, like /oracle/client_<SID> and
/usr/sap/trans_<SID> also have to be removed manually. Sapinst does not recognize non-
default directories.