Summary
Symptom
An upgrade from a 32-bit to a 64-bit SAP kernel or
database software is planned.
Reason and Prerequisites
To function properly, the SAP software often needs several GByte of accessible memory. While 32-bit software may use between 1.7 GB and 4 GB depending on the operating system, when you use a 64-bit version of the software, several terabytes of memory may be used. This prevents errors from occurring and enables administration of the SAP.com software. 64-bit software requires 64-bit-capable hardware.
Solution
The 64-bit SAP kernel is available as of SAP Basis Release 4.0. The SAP.com solutions which are based on Web Application Server 6.10 or higher are (with few exceptions) available only as 64-bit versions for operating systems that run on 64-bit-capable hardware.
To provide SAP.com 64-bit software, the source code of the SAP kernel was re-translated for 64-bit. The functions of the 64-bit and the 32-bit versions do not differ.
Basically, 64-bit software differs from the 32-bit version only in the different manner of accessing the memory. 64-bit software uses a 64-bit address pointer which, in theory, can access 18 billion GB of memory directly. Actually, a 64-bit application can access significantly less with the different operating systems and hardware available; however, it can still access several terabytes (that is, several thousand GB) of memory. This is considerably more than required by the SAP.com software components.
For a 32-bit address pointer, the address space is limited to about 4 GB; in reality, even less is available to the application. There are examples where this 4 GB limit prevents an efficient operation of an SAP.com system.
The latest information on SAP release planning is available on the SAP Website at http://sapnet.sap.com/platforms. For detailed information about the platform combinations released by SAP, see the SAP release notes under the componentXX_SER-SWREL.
All existing 32-bit 4.x releases are supported with 32-bit versions of the SAP kernel until further notice.
In addition to the basic prerequisites (64-bit hardware, 64-bit operating system, and 64-bit database) you must also consider the following aspects when preparing to install a 64-bit SAP kernel:
INSTALLATION TIPS
Installing the 64-bit SAP kernel for SAP Release 4.0B and 4.5B
You install the 64-bit SAP kernel for Release 4.0B and Release 4.5B manually. First, the system prerequisites described above must be fulfilled. To install the 64-bit SAP kernel, you simply have to replace all of the existing 32-bit executables in the SAP kernel with the corresponding 64-bit executables.
For example:
Initial state:
SAP Release 4.5B
SAP kernel 4.5B 32-bit
RDBMS ORACLE 8.0.5 64-bit
OS: HP-UX 11.00 64-bit
Target:
SAP Release 4.5B
SAP kernel 4.5B 64-bit
RDBMS ORACLE 8.0.5 64-bit
OS: HP-UX 11.0 64-bit
Procedure:
The procedure is described in detail in the following notes:
Note: 146248 Installation SAP R/3 4.0B 64-bit kernel
Note: 155355 Installation SAP R/3 4.5B 64-bit kernel
Installing the 64-bit SAP kernel as of SAP Basis Release 4.6B
As of SAP Release 4.6B, the installation tool R3SETUP is
delivered as a 64-bit version on the CD and is supported.
System copy with 64-bit SAP 4.5B (ORACLE)
When you use R3SETUP (32-bit version) to unload an Oracle database, R3SETUP cannot connect to the database if a 64-bit SAP kernel is used.
If you use the 64-bit SAP kernel for Oracle, you automatically use a 64-bit Oracle client library because only a 64-bit library can be loaded for a 64-bit SAP kernel. However, since the R3SETUP is only available as a 32-bit version up to Release 4.5B and since the 32-bit R3SETUP is not compatible with the 64-bit Oracle client library, the error mentioned above occurs during a system copy (in particular during the unload).
During loading, the system first unpacks the 32-bit SAP kernel to ensure that problems related to this do not occur.
However, if you still want to be able to perform a system copy (unload) using the 32-bit R3SETUP, proceed as described in Note 177724.
UPGRADE TIPS
Upgrading from a 32-bit SAP system to a 64-bit SAP system
The operating system upgrade and the SAP upgrade must be
performed separately (if possible), in addition to converting
from the 32-bit SAP kernel to the 64-bit R/3 kernel; this is to ensure that these phases
can be tested and completed individually.
As of 4.6C the change to a 64-bit SAP kernel will be supported during an upgrade.
That means that the individual phases such as operating system upgrade, database migration, and kernel exchange should be included in the planning.
Database
For a database, you need to check whether the binaries have to be replaced during the operating system upgrade. For example, the Oracle binaries for HP-UX 10.20 CANNOT run on HP-UX 11. Here, you must install the relevant Oracle software for HP-UX 11. When upgrading to a 64-bit Oracle 8 version you must first migrate to a 32-bit Oracle 8 version. Only after you have done this can you
implement the 64-bit RDBMS.
In addition, you must always first perform the SAP upgrade
before you replace the 32-bit SAP kernel with the 64-bit SAP kernel
because this also includes an adjustment of the UNIX kernel and the
instance parameter.
Sample scenario 1:
Initial state:
R/3 Release 3.1I
SAP kernel 3.1I (32-bit)
RDBMS: ORACLE 7.3.4 (32-bit)
OS: HP-UX 10.20 (32-bit)
Target:
R/3 Release 4.6B
SAP kernel 3.1I (32-bit)
RDBMS: ORACLE 8.0.5 64-bit
OS: HP-UX 11.0 64-bit
Procedure:
Option 1:
1) Upgrade the operating system to HP-UX 11.0
2) Install the 7.3.4 RDBMS binaries for HP-UX 11.0
3 Migrate to 8.0.5 32-bit RDBMS for HP-UX 11.0 (see the guide).
This step is required because a database migration from 7 to
8 must always take place using Oracle 8 32-bit.
4) Subsequently exchange RDBMS 8.0.5 32-bit with 8.0.5 64-bit.
This step can be performed only after the upgrade (before exchanging
the SAP kernel).
5) Upgrade the R/3 system to 4.6B with 32-bit SAP kernel PREPARE
unpacks the 32-bit tools automatically so that no manual
change is required.
6) Exchange the SAP kernel to 64-bit before the upgrade and adjust
the kernel parameters and instance parameters.
Option 2:
1) Migrate to 8.0.5 32-bit on HP-UX 10.20
2) Upgrade the operating system to HP-UX 11.0
3) Upgrade the RDBMS binaries to 8.0.5 64-bit for HP-UX 11.0
4) Upgrade the R/3 system to 4.6B with 32-bit SAP kernel
5) Exchange the SAP kernel to 4.6B 64-bit
Alternatively (if planning requires this):
Option 3:
1) Migrate Oracle to 8.0.5 32-bit (on HP-UX 10.20)
2) Upgrade the R/3 system to 4.6B with 32-bit SAP kernel
3) Upgrade the operating system to HP-UX 11 64-bit
4) Exchange the Oracle binaries to 8.0.5 64-bit
5) Exchange the SAP kernel to 4.6B 64-bit
Sample scenario 2:
Initial state:
R/3 Release 3.1I
SAP kernel 3.1I (32-bit)
RDBMS Oracle 7.3.4 (32-bit)
OS HP-UX 10.20 (32-bit)
Target:
R/3 Release 4.5B
SAP kernel 4.5B 64-bit
RDBMS Oracle 8.0.5 64-bit
OS HP-UX 11.0 64-bit
Procedure:
The procedure is similar to the one described for the first scenario.
However, during the upgrade, you do not have the option
to apply the 64-bit SAP kernel during the upgrade phase KX_SWITCH.
This is because the 64-bit SAP kernel for Release 4.5B
is not delivered on the upgrade CD.
Therefore, you must apply the 64-bit SAP kernel manually after the R/3 upgrade.
An upgrade from a 32-bit to a 64-bit SAP kernel or
database software is planned.
Reason and Prerequisites
To function properly, the SAP software often needs several GByte of accessible memory. While 32-bit software may use between 1.7 GB and 4 GB depending on the operating system, when you use a 64-bit version of the software, several terabytes of memory may be used. This prevents errors from occurring and enables administration of the SAP.com software. 64-bit software requires 64-bit-capable hardware.
Solution
The 64-bit SAP kernel is available as of SAP Basis Release 4.0. The SAP.com solutions which are based on Web Application Server 6.10 or higher are (with few exceptions) available only as 64-bit versions for operating systems that run on 64-bit-capable hardware.
- 1. 64-bit SAP.com, what's behind it?
To provide SAP.com 64-bit software, the source code of the SAP kernel was re-translated for 64-bit. The functions of the 64-bit and the 32-bit versions do not differ.
Basically, 64-bit software differs from the 32-bit version only in the different manner of accessing the memory. 64-bit software uses a 64-bit address pointer which, in theory, can access 18 billion GB of memory directly. Actually, a 64-bit application can access significantly less with the different operating systems and hardware available; however, it can still access several terabytes (that is, several thousand GB) of memory. This is considerably more than required by the SAP.com software components.
For a 32-bit address pointer, the address space is limited to about 4 GB; in reality, even less is available to the application. There are examples where this 4 GB limit prevents an efficient operation of an SAP.com system.
- 2. Advantages of the 64-bit technology for SAP.com.
- The administration of the SAP system is simplified considerably.
- The SAP software can scale the available hardware (RAM, CPU) to a much higher degree.
- 3. System requirements for 64-bit SAP.com
- a) 64-bit-capable hardware
A basic requirement for using 64-bit operating systems and 64-bit applications is 64-bit-capable hardware. In particular, the version of the processors (CPU) used determines the 64-bit capability of existing hardware. For detailed information, such as about the compatibility of the hardware with 64-bit operating systems, contact the person responsible at your hardware partner.
- b) 64-bit operating system
If you want to use 64-bit SAP software, you may have to upgrade to a 64-bit operating system. For releases, refer to the release notes that are available for each database for each SAP kernel release.
- c) 64-bit database
When using 64-bit SAP.com software, we recommend that you use a combination with a 64-bit database version (RDBMS). SAP, IBM, INFORMIX, and ORACLE databases are supported as 64-bit versions as of SAP release 4.0.
- 4. Exceptions
- a) Operating systems on servers with Intel Pentium processors.
The Intel Pentium processor is a 32-bit processor. For this reason, the SAP Software for Microsoft Server operating systems and Linux will remain available in the 32-bit version for the coming years. In the long term, SAP will also upgrade to the 64-bit version of the SAP software on these platforms; this requires 64-bit Itanium processors. When upgrading to the 64-bit version, we will also take into account the investment security of our customers.
- b) DB2 UDB for Unix and Windows (DB6):
Since the DB2 UDB database allows a mixed operation of 32-bit and 64-bit database client applications only as of version 8, SAP will provide 32-bit SAP Software in Release 6.x for DB2 UDB systems until the end of 2003.
- 5. Availability of 64-bit SAP.com solutions
The latest information on SAP release planning is available on the SAP Website at http://sapnet.sap.com/platforms. For detailed information about the platform combinations released by SAP, see the SAP release notes under the componentXX_SER-SWREL.
All existing 32-bit 4.x releases are supported with 32-bit versions of the SAP kernel until further notice.
- 6. Availability of the different 64-bit SAP.com solutions
- a) R/3
R/3 is available as of Release R/3 4.0.
- b) Business Information Warehouse (BW)
Business Information Warehouse is available with the 64-bit SAP kernel as of version 2.0A.
- c) Enterprise Buyer Professional (EBP), former BBP
EBP is available with the 64-bit SAP kernel as of Version 2.0A.
- d) Customer Relationship Management (CRM)
Customer Relationship Management is available with the 64-bit SAP kernel as of Version 1.2.
- e) Advanced Planner and Optimizer (APO)
APO is available with the 64-bit SAP kernel as of version 3.0A.
- 7. Possible combinations of 32-bit and 64-bit
- a) Possible combinations within an SAP system
For SAP releases as of 4.0B, a mixed use of 32-bit and 64-bit instances within one SAP system is supported at application server level. However, 32-bit and 64-bit SAP instances must reside on separate servers. Mixed use of 32-bit and 64-bit SAP instances on the same server is not supported.
For SAP releases as of 4.0, the combination of 32-bit SAP application servers with a 64-bit database server, and of a 32-bit database with 64-bit application servers is possible in principle. Releases for these combinations are granted in justified cases and are published in a suitable location (special note or at http://service.sap.com/pam). In the case of a mixed installation of a 32-bit SAP application server and a 64-bit database server or vice versa on a shared host, you need to make particularly sure that the SAP application server uses the correct database libraries. A manual reconfiguration may be required. The database upgrade guide describes how to proceed (see also Oracle Note 406140 or 539922).
- b) Possible combinations within an SAP.com system landscape
Transports with '#tp' or ''#R3trans' between 32-bit and 64-bit SAP systems are possible.
There are many differences between a 32-bit and a 64-bit SAP system. For example, the parameter settings of the HP-UX operating system kernel and SAP kernel that do not take into account a combined configuration of test and production systems. All features and functions that depend on the parameter settings cannot be sufficiently tested for a 64-bit production environment in a 32-bit test or development system. In particular, this includes the effect of the parameter settings on memory management and the performance of an SAP system.
For this reason, we recommend that you have at least one other 64-bit system available for each 64-bit production system within the transport track, where the availability of SAP kernel, operating system and database can be tested.
- c) Interoperability with 32-bit add-on products
For software products of third-party suppliers used with SAP software it is not important whether a 32-bit or a 64-bit SAP kernel is used. The use of a 32-bit or 64-bit SAP R/3 kernel is completely transparent for add-on products of third party suppliers as long as these products use SAP certified interfaces. 32-bit and 64-bit applications that directly access shared memory segments cannot be combined. For add-on SAP products with direct access to the shared memory you have to ensure that the bit size corresponds to that of the SAP kernel. For example, this applies to saposcol. With a 64-bit SAP kernel it is only possible to use a 64- bit saposcol.
- 8. Preparing to install a 64-bit SAP kernel
In addition to the basic prerequisites (64-bit hardware, 64-bit operating system, and 64-bit database) you must also consider the following aspects when preparing to install a 64-bit SAP kernel:
- a) Shared memory
Since there is virtually no limit on the shared memories in the case of a 64-bit SAP you can set large sizes for all buffers. For more information, see the recommendations in category III of Note 103747.
- b) Swap space
Addressing a very large memory requires the configuration of a correspondingly large swap space. To use a 64-bit SAP kernel you must configure at least 20 GB of swap space.
- c) Operating system kernel parameters
With a few exceptions, the parameter settings of the operating system kernel are identical for 32-bit and 64-bit. For information about the most important kernel parameters and the values that we recommend for them, see Note 146289. For HP-UX, also see Note 172747.
INSTALLATION TIPS
Installing the 64-bit SAP kernel for SAP Release 4.0B and 4.5B
You install the 64-bit SAP kernel for Release 4.0B and Release 4.5B manually. First, the system prerequisites described above must be fulfilled. To install the 64-bit SAP kernel, you simply have to replace all of the existing 32-bit executables in the SAP kernel with the corresponding 64-bit executables.
For example:
Initial state:
SAP Release 4.5B
SAP kernel 4.5B 32-bit
RDBMS ORACLE 8.0.5 64-bit
OS: HP-UX 11.00 64-bit
Target:
SAP Release 4.5B
SAP kernel 4.5B 64-bit
RDBMS ORACLE 8.0.5 64-bit
OS: HP-UX 11.0 64-bit
Procedure:
The procedure is described in detail in the following notes:
Note: 146248 Installation SAP R/3 4.0B 64-bit kernel
Note: 155355 Installation SAP R/3 4.5B 64-bit kernel
Installing the 64-bit SAP kernel as of SAP Basis Release 4.6B
As of SAP Release 4.6B, the installation tool R3SETUP is
delivered as a 64-bit version on the CD and is supported.
System copy with 64-bit SAP 4.5B (ORACLE)
When you use R3SETUP (32-bit version) to unload an Oracle database, R3SETUP cannot connect to the database if a 64-bit SAP kernel is used.
If you use the 64-bit SAP kernel for Oracle, you automatically use a 64-bit Oracle client library because only a 64-bit library can be loaded for a 64-bit SAP kernel. However, since the R3SETUP is only available as a 32-bit version up to Release 4.5B and since the 32-bit R3SETUP is not compatible with the 64-bit Oracle client library, the error mentioned above occurs during a system copy (in particular during the unload).
During loading, the system first unpacks the 32-bit SAP kernel to ensure that problems related to this do not occur.
However, if you still want to be able to perform a system copy (unload) using the 32-bit R3SETUP, proceed as described in Note 177724.
UPGRADE TIPS
Upgrading from a 32-bit SAP system to a 64-bit SAP system
The operating system upgrade and the SAP upgrade must be
performed separately (if possible), in addition to converting
from the 32-bit SAP kernel to the 64-bit R/3 kernel; this is to ensure that these phases
can be tested and completed individually.
As of 4.6C the change to a 64-bit SAP kernel will be supported during an upgrade.
That means that the individual phases such as operating system upgrade, database migration, and kernel exchange should be included in the planning.
Database
For a database, you need to check whether the binaries have to be replaced during the operating system upgrade. For example, the Oracle binaries for HP-UX 10.20 CANNOT run on HP-UX 11. Here, you must install the relevant Oracle software for HP-UX 11. When upgrading to a 64-bit Oracle 8 version you must first migrate to a 32-bit Oracle 8 version. Only after you have done this can you
implement the 64-bit RDBMS.
In addition, you must always first perform the SAP upgrade
before you replace the 32-bit SAP kernel with the 64-bit SAP kernel
because this also includes an adjustment of the UNIX kernel and the
instance parameter.
Sample scenario 1:
Initial state:
R/3 Release 3.1I
SAP kernel 3.1I (32-bit)
RDBMS: ORACLE 7.3.4 (32-bit)
OS: HP-UX 10.20 (32-bit)
Target:
R/3 Release 4.6B
SAP kernel 3.1I (32-bit)
RDBMS: ORACLE 8.0.5 64-bit
OS: HP-UX 11.0 64-bit
Procedure:
Option 1:
1) Upgrade the operating system to HP-UX 11.0
2) Install the 7.3.4 RDBMS binaries for HP-UX 11.0
3 Migrate to 8.0.5 32-bit RDBMS for HP-UX 11.0 (see the guide).
This step is required because a database migration from 7 to
8 must always take place using Oracle 8 32-bit.
4) Subsequently exchange RDBMS 8.0.5 32-bit with 8.0.5 64-bit.
This step can be performed only after the upgrade (before exchanging
the SAP kernel).
5) Upgrade the R/3 system to 4.6B with 32-bit SAP kernel PREPARE
unpacks the 32-bit tools automatically so that no manual
change is required.
6) Exchange the SAP kernel to 64-bit before the upgrade and adjust
the kernel parameters and instance parameters.
Option 2:
1) Migrate to 8.0.5 32-bit on HP-UX 10.20
2) Upgrade the operating system to HP-UX 11.0
3) Upgrade the RDBMS binaries to 8.0.5 64-bit for HP-UX 11.0
4) Upgrade the R/3 system to 4.6B with 32-bit SAP kernel
5) Exchange the SAP kernel to 4.6B 64-bit
Alternatively (if planning requires this):
Option 3:
1) Migrate Oracle to 8.0.5 32-bit (on HP-UX 10.20)
2) Upgrade the R/3 system to 4.6B with 32-bit SAP kernel
3) Upgrade the operating system to HP-UX 11 64-bit
4) Exchange the Oracle binaries to 8.0.5 64-bit
5) Exchange the SAP kernel to 4.6B 64-bit
Sample scenario 2:
Initial state:
R/3 Release 3.1I
SAP kernel 3.1I (32-bit)
RDBMS Oracle 7.3.4 (32-bit)
OS HP-UX 10.20 (32-bit)
Target:
R/3 Release 4.5B
SAP kernel 4.5B 64-bit
RDBMS Oracle 8.0.5 64-bit
OS HP-UX 11.0 64-bit
Procedure:
The procedure is similar to the one described for the first scenario.
However, during the upgrade, you do not have the option
to apply the 64-bit SAP kernel during the upgrade phase KX_SWITCH.
This is because the 64-bit SAP kernel for Release 4.5B
is not delivered on the upgrade CD.
Therefore, you must apply the 64-bit SAP kernel manually after the R/3 upgrade.
Header Data
| Release Status: | Released for Customer |
| Released on: | 21.09.2009 09:16:13 |
| Master Language: | German |
| Priority: | Recommendations/additional info |
| Category: | Upgrade information |
| Primary Component: | BC Basis Components |
| Secondary Components: | BC-UPG Upgrade - general |
| BC-OP-AIX IBM AIX | |
| BC-OP-BUL Bull AIX | |
| BC-OP-TRU64 HP Tru64 | |
| BC-OP-HPX HP-UX | |
| BC-OP-SUN SUN Solaris | |
| BC-OP-FTS-REL Reliant Unix | |
| BC-OP-FTS-SOL Fujitsu Solaris |
Affected Releases
Release-Independent
Related Notes
No comments:
Post a Comment