Using Sap Netweaver with the Oracle Database Appliance

Download Using Sap Netweaver with the Oracle Database Appliance

Post on 21-Sep-2015

227 views

Category:

Documents

4 download

Embed Size (px)

DESCRIPTION

This document explain all the necessary steps do setup an SAP system based on the SAP Netweaver technology using an Oracle Database Appliance 2.9 and later.

TRANSCRIPT

  • An Oracle White Paper March 2014

    UsingSAPNetWeaverwiththeOracle DatabaseAppliance2.9 A Best Practices Guide

  • Preface...........................................................................................................................3

    Oracle Database Appliance Installation Overview..........................................................5

    ASM Disk Groups forSAP Databases...........................................................................7

    Clustering Solution for SAP HA on Oracle Database Appliance....................................8

    Newer SAP NetWeaver Products on Oracle Database Appliance.................................8

    CharacterSet Requirements for SAP Databases..........................................................8

    NonUnicode SAP Installations.......................................................................................8

    Shared File Systems in SAP Environments...................................................................10

    Oracle Database Appliance for SAP Deployment..........................................................11

    SAP Oracle Home Naming Requirements.....................................................................22

    Using SAPinst on the Oracle Database Appliance.........................................................23

    SAPinst: Oracle Database Instance...............................................................................40

    Post SAPinst Installation Steps......................................................................................65

    SAP Database Administration with BR*Tools.................................................................66

    Lifecycle Management forSAP Databases....................................................................67

    Installation of the Operating System and Firmware Patches..........................................68

    Installation of the SAP Bundle Patch forthe Oracle Database Appliance......................69

    Migration of SAP Databases...........................................................................................70

    Migration Approach 1: OracletoOracle (O2O) ACS Service and Customer SelfService. . .70

    Migration Approach 2: OracletoOracle (TripleO)ACS Service only...........................71

    Migration Approach 3: Oracle RMAN and Transportable Tablespaces..........................73

    Documentation References:...........................................................................................74

  • Using SAP NetWeaver with the Oracle Database Appliance

    Preface

    This document explains all the necessary steps to setup an SAP system based on the SAP NetWeaver technology using an Oracle Database Appliance 2.9 and later.

    Note: This paper is for Oracle Database Appliance 2.9 and later releases. All SAP products and solutions based on SAP NetWeaver Technology using a minimum SAP NetWeaver Version 7.0 are certified and supported to be used with the Oracle Database Appliance. Therefore SAP products such as SAP ERP 6.0, SAP ECC 6.0, SAP BW 7.0, SAP CRM 7.0 , SAP SRM 7.0 or SAP Solutions such as SAP Banking Services version 7.0 can be used with the Oracle Database Appliance. SAP products which are not based on SAP NetWeaver Technology such as SAP Business Objects cannot be used with the Oracle Database Appliance.

    The Oracle Database Appliance provides the following capabilities to an SAP environment:

    Highly available active-active clustered database server for SAP Applications

    Highly available file server for SAP required shared file systems such as /sapmnt

    Complete clustering solution for SAP High Availability Resources such as Central Services for both ABAP and JAVA stack

    The Oracle Database Appliance cannot be used to run SAP application instances. SAP application instances have to run on separate machines which use the Ethernet network to exchange data with the database(s) on the Oracle Database Appliance. In SAP terminology this is called a three tier architecture. This flexible three tier architecture allows for any combination of hardware and operating systems running the SAP instances to be used with the Oracle Database Appliance. So for example you can run or keep existing SAP Application servers on AIX or HP-UX platforms connected to the Oracle Database Appliance. This flexibility allows for an easy introduction of the Oracle Database Appliance in existing SAP environments as it leaves the SAP application layer unchanged. The only SAP components which are supported to run on the Oracle Database Appliance are the SAP database administration tools (BR*Tools) and the SAP central services (SCS and ASCS). This whitepaper describes the SAP specific deployment andconfiguration of necessary Oracle software settings on the Oracle Database Appliance as of the following version:

    3

  • Using SAP NetWeaver with the Oracle Database Appliance

    Oracle Database ApplianceVersion

    End User Bundle Version

    Grid Infrastructu re Version

    Database Version

    2.9.0.0.0 2.9.0.0.0 11.2.0.4 11.2.0.4.0 SingleInstance 11.2.0.4.0 RAC

    For older Oracle Database Appliance, see the respective whitepaperon SCN.

    When using SAP applications with the Oracle Database Appliance you can either use Oracle Database 11g Release 2 or Oracle Real Application Clusters 11g Release 2. Oracle Real Application Clusters One Node is not supported with SAP products and therefore cannot be used.

    The paper describes the SAP specific deployment and configuration of necessary Oracle software settings on the Oracle Database Appliance, SAP specific database requirements, information on how to install SAP required database patches for the Oracle Database Appliance and suggestions for the implementation of shared file systems for SAP installations.

    SAP Note 1760737 will be updated on a regular base to reflect any changes on using SAP Applications with the Oracle Database Appliance.

    Overall this document complements the existing Oracle Database Appliance documentation [1] and therefore it is assumed that the reader is familiar with the Oracle Database Appliance documentation.

    To understand the requirements and steps outlined in this document it is necessary that the reader is also familiar with the SAP specific support notes and white papers on Oracle RAC [2] and Oracle ASM [3].

    SAP support notes [4] are available from the SAP Service Marketplace for authorized users.

    4

  • Using SAP NetWeaver with the Oracle Database Appliance

    OracleDatabaseApplianceInstallationOverview

    To set up your Oracle Database Appliance for an SAP database, you must follow the below steps:

    1. Re-image the Oracle Database Appliance If the Oracle Database Appliance is delivered with a factory image of version less than 2.9.0.0.0, you must re-image the Oracle Database Appliance with the OS ISO Image 2.9.0.0.0 or later. You can download the ISO image following the links in Oracle Support Note 888888.1 and install it according to the instructions in the Oracle Database Application documentation.

    2. Install the Oracle Database Appliance Bundle Patch Install the Oracle Database Appliance Bundle Patch corresponding to the Oracle Database Appliance ISO image you installed in the first step (2.9.0.0.0 or later). It is recommended to install the Oracle Database Appliance Bundle Patch even after re-imaging the Oracle Database Appliance with an ISO image, since the Oracle Database Appliance Bundle Patch may contain firmware patches that are not installed by the ISO image. You can download the Oracle Database Appliance Bundle Patch following the links in Oracle Support Note 888888.1 and install it according to the instructions in the Oracle Database Application documentation.

    3. Install and deploy the Oracle Database Appliance End User Bundle Install the Oracle Database Appliance End User Bundle corresponding to your Oracle Database Appliance version and start the database deployment. You can download the Oracle Database Appliance End User Bundle following the links in Oracle Support Note 888888.1. Install and deploy the end user bundle according to the instructions in section "Oracle Database Appliance for SAP Deployment" of this white paper.

    4. Use SAPinst to prepare the Oracle Database Appliance for an SAP database Run SAPinst as described in section "Using SAPinst on the Oracle Database Appliance" of this white paper to create SAP-specific OS users, create SAP-specific directories, and otherwise prepare the Oracle Database Appliance for an SAP database.

    5. Install the latest SAP Bundle Patch for the OracleDatabase ApplianceIt is required that any database instance has the latest SAP-recommended Oracle grid and database patches installed.

    5

  • Using SAP NetWeaver with the Oracle Database Appliance

    For the Oracle Database Appliance, these are delivered in the SAP Bundle Patch for Oracle Database Appliance on the SAP Service Marketplace. You can download the latest SAP Bundle Patch for the Oracle Database Appliance following the instructions in SAP Note 1975175 and install it according to the instruction in section "Installation of the SAP Bundle Patch for ODA" of this white paper.

    6. Create or migrate an SAP database instance Run SAPinst as described in section "Using SAPinst on the Oracle Database Appliance" to create a new SAP database instance. That database instance will use the Oracle database software deployed by the Oracle Database Appliance End User Bundle above. Alternatively, you can migrate an existing SAP database to the Oracle Database Appliance as described in section "Migration of SAP Databases" of this white paper.

    6

  • Using SAP NetWeaver with the Oracle Database Appliance

    ASMDiskGroupsfor SAPDatabases

    The default ASM Disk Groups provided by the Oracle Database Appliance should be used for all SAP databases. For SAP production databases a redundancy level of high should be used to achieve the highest level of protection against any type of storage failure. Other SAP databases used for development, test and QA may use a normal ASM redundancy level.

    In line with the standard Oracle Database Appliance setup you should use the ASM disk Groups +DATA, +REDO and +RECO. The DATA Group should contain all data files, control files, spfiles, OCR and voting disks. The RECO Group should contain temporary files, archive logs, flashback files and backups. The REDO Group should contain all non-multiplexed redo log files.

    When storing more than one SAP database (for instance an SAP ERP database and an SAP BW database or an SAP ERP database with an SAP CRM database or multiple SAP ERP databases) on the Oracle Database Appliance all files of each of these SAP databases should follow the above recommendation and all be stored in the DATA , REDO and RECO disk groups.

    For performance and throughput reasons it is recommended for each SAP database to only have two control files in the DATA disk group and non-multiplexed online redo log files in the REDO disk group. As standard SAP installations use three control files in the database it is recommended to remove one control file from the spfile or init.ora. Standard SAP installations also use two members for each online redo log file. On the Oracle Database Appliance it is therefore necessary to remove one member of each online redo log file for each redo thread. The source database will have multiple redo threads if it was a RAC database. Three control files and multiplexed online redo log files are not needed on the Oracle Database Appliance as the control files and the online redo log files are stored in the DATA and REDO disk groups which already provide triple mirroring for each file at the Oracle ASM level due to the redundancy level of high.

    7

  • Using SAP NetWeaver with the Oracle Database Appliance

    ClusteringSolutionforSAPHAonOracle DatabaseAppliance

    If you plan implementing of SAP High Availability Resources such as Central Services for both SAP ABAP (ASCS, ERS) stack, SAP JAVA (SCS, ERS) stack and SAP WebDispatcher you can choose SAPCTL.

    Check the support of SAP NetWeaver product and SAP Kernel with Oracle Linux 5.x in the SAP PAM. SAP Note 1496927 describes SAPCTL. A very detailed guide, how to implement ASCS and ERS on Oracle Database Appliance you can find in SAP Note 1877857.

    NewerSAPNetWeaverProductsonOracleDatabaseAppliance

    SAP NetWeaver products will be delivered with SAP Kernel 7.20 EXT and higher or with SAP Kernel 7.40 and higher. Oracle Database Appliance runs with Oracle Linux 5.x and these newer versions of SAP Kernel are not supported for this OS release.

    Running the Oracle Databases on Oracle Database Appliance is allowed and BR*Tools and SAP Host Agent for 7.20 must be used. Any other parts of a SAP System (ASCS, SCS, ERS, PAS, AS) must be run on an other server with following the requirements of SAP.

    More related information can be found in SAP Note 1760737 and 1973403.

    CharacterSetRequirementsforSAPDatabases

    New installations of systems from SAP NetWeaver 7.0 are only supported with Unicode. For an SAP Unicode installation it is required that both the character and the national character set in the database is set to UTF8. The installation tool of SAP will take care about the character set and automatically choose the right one. With ODA version 2.9.0.0 the deployment has changed and you can decide whether a default database should be created or not. For SAP the recommendation is not to create a default database and bypass the step Database Information.

    NonUnicodeSAPInstallations

    Existing Non-Unicode SAP installations can be used with the Oracle Database Appliance. It is important for these Non-Unicode installations that the character and national character set of the migrated databases from existing systems to the Oracle Database Appliance are kept the same as in the original system.

    It is mandatory that the SAP application of such a Non-Unicode SAP installation runs on an operating system which supports the Non-

    8

  • Using SAP NetWeaver with the Oracle Database Appliance

    Unicode runtime requirements of SAP. The Product Availability Matrix (PAM) of SAP (http://www.service.sap.com/PAM) should be checked for valid operating system support for Non-Unicode SAP installations.

    In the case of Non-Unicode installations it is highly recommended to not change the hardware or operating system for the SAP application layer. Only the existing database server and storage layer should be changed to the Oracle Database Appliance.

    Note: In the case of Non-Unicode SAP installations you cannot run the SAP Central Services on the Oracle Database Appliance.

    9

  • Using SAP NetWeaver with the Oracle Database Appliance

    SharedFileSystemsinSAPEnvironments

    In an SAP environment it is common that all SAP Application Servers have access to a shared file system (/sapmnt, /usr/sap/trans, ...) which store the SAP kernels, profiles, trace files and provide the global SAP transport directory. In typical SAP installations such a shared file system is implemented using a NAS appliance, a cluster file system...

Recommended

View more >