Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Managing MC/ServiceGuard Extension for SAP R/3: > Chapter 1 Understanding MC/ServiceGuard Extension for SAP

Server Consolidation

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

Server consolidation in an SAP R/3 environment is a strategy to put multiple SAP R/3 systems on a single physical server, a single host system. Since HP introduced HP-UX 11.00 with its 64-bit technology, addressing memory is no longer a limitation. The availability of 64-bit compiled SAP R/3 versions now enables a full blown 64-bit solution for SAP R/3. This results in having either multiple SAP R/3 clients running on a single SAP R/3 server or having multiple 2-tier SAP R/3 systems running on a single host. Additional SAP R/3 dialog instances can also run on the same server—in both scenarios.

Clustering a consolidated SAP R/3 server is different from clustering a single SAP R/3 instance. SGeSAP Version 3.1 supports dialog instance handling and shared memory resource handling on a consolidation host.

Dialog Instance Handling

With SGeSAP 3.1, SAP R/3 dialog instance treatment during CI / DB / DBCI package startup and stop has changed. SGeSAP now supports dialog instances on a host where CI / DB / DBCI packages are currently started as listed in Table 1-1 “Dialog Instance Treatment During Startup and Shutdown”.

Table 1-1 Dialog Instance Treatment During Startup and Shutdown

ASTREATRestartFinal_
Stop
ActiveRunpkg DBHaltpkg DBRunpkg CIHaltpkg CI
0000nopnopnopnop
1001CI-startnopst_if_nlnop
2010nopnopnopstop
3011CI-startnopst_if_nlstop
4100stopnopstopnop
5101stop CI-startnopstop startnop
6110stopnopstopstop
7111stop CI-startnopstop st_if_nlstop

nop = no operation
st_if_nl = start if not on local host

 

Shared Memory Resource Handling

SGeSAP 3.1 provides shared memory resource cleanup policies as listed in Table 1-2 “Shared Memory Cleanup Policies and their Effects”.

Table 1-2 Shared Memory Cleanup Policies and their Effects

CLEANUP_
POLICY
CI ResourcesDB ResourcesAppServer Resources
lazyno actionno actionno action
normaluse cleanipc to remove unused own resourcesunused Oracle SGA is removeduse cleanipc to remove unused own resources
strictremove any resource belonging to any SAP R/3 instanceremove any resource belonging to any databaseuser cleanipc to remove unused own resources

 

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.