An Oracle White Paper March Using SAP NetWeaver with the Oracle Database Appliance 2.9. A Best Practices Guide

Please download to get full document.

View again

of 76
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Information Report
Category:

Real Estate

Published:

Views: 10 | Pages: 76

Extension: PDF | Download: 0

Share
Related documents
Description
An Oracle White Paper March 2014 Using SAP NetWeaver with the Oracle Database Appliance 2.9 A Best Practices Guide Preface... 3 Oracle Database Appliance Installation Overview...5 ASM Disk Groups for SAP
Transcript
An Oracle White Paper March 2014 Using SAP NetWeaver with the Oracle Database Appliance 2.9 A Best Practices Guide Preface... 3 Oracle Database Appliance Installation Overview...5 ASM Disk Groups for SAP Databases... 7 Clustering Solution for SAP HA on Oracle Database Appliance...8 Newer SAP NetWeaver Products on Oracle Database Appliance...8 Character Set Requirements for SAP Databases... 8 Non Unicode SAP Installations... 8 Shared File Systems in SAP Environments Oracle Database Appliance for SAP Deployment SAP Oracle Home Naming Requirements Using SAPinst on the Oracle Database Appliance...23 SAPinst: Oracle Database Instance Post SAPinst Installation Steps SAP Database Administration with BR*Tools...66 Lifecycle Management for SAP Databases Installation of the Operating System and Firmware Patches...68 Installation of the SAP Bundle Patch for the Oracle Database Appliance...69 Migration of SAP Databases Migration Approach 1: Oracle to Oracle (O2O) ACS Service and Customer Self Service...70 Migration Approach 2: Oracle to Oracle (Triple O) ACS Service only Migration Approach 3: Oracle RMAN and Transportable Tablespaces...73 Documentation References:... 74 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 and configuration of necessary Oracle software settings on the Oracle Database Appliance as of the following version: 3 Oracle Database End User Appliance Bundle Version Version Grid Database Infrastructu Version re Version Single Instance RAC For older Oracle Database Appliance, see the respective whitepaper on 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 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 Oracle Database Appliance Installation Overview 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 , you must re-image the Oracle Database Appliance with the OS ISO Image or later. You can download the ISO image following the links in Oracle Support Note 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 ( 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 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 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 SAPspecific 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 Oracle Database Appliance It is required that any database instance has the latest SAPrecommended Oracle grid and database patches installed. 5 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 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 ASM Disk Groups for SAP Databases 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 Clustering Solution for SAP HA on Oracle Database Appliance 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 describes SAPCTL. A very detailed guide, how to implement ASCS and ERS on Oracle Database Appliance you can find in SAP Note Newer SAP NetWeaver Products on Oracle Database Appliance 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 and Character Set Requirements for SAP Databases 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 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. Non Unicode SAP Installations 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 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 Shared File Systems in SAP Environments 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 or through an NFS exported file system from the database server. For high availability reasons a cluster file system is being used or the source of the NFS location is protected by special configurations such as HA-NFS to not be a single point of failure in an SAP environment. If you already have an existing shared file system solution in your SAP environment not using an NFS exported file system from the database server it is recommended to continue to use this solution when moving to the Oracle Database Appliance. The Oracle Database Appliance offers during the deployment phase the configuration of a Cloud File System. This file system is based on Oracle's Advanced Cluster File System (ACFS) and can be used for /sapmnt on all application servers, if it is NFS exported from the database server.. After the deployment you can add additional file systems like /usr/sap/trans,..., using Advanced Storage Management Configuration Assistance (asmca). 10 Oracle Database Appliance for SAP Deployment This section describes the deployment of the ODA End User Bundle for SAP. The deployment installs the Oracle Grid and RDBMS software and creates an Oracle Grid instance and an Oracle database. With ODA version as mentioned above we bypass the create database step, we deploy the RDBMS software only. The deployment can be divided into two major parts. The first part is the pre-installation part, where all necessary customer specific parameters are collected and be stored into a configuration file. The second part of the installation uses the information from the configuration file. The deployment is divided into 25 automated running steps. Before you can start the deployment of the Oracle Database Appliance end user bundle, ensure that you have the latest Oracle Database Appliance Bundle Patch installed. See above section Oracle Database Appliance Installation Overview for more details. The next pages show a step by step deployment. Note that since version the option -advance to command oakcli deploy is available, which offers new functionality. Login as user root on the first node Change to directory /tmp Run the deployment:: /opt/oracle/oak/bin/oakcli deploy -advance 11 Choose SAP Application. 12 Set the user id and group id dependent on your environment. SAP defined the GI User and the DB User as oracle, the Install Group is oinstall, DBA Group is dba, DBA Oper Group is oper, ASM DBA Group is asmdba, ASM Oper Group is asmoper and ASM Admin Group is asmadmin. 13 Set your System Name, with Help you get answers, what is meant with each input. 14 15 ODA supports beside the public network other network if needed. 16 SAPinst will be used to create the database. Therefore this step will be skipped. 17 18 In case you will use Oracle Database Appliance to provide /sapmnt, this mask is to setup an Oracle CloudFS/ACFS file system. 19 Use Install to start the deployment. 20 21 SAP Oracle Home Naming Requirements The correct installation and operation of any SAP utility such as SAPinst or BR*Tools on the database nodes of the Oracle Database Appliance requires some preparation for the correct setting of the ORACLE_HOME environment variable in the SAP environment. The SAP environment requires the ORACLE_HOME environment variable to be set to /oracle/ sid / release . To create an SAP database, SAPinst searches for the ORACLE_HOME directory. If there is a usable installation with the Oracle RDBMS software correctly installed SAPinst will not extract the RDBMS DVD, it will use the existing installation. SAPinst looks for the RDBMS software in /oracle/ sid / release the standard path of SAP for the Oracle RDBMS software. The ODA deployment installs the RDBMS software under /u01/app/oracle/product/ /dbhome_1. Therefore we need to create a symbolic link on both nodes. login to the nodes and create the directory /oracle and /oracle/ sid . We use here ADO as the SID / ]# mkdir /oracle / ]# chown oracle:oinstall /oracle / ]# su oracle create the symbolic link / ]# mkdir -p /oracle/ado / ]# ln -s /u01/app/oracle/product/ /dbhome_1 /oracle/ado/112 Repeat above steps on the second node / ]# mkdir /oracle / ]# chown oracle:oinstall /oracle / ]# su oracle create the symbolic link / ]# mkdir -p /oracle/ado / ]# ln -s /u01/app/oracle/product/ /dbhome_1 /oracle/ado/112 22 Using SAPinst on the Oracle Database Appliance SAP has changed the installation utility SAPinst to work on the Oracle Database Appliance. The next pages show the Oracle Database Appliance related steps from a perspective of SAPinst. We start SAPinst with the step RAC/ASM/Database Instance Preparation to create SAP-specific OS users, create SAP-specific directories, and otherwise prepare the Oracle Database Appliance for an SAP database. Preparation is recommended for both nodes of the Oracle Database Appliance. 23 Select Custom Mode. 24 Deselect Profiles are available, we have no SAP profiles with a new installation. 25 Set the SAP system ID, we use here ADO for SAP SID and Oracle SID. The ACFS file system /sapmnt is available and realized with Oracle ACFS. 26 27 28 29 Set the Oracle SID, select RAC on Oracle ASM and the type of RAC on Engineered Systems. 30 31 32 33 34 Set the ORACLE_HOME for GRID and the ASM instance. 35 36 37 38 Repeat the step Database Instance Preparation on the second node. 39 SAPinst: Oracle Database Instance Dependent on your installation needs, it is required to install the necessary SAP instances (ASCS, SCS or ERS) first, as described in the SAP Installation Guide. After that you can start the database installation described on the next pages. This steps are only needed on one of the nodes of Oracle Database Appliance. We make these steps on the first node lsoda01. 40 41 42 43 44 45 46 47 48 49 50 Before you choose Next verify the OS user oracle belongs to OS group sapinst! 51 52 53 54 55 56 Check Mirror Redo Log Files and select ASM Diskgroup +REDO for the secondary member of the RedoLogs. All RedoLog are located on the Diskgroup +REDO. 57 All Control Files are located on the ASM Diskgroup +DATA. If plan more then one Control File you have to use different names. 58 Verify the database parameter compatible. If compatible is less than the database compatibility of your ASM Disk Group, change the parameter to the database compatibility of your ASM Disk Group compatibility. In addition verify if the following parameters are set, if not add them. _enable_numa_support = FALSE _file_size_increase_increment= 2044M _disable_interface_checking = TRUE _gc_undo_affinity = FALSE _gc_policy_time = 0 db_block_checksum = FULL db_lost_write_protect = TYPICAL db_block_checking = FULL db_create_file_dest = +DATA db_create_online_log_dest_1= +REDO 59 60 61 62 63 64 Post SAPinst Installation Steps Setup the environment for your new database on each node, edit the file /etc/oratab and add the lines: on first node lsoda01: ADO1:/oracle/ADO/112:N on seco
Recommended
View more...
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks
SAVE OUR EARTH

We need your sign to support Project to invent "SMART AND CONTROLLABLE REFLECTIVE BALLOONS" to cover the Sun and Save Our Earth.

More details...

Sign Now!

We are very appreciated for your Prompt Action!

x