This note describes the configuration or installation of two SAP R/3 systems on one Windows NT server.
Several instances, parallel, NT, multiple, second
You want to install an additional central instance or an additional dialog instance on a Windows NT server that has an existing R/3 system. Plausible reasons for this could be:
- Easier administration of small MySAP landscapes
- Better utilization of large amounts of available resources in the Windows 2000 DataCenter (for example, main memory up to 64 GB or multi-processor up to 32 CPUs)
- 1. SAP note
===============
You must plan all resources carefully. Mutual effects with regard to performance and stability are to be expected.
It is technically possible to install and operate several SAP systems on one host without restrictions. We therefore provide support for a configuration of several SAP systems on the same host under the usual prerequisites. For this, take the following further recommendations into account:
- A combination of test, consolidation and production systems
on the same host is not recommended because of possible negative effects
on the stability of the production system.
All systems should represent components of one landscape.
- Furthermore, you should ensure in the case of several databases (RDBMS)
that all databases on a server come from the same manufacturer.
For further enquiries about this contact your database partner.
Your database partner can tell you which database systems
and versions can be installed together on one host.
If it turns out that performance problems are caused mainly by incorrect sizing during implementation (in other words, by inadequately assigning the individual server resources), support should be provided by the implementation partner.
- 2. General information
===============
Several SAP systems on one host have mutual effects with regard to stability and performance. These effects are difficult to diagnose.
The technical implementation for the simultaneous operation of several systems or instances on one host is a matter of sizing, that is, the precise planning of the required hardware resources and the corresponding adjustment of operating system, database and R/3 parameters. These result from the individual demands of the individual user and his or her initial situation. The required hardware resources and system parameters therefore must be accurately determined by the implementation partner (for example, the operating system partner, database partner or the SAP Basis adviser) together with the customer. For this, there are no general notes or recommendations on the part of SAP.
If you are discontented with the response times and the general performance of your R/3 production system setup and want a performance analysis on the basis of remote consulting by the SAP department Technical Competence Center, we urge you to read Note 61781. Make sure you also read the installation guide for your particular release/operating system/database combination.
This note does not claim to be complete.
- 3. Installation notes
=======================
- a) Memory Management
Releases 3.x
Note the memory requirement of the second R/3 system and, in the case of two central systems, the requirements of the second DB. Size your system correspondingly using Notes 68544 and 88416. Use the output of the tool sappfpar (point 'Worst case requirements') for determining NT Paging file requirements of every R/3 instance:
sappfpar check pf=
and adjust the instance profile and the paging file accordingly.
Releases 4.x
Note the value of the instance profile parameter PHYS_MEMSIZE which is used to calculate all memory management parameters that can be calculated dynamically. Adjust this value in accordance with the recommendations in Note 88416. Also notice the changed resource requirements for Release 4.0x in Note 98252.
- b) SAP processes
Note that only one SAPOSCOL process can run at a time and that bottlenecks and blocking statuses can occur in the case of simultaneous access to system resources that only exist once (see point 'General information').
- c) Other operating system resources
Every SAP R/3 instance is characterized by a unique instance number and a SID, which in no case may be assigned twice, since these characteristics are partially used for the description of system-specific R/3 resources (TCP ports).
In general, the installation tool (R3INST or R3SETUP) takes this into account, however, in case of problems, check the files .sapconf (usr\sap\trans, only for R3INST) and SERVICES (%windir%\system32\drivers\etc) as to whether the ports for SAP resources (sapdp00, sapgw00 and sapms
Instance numbers 98 and 99 are reserved (see Note 29972).
- d) Database compatibility
You generally should make sure that there is no conflicts between the chosen database platforms before the installation of the second system.
- e) R/3 release compatibility
No conflicts between the different R/3 update levels are known to exist. Since, however, only one SAPOSCOL can run on the server, you should make sure that it is a later R/3 release.
- f) Batch operation
No comments:
Post a Comment