From: JY.Torres (john_yves_torres@yahoo.com)
Date: Thu Dec 22 2005 - 05:01:43 EST
Hi admins
May be it's of topics here, but I am sure one day, your manager will ask you quite the same questions, put several Oracle and/or SAP instances on the same vPar
The purpose is to plan several SAP instances on one uniq vPars, for low cost.
Before starting SAP is like a virtual database running on databases (DB2, Informix, Oracle and so on..)
===========================================================
Hi admins,
In my new role, I just got a new projet. "Mutualization of instance SAP on
HPUX 11i on vPars from a superdome 32way." For example, one Vpar (SAP ECC5,
Oracle 9.2.6.0) is like this :
___________________________________________________
HP-UX uxddig2a B.11.11 U 9000/800 1053141885 unlimited-user license
CPU Count: 3
CPU Speed: 875 MHz
CPU HW Support: 64-bit
Kernel Support: 64-bit
RAM Size: 3968 MB
...
___________________________________________________
The informations I got from SAP, Metalink and HP :
- 20 GB Swap
- 1.5 GB RAM for OS
- 2 Gb RAM per SAP instance
- 2 proc
And at least, 100 Gb diskspace for SAP datas for each SAP instance.
But, there is no answer on reasearch on the key word "mutualization"
So, I am looking for technical informations and the best practises for
sizing the stuff. (I find nothing on the Net). Any ideas will be appreciated
=====================================================
SAP just gave the following OSS notes.
21260,98252,153835,350251
The OSS notes says :
=======================================================
1. Several SAP systems on one computer
Using several SAP systems on one computer is particularly challenging in terms of the administration of such configurations. Above all, there will be opposing side effects in terms of release dependences and patch provision which are difficult to recognize. The analysis tools provided by SAP cannot be used without modifications with the configuration of several systems on one host. Therefore, if you want to use the services 'Early Watch' and 'Going Live Check' for configurations of several SAP systems on one computer, you should first inform SAP service about this situation.
If it turns out that performance problems are caused mainly by incorrect sizing during implementation (that is, by inadequately assigning the individual server resources), support should be provided by the implementation partner.
2. Instance numbers
SAP instances are identified uniquely by the host name and the two-digit SAP system number (instance number). The instance numbers must therefore (also in the first case) be different. Instance numbers 98 and 99 are not allowed. For HP-UX 11.0 the port belonging to instance number 75 is already used in the operating system. See also Notes 29972 and 94783 (ERROR => DpShMCreate DpIPCInit).
3. CPU
The required total CPU power for several systems on one host can exceed the sum of the CPU power for the same systems on separate hosts. Ask your hardware partner or operating system partner about mechanisms in the operating system that limit the competing consumption of available CPU power among the individual SAP systems and the third-party software.
4. Main memory
The amount of required main memory (RAM) must be higher than the sum of the same systems on separate hosts.
6. Swap Space
You can determine the Swap space requirement for every R/3 system using the SAPPFPAR program. The sum of these values, the Swap space of the operating system and other programs gives you the required Swap space on the computer. Make sure you define ample Swap space. See Note 38052 97179 and 153641
9. Operating system dependency
a) For Memory Management
For the operating system-specific aspects of Memory Management, see the following Notes:
HP-UX: 33576, 37537, 43427,106819, 100410, 113189
TRU-64: 32915, 30606
Windows NT: 28392
AIX: 37537, 78498, 95454
b) The SAP hardware partners have tested workload or resource management tools for use in SAP production environments.
c) The option to statically or dynamically partition software is also an alternative for the consolidated use of SAP software. Contact your hardware partner to request additional information about products and recommendations. SAP views these server partitions, which are running on one server and upon which several operating systems are running simultaneously using partitioning technology, as a standalone server. Make sure that sufficient resources are available to the SAP software (see above). If you are dynamically adjusting the CPU and memory resources available to the SAP system, take the cautionary measures mentioned in section 1 of the solution, since certain SAP monitoring tools are not set up for this adjustment.
d) For all usage types, the platform partner or the implementation partner is responsible for the sizing of the integrated solution.
SAP advises against installing test, development and production systems on the same operating system.
Cordialement, Kind regards, Yours sincerely
JY.Torres - Consultanting in SAP/ORACLE/HPUX ________________________________________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original transmission and its attachments without reading
or saving in any manner. Any other use of the email by you is prohibited. Private Fax : 1-425-740-1864
_______________________________________________________________
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:51 EDT