June 10, 2011 - Oracle Database Machine has been certified by SAP
ALL SAP products based on SAP NetWeaver 7.0 are certified .
DBM can only be used to host the SAP database level. SAP instances cannot run on DBM — they run on separate servers connected to the DBM network. In SAP terminology, this is called a three-tier architecture. This allows you to use any combination of platforms on levels. In a 3-tier configuration, the database level can be easily replaced with DBM without changes at other levels. SAP administrative tools (BR * Tools) and SAP Central Services can be installed on DBM.
On 10.06.2011 there is no possibility of the initial installation of SAP on DBM. Only existing database can be transferred.
• Constantly changeable SAP activity document on DBM: SAP Note 1590515
• New installations of NetWeaver 7.0 work only with Unicode, therefore both database encodings should be only UTF8
• There are restrictions for non-Unicode installations.
• When migrating to DBM, the encodings must match the encodings of the original system. The encoding will be either WE8DEC or UTF8, the national encoding is only UTF8.
• When upgrading, two bundles must be installed together: “Oracle Exadata Bundle Patch” and “SAP Exadata Bundle Patch”. The second version must match the first version.
• SAP Application Servers and BR * Tools use a shared file system exported from the outside. If the file system was implemented on the database server, then you need to use another server or NAS for this (Recommended by ZFS-Appliance). HA-NFS is desirable.
• In an SAP installation, SAP Central Services components are protected using cluster solutions. If in the old installation their protection was provided by the cluster software of the database server, then the following options are possible:
Two additional x86 machines with Solaris and Solaris Cluster;
Installing and integrating them with Oracle Clusterware on DBM.
')
About Exadata Features for SAP
The SAP BR * Tool administration tool does not support HCC compression. SAP itself does not use direct downloads, which are necessary for HCC compression, but uses conventional single-line data inserts. In SAP, there is formally no division into operational data and archived data. All this greatly limits the use of HCC for SAP, but does not prevent.
DBFS is not supported by SAP.
All other features are fully supported and do not require additional settings. But you should know that any SAP application (SAP BW) makes extensive use of indices, with infrequent full scans, so you should not expect the use of Smart Scans and the corresponding productivity growth.
Smart Flash Cache and wide I / O channels will provide the highest level of I / O. I / O Resource Manager provides I / O scheduling, which is very important when using DBM to consolidate both various SAP applications and SAP applications with other applications.
DBM can only be used to host the SAP database level. SAP instances cannot run on DBM — they run on separate servers connected to the DBM network. In SAP terminology, this is called a three-tier architecture. This allows you to use any combination of platforms on levels. In a 3-tier configuration, the database level can be easily replaced with DBM without changes at other levels. SAP administrative tools (BR * Tools) and SAP Central Services can be installed on DBM.
On 10.06.2011 there is no possibility of the initial installation of SAP on DBM. Only existing database can be transferred.
• Constantly changeable SAP activity document on DBM: SAP Note 1590515
• New installations of NetWeaver 7.0 work only with Unicode, therefore both database encodings should be only UTF8
• There are restrictions for non-Unicode installations.
• When migrating to DBM, the encodings must match the encodings of the original system. The encoding will be either WE8DEC or UTF8, the national encoding is only UTF8.
• When upgrading, two bundles must be installed together: “Oracle Exadata Bundle Patch” and “SAP Exadata Bundle Patch”. The second version must match the first version.
• SAP Application Servers and BR * Tools use a shared file system exported from the outside. If the file system was implemented on the database server, then you need to use another server or NAS for this (Recommended by ZFS-Appliance). HA-NFS is desirable.
• In an SAP installation, SAP Central Services components are protected using cluster solutions. If in the old installation their protection was provided by the cluster software of the database server, then the following options are possible:
Two additional x86 machines with Solaris and Solaris Cluster;
Installing and integrating them with Oracle Clusterware on DBM.
')
About Exadata Features for SAP
The SAP BR * Tool administration tool does not support HCC compression. SAP itself does not use direct downloads, which are necessary for HCC compression, but uses conventional single-line data inserts. In SAP, there is formally no division into operational data and archived data. All this greatly limits the use of HCC for SAP, but does not prevent.
DBFS is not supported by SAP.
All other features are fully supported and do not require additional settings. But you should know that any SAP application (SAP BW) makes extensive use of indices, with infrequent full scans, so you should not expect the use of Smart Scans and the corresponding productivity growth.
Smart Flash Cache and wide I / O channels will provide the highest level of I / O. I / O Resource Manager provides I / O scheduling, which is very important when using DBM to consolidate both various SAP applications and SAP applications with other applications.
Source: https://habr.com/ru/post/123607/
All Articles