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

12. Only for Oracle installation:

If the directory /oracle/oraInventory already exists on the host created by another Oracle

installation in another SRP compartment, the next Oracle installation will have issues that

can be avoided by utilizing either of the next steps:

 Rename the existing directory but be very careful not to delete the directory

as it will be needed for future Oracle updates or upgrades. If an Oracle

upgrade is planned for later on, rename the directory back to

“oraInventory”.

 Start the Oracle RUNINSTALLER and Oracle patch runInstaller with the

option –invPtrLoc to define the new Oracle Inventory directory. For example:

RUNINSTALLER -invPtrLoc

/var/hpsrp/<compartment>/ora_ux10/db_1/oraInst.loc

13. After the SAP installation completes, configure the system as described in the section of this

white paper, “SAP modifications for SRP.”

Best practices for configuring SRP for the SAP production system

SAP modifications for SRP

To use the SAP system to its fullest potential, modify the SAP system as follows:

1. Rename the Transport Directory.

Use a unique name on the host for the new transport directory if several SAP systems exist on

the host. For example, the SAP ID could be used: /usr/sap/trans_<SID>.

Adapt the instance profile parameters DIR_TRANS to /usr/sap/trans_<SID> and

DIR_EPS_ROOT to /usr/sap/trans_<SID>/EPS and restart the system. This restart can be

done later when the SRP compartment is restarted.

Rename the transport directory path in transaction STMS to the new name.

2. For Systems >= 7.00 only, adapt startup framework as follows:

 Rename the sapservice file.

If several SAP systems are installed on your host, rename the sapservice file to something

unique. A unique hostname could be used to identify the different sapservice files. In this

document, the use of the SAP ID is assumed.

mv /usr/sap/sapservice /usr/sap/sapservice_<SID>

 If there are already several systems on the host with entries in the sapservice file, split the

file and create a new file for each system with only the respective entries for this system.

 To enable the automatic startup of the sapstartsrv service after a compartment start, the

sapinit script has to be relocated.

 Move the file /sbin/init.d/sapinit to the init.d directory of your compartment:

mv /sbin/init.d/sapinit /var/hpsrp/<compartment>/sbin/init.d

In the sapinit file edit the value for the parameter PATH. Change the value from “/sbin” to

“/var/hpsrp/<compartment>/sbin”

If the sapservice file was renamed, also change the value of SAPSERVICE_PATH to the new

sapservice name.

 Create a logical link to enable the automatic start of the sapstartsrv process:

ln –s /var/hpsrp/<Compartment>/sbin/init.d/sapinit

/var/hpsrp/<Compartment>/sbin/rc<n>.d/SAPINIT