White Paper: Using SAP NetWeaver with Oracle Database Appliance Software 12.1.2.6.0

Add to my manuals
106 Pages

advertisement

White Paper: Using SAP NetWeaver with Oracle Database Appliance Software 12.1.2.6.0 | Manualzz

Using SAP NetWeaver with Oracle Database

Appliance Software 12.1.2.6.0

Key Guidelines

O R A C L E W H I T E P A P E R | M A R C H 2 0 1 6

Table of Contents

Disclaimer

Introduction

Mixed Grid Infrastructure and RDBMS Versions

Oracle Database Appliance Software Installation Overview

ASM Disk Groups for SAP Databases

Clustering Solution for SAP HA on Oracle Database Appliance

SAP NetWeaver Products on the Oracle Database Appliance

Character Set Requirements for SAP Databases

Non-Unicode SAP Installations

Shared File Systems in SAP Environments

Oracle Database Appliance Node as an NFS Server

Oracle Database Appliance Node as an NFS Client

Oracle Database Appliance Software for SAP Deployment

Rolling back initial DB PSU

SAP Software Provisioning Manager on Oracle Database Appliance

SWPM: ASCS Instance installation

SAP Oracle Home Naming Requirements

SWPM: Oracle Database Instance

Post SWPM Installation Steps etc/oratab adjustments

Setup orabtt

– Ora BaseTabTool

Copy init<SID>.ora file to remote host

1 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

21

47

56

57

9

20

8

8

93

93

93

93

6

7

7

7

6

6

4

5

3

3

Verify correct database parameter settings, and correct if needed 93

Database Service scripts on PAS / subsequent Application Server instance(s) 93

Clean up install space

– TMP

94

SAP PAS, subsequent Application Servers require uuid and uuidd packages 94

Virtual host names for SAP PAS and subsequent SAP Application Servers 94

Complete the HA awareness for ASCS and ERS instances

Verify environment for user oraado

94

94

SAP Database Administration with BR*Tools

Lifecycle Management for SAP Databases

Installation of the Operating System and Firmware Patches

Installation of the SAP Bundle Patch for the Oracle Database Appliance

Documentation References

Appendix A

– crsctl output after a fresh deployment

Appendix B - Additional Local + Cluster Resources after HA awareness

Appendix C

– Full CRS output after configuration

98

100

101

102

95

96

96

97

2 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Disclaimer

Oracle Database Appliance Software 12.1.2.6.0 on Oracle Database Appliance X5-2 models do not support 11.2 databases for SAP environments due to some constraints. Please note earlier versions of Oracle Database

Appliance models are unaffected and this disclaimer is solely applicable to X5-2 models only.

Oracle MOS Note 888888.1 dictates that databases on Oracle Database Appliance Software 12.1.2.6.0 on X5-2 models have to run on ACFS; however SAP and Oracle Database Appliance engineering worked together and do support Oracle databases for SAP on classic ASM diskgroup layouts.

Introduction

This document explains all the necessary steps to setup an SAP system using an Oracle Database Appliance

Software 12.1.2.6.0 and later.

Note: This paper is for Oracle Database Appliance Software 12.1.2.6.0 and later releases.

All SAP products and solutions based on SAP NetWeaver Technology using a minimum SAP NetWeaver Version

7.0 are both certified and supported to be used with the Oracle Database Appliance. As an excerpt from SAP Note

2133079, SAP products such as SAP ERP 6.0, SAP BW 7.0 and later, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0 or SAP solutions such as SAP Banking Services version 6.0 and later can be used with the Oracle Database

Appliance. Additional SAP products like:

» SAP NetWeaver MDM 7.1 SP12 and later

» Reporting Data Source of SAP Business Objects BI 4.0 (minimum SP10) and BI 4.1 (minimum SP04)

» Repository,source and target databases for SAP Data Services 4.2 (minimum SP 03) can also be used with the Oracle Database Appliance.

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

» Highly available active-active clustered database server for SAP Applications

» Complete clustering solution for SAP High Availability Resources such as Application Server Central Services for both ABAP and JAVA stack (ASCS, SCS)

» Highly available file server for SAP required shared file systems such as /sapmnt and /usr/sap/trans.

The Oracle Database Appliance Software cannot be used to run SAP application instances. SAP application instances have to run on separate hosts and connect via network against the database(s) on the Oracle Database

Appliance. In SAP terminology this is called a three tier architecture. This flexible three tier architecture allows any supported combination of hardware and operating systems running the SAP instances to be used with the Oracle

Database Appliance, e.g. we can run or keep existing SAP Application servers on any supported platform connected to the Oracle Database Appliance. This flexibility allows an easy introduction of the Oracle Database Appliance in existing SAP environments as the SAP application layer remains unchanged.

The only SAP components which are supported to run on the Oracle Database Appliance Software are the SAP database administration tools (BR*Tools), SAP Application Server Central Services (ASCS, SCS), the SAP

Enqueue Replication Server (ERS) and various SAP agents. This paper describes the SAP specific deployment and configuration on the Oracle Database Appliance with the Oracle components and their versions, SAP specific database requirements, information on how to install SAP required database patches for the Oracle Database

Appliance Software and suggestions for the implementation of shared file systems for SAP installations.

3 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Whilst both bare and virtualized deployments are possible on the Oracle Database Appliance this document illustrates the bare metal deployment as the virtualized deployment is not certified in an SAP environment.

Oracle

Database

Appliance version

OS release

End User

Bundle version

Grid Infrastructure version

Database version

12.1.2.6.0

12.1.2.6.0

Oracle Linux 6.7 12.1.2.6.0

Oracle Linux 6.7 12.1.2.6.0

12.1.2.0.2+

12.1.2.0.2+

12.1.2.0.2+ RAC

12.1.2.0.2+ Single Instance

11.2.0.4.x+ RAC*

11.2.0.4.x+ Single Instance*

* Not on X5-2 models

Please check the respective whitepaper on SCN for earlier versions of the Oracle Database Appliance.

When using SAP applications with the Oracle Database Appliance you can run Oracle Real Application Clusters 12c or 11gR2, or, Oracle Database 12c or 11gR2. Oracle Real Application Clusters One Node is not supported with SAP products and therefore cannot be used.

SAP Note 2290084 will be updated on a regular basis 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 and HA capabilities [3].

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

Mixed Grid Infrastructure and RDBMS Versions

Starting with Grid Infrastructure (GI) version 12.1.0.2 it is now supported to run a certain mix of GI and RDBMS for

SAP databases. With GI 12.1.0.2 Oracle supports to run RDBMS 11.2.0.4 and/or RDBMS 12.1.0.2 for SAP databases. Detailed information is being provided in SAP Notes 1677978 and 527843. Please remember the constraint for X5-2 models.

4 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Oracle Database Appliance Software Installation Overview

To set up your Oracle Database Appliance Software for an SAP database, we follow below major steps:

1. Re-image the Oracle Database Appliance if needed

If the Oracle Database Appliance is delivered with a factory image of version less than 12.1.2.6.0, one has to reimage the Oracle Database Appliance with the OS ISO Image 12.1.2.6.0 or later. Download the ISO image following the links in Oracle Support Note 888888.1 and install it according to the instructions in the Oracle Database

Appliance 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 (12.1.2.6.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 in Step 1 as the Oracle Database

Appliance Bundle Patch may contain firmware patches that are not installed by the ISO image. 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. 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. Rollback DB PSU

This step aims for a faster installation of the SAPDBBundlePatch later on.

Please follow chapter “Rolling back initial

DB PSU”.

5. Use SWPM to prepare the Oracle Database Appliance for an SAP database

Run the SAP Software Provisioning Manager (SWPM) as described in section "SAP Software Provisioning Manager on Oracle Database Appliance" of this white paper to create SAP-specific OS users, create SAP-specific directories, and other preparations of the Oracle Database Appliance for an SAP database.

6. ASCS Instance installation

Before moving on creating a database instance SAP requires to have an Application Server ABAP Central Services instance. We perform this installation in high availability mode.

Follow chapter “SWPM: ASCS Instance installation”

7. Create an SAP database instance

Run SWPM as described in section "Using SWPM on the Oracle Database Appliance" to create a new SAP database instance. This database instance will use the Oracle database software deployed by the Oracle Database

Appliance End User Bundle in Step 3.

8. Install the latest SAP Bundle Patch for the Oracle Database Appliance

It is required that any database instance has the latest SAP-recommended Oracle Grid Infrastructure and database patches installed. Download the latest SAP Bundle Patch for the Oracle Database Appliance following the instructions in SAP Note 2145651 and install it according to the instructions in section "Installation of the SAP

Bundle Patch for ODA" of this white paper.

9. Post installation considerations.

5 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

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, backups and a mirrored controlfile copy. The

REDO Group should contain all non-multiplexed redo log files.

When storing more than one SAP database (e.g. SAP ERP database and SAP BW database or, 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 have two control files, one in the DATA disk group and the other in the RECO disk group. Non-multiplexed online redo log files shall be stored in the REDO disk group. The REDO disk group is formed entirely by SSDs. Standard SAP installations use three control files in the database, thus it can be suggested to remove one control file from the spfile or init.ora. Standard

SAP installations also create two members for each online redo log file. On the Oracle Database Appliance it is therefore possible to remove one member of each online redo log file for each redo thread. 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, RECO and REDO disk groups which already provide triple mirroring for each file at the Oracle ASM level due to the redundancy level of high.

Clustering Solution for SAP HA on Oracle Database Appliance

If you plan to implement SAP High Availability Resources such as Central Services for the SAP ABAP stack(ASCS,

ERS), SAP JAVA stack(SCS, ERS) and/or SAP WebDispatcher SAPCTL is the tool of choice.

A detailed guide how to implement ASCS and ERS on Oracle Database Appliance is provided in SAP Note 1877857 at install time. Once installed this requires configuration against Oracle CRS using SAPCTL. Consult SAP Note

1496927 for download and guidance on SAPCTL. This document takes care of implementing ASCS + ERS high availability using SAPCTL .

SAP NetWeaver Products on the Oracle Database Appliance

SAP NetWeaver integration points are split between the parts that are certified to run on the Oracle Database appliance itself on one hand, and on other hand for those hosts that form the SAP application servers. Consequently we have to choose a certification that satisfies both database and host operation system requirements, which is SAP

NetWeaver 7.41 (or higher) 64-bit Unicode.

Non-local software deployments need to run SAP Kernel Release 7.21 EXT or higher.

SAP NetWeaver products will be delivered with SAP Kernel Release 7.21 EXT and higher or with SAP NetWeaver

7.0 and higher. More related information can be found in SAP Notes 2290084, 1760737 and 1973403. Information leading entity is the SAP Product Availability Matrix, SAP PAM.

6 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Character Set Requirements for SAP Databases

Fresh installations of SAP NetWeaver 7.x systems or higher provide Unicode support only. For an SAP Unicode installation it is required that both the character set and the national character set in the database is set to UTF8.

SAP SWPM will take care about the character set and automatically choose the right one. With the current Oracle

Database Appliance version one 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 required for these non-Unicode installations that the character and national character set of the migrated databases from existing systems to the Oracle Database Appliance remain 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-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 not to change the hardware nor 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.

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 stores the SAP kernels, profiles, trace files and provide the global SAP transport directory.

Typical SAP installations implement such a shared file system using a NAS appliance, a cluster file system or via an

NFS exported file system from the database server. Highest availability can be achieved via a cluster file system or, the NFS sourcing location is protected by special configurations like HA-NFS in order to avoid a single point of failure within the SAP environment.

If you already run 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 keep this solution when moving to the Oracle Database

Appliance.

The deployment phase of the Oracle Database Appliance offers the creation and 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 getting NFS exported from the database server. Post-deployment one can add additional file systems like /usr/sap/trans and others using the Advanced Storage Management Configuration

Assistant (asmca).

In case of Oracle DataGuard deployments

– and topographic switchover or failover scenarios ACFS based filesystems won’t fail over.

7 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Oracle Database Appliance Node as an NFS Server

This is best described in Oracle MOS Note:1934030.1 ODA (Oracle Database Appliance): HowTo export ACFS

(cloudfs) using HANFS.

Oracle Database Appliance Node as an NFS Client

This scenario is applicable to environments where /sapmnt is being consumed from a 3 rd

party and not part of the

Oracle Database Appliance setup. We demonstrate here the nfs mount exported from sapstore to the local mountpoint /path/to/mountpoint.

Ensure that required packages are around, if not, install them.

[root@lsoda01]# rpm -qa | grep "nfs\|rpcbind" rpcbind-0.2.0-11.el6.x86_64 nfs-utils-1.2.3-54.el6.x86_64 nfs-utils-lib-1.1.5-9.el6.x86_64

Create local mountpoint, check/start rpc service, mount, verify:

[root@lsoda01]# mkdir –p /path/to/mountpoint

[root@lsoda01]# chmod 755 /path/to/mountpoint

[root@lsoda01]# showmount -e sapstore

Export list for sapstore:

/export/Oracle_Data (everyone)

/export/Oracle_Home (everyone)

[root@lsoda01]# service rpcbind status ; service rpcbind start

Starting rpcbind: [ OK ]

[root@lsoda01]# mount sapstore:/export/Oracle_Home /path/to/mountpoint

[root@lsoda01]# mount

.. sapstore:/export/Oracle_Home on /path/to/mountpoint type nfs

(rw,vers=4,addr=10.17.30.74,clientaddr=10.20.91.105)

8 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Oracle Database Appliance Software for SAP Deployment

This section describes the deployment of the Oracle Database Appliance Software End User Bundle for SAP. The deployment typically installs the Oracle Grid and RDBMS software and creates an Oracle Grid instance and an

Oracle database. With Oracle Database Appliance Software version 12.1.2.6.0 we bypass the create database step, we deploy the RDBMS software only.

The deployment consists of two major pieces. The first piece is the pre-installation part, where all necessary customer specific parameters are collected and stored into a configuration file. The second part of the installation uses the information from the freshly created configuration file and kicks off 24 automated installation steps.

Before you start the deployment of the Oracle Database Appliance end user bundle ensure that you have the latest

Oracle Database Appliance Bundle Patch installed. Review above section "Oracle Database Appliance Installation

Overview" for more details. OAKEndUserBundle* files come as different file names when downloaded from MOS.

The next pages show a step by step deployment.

We’re using the –advance switch for “oakcli deploy”.

Login as user root on the first node

» cd /tmp ; mv /path/to/OAKEndUserBundle_*of2.zip /tmp

» oakcli unpack -package /tmp/OAKEndUserBundle_1of2.zip

» oakcli unpack -package /tmp/OAKEndUserBundle_2of2.zip

Repeat above commands on the second node.

When finished run following command on the first node: /opt/oracle/oak/bin/oakcli deploy –advance

9 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

In case you’ve got an existing config file uploaded to the first net interface, “Browse” and locate the file. If not, select

“SAP Application”, click Next.

10 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Set the user id and group id according to your environment. SAP defines 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.

11 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Set System name and other main parameters, Help button provides assistance if needed. Oracle OS user + root will have identical passwords after deployment.

12 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

13 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Oracle Database Appliance secondary network support.

14 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

SAP SWPM will be used to create the database. Therefore this step will be skipped.

15 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

16 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

In case one plans to use Oracle Database Appliance to provide /sapmnt use this screen to setup an Oracle

CloudFS/ACFS file system.

17 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Consider saving the generated configuration and copy the generated config file to a place outside of the device

– you may need it on subsequent deployments. Then press the

“Install” button.

18 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

19 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Incomplete or Unsuccessful deployments

– please check Oracle Note:1409835.1 ODA (Oracle Database

Appliance): Deployment & Cleanup Steps.

At this stage X5-2 deployments have to verify and potentially correct ASM diskgroup compatibility settings as follows:

Login as user Oracle using the client of your choice. As these are shared disks it’s a one-time task.

[oracle@lsoda01 ]$ . oraenv

+ASM1

[oracle@lsoda01 ]$ asmcmd lsattr –lm | egrep “Name|compatible”

If that output would report any non 12.1 output, run following commands for each diskgroup:

[oracle@lsoda01 ]$ sqlplus “/ as sysasm”

SQL> alter diskgroup <DG> set attribute ‘compatible.asm’=’12.1.0.2’;

SQL> alter diskgroup <DG> set attribute ‘compatible.advm’=’12.1.0.2’;

SQL> alter diskgroup <DG> set attribute ‘compatible.rdbms’=’12.1.0.2’;

This is an irreversible change. Thus, no 11.2.x databases beyond this point for X5-

2’s.

Rolling back initial DB PSU

We roll back Oracle Patch 21948354 - Database Patch Set Update 12.1.0.2.160119 (Includes CPUJan2016) from all ORACLE_HOMEs per host.

Perform following steps per host: su – oracle export SBPFUSER=/sbin/fuser export OHGRID=/u01/app/12.1.0.2/grid export IHRDBMS=/u01/app/oracle/product/12.1.0.2/dbhome_1 export ORACLE_HOME=$IHRDBMS echo $ORACLE_HOME (verification)

$ORACLE_HOME/OPatch/opatch rollback –id 21948354 –local –all_subpatches

As there is no database associated to this ORACLE_HOME, no further script has to run. Keep in mind copy+pasting above commands may fail due to document to terminal character incompatibility.

Next is the GI home

– we borrow these steps from the SAP Bundle Patch for Oracle Database Appliance, Section

3, “SAP Bundle Patch deinstallation” – execute these on both hosts as well: su root -c "$SBPFUSER $IHRDBMS/bin/oracle" su root -c "/sbin/acfsutil info fs -o mountpoints | xargs $SBPFUSER -mu" su root -c "$OHGRID/crs/install/rootcrs.pl -prepatch -nonrolling" env ORACLE_HOME=$OHGRID $OHGRID/OPatch/opatch rollback -id 21948354 -silent -local all_subpatches su root -c "$OHGRID/rdbms/install/rootadd_rdbms.sh" su root -c "$OHGRID/crs/install/rootcrs.pl -postpatch -nonrolling"

..

..

Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [964513507].

20 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

SAP Software Provisioning Manager on Oracle Database Appliance

The next pages show the Oracle Database Appliance related steps from an SAP Software Provisioning Manager 1.0 perspective. Hence we refer throughout this document this as SWPM. It is recommended to start SWPM with a TMP variable set to /usr/sap/tmp which allows easier post-install cleanup. We start SWPM with the step

“RAC/ASM/Database Instance Preparation” to create SAP-specific OS users, create SAP-specific directories and other preparations for an SAP database. This preparation step is required for both nodes of the Oracle Database

Appliance. It is however recommended to perform a general prerequisite check per host

– SWPM Navigation is visible via the window title.

Following slides illustrate an SAP Netweaver 7.40 SR2 installation using SWPM SP10. SWPM is available via the

SLToolset. See SAP Note 1680045 for details on SWPM.

Database Instance Preparation consists of

» SAP Kernel independent and database dependent parts of the SAP Kernel installation

» BR*Tools installation as a portion of the database dependent part

» Oracle Instant Client installation

» SAP Hostagent installation

» SAP users and groups creation

» Preparation of the environment for running the SAP database on Oracle ASM with RAC

21 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Keep following media handy:

» SAP NetWeaver 7.40 SR2 OS dependent kernel

» Oracle Client 12c

22 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

From Generic Options drill down to Oracle, Database Tools, RAC/ASM/Exadata Database Instance Preparation

ABAP

– Kernel 7.4.x. Kernel version and stack need to match subsequent SAP NetWeaver product selection.

23 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Select Custom Mode.

24 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Deselect “Profiles are available”, fresh installations don’t offer SAP profiles.

25 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Set the SAP system ID; we choose ADO here for both SAP SID and Oracle SID. The mountpoint /sapmnt has been created earlier via the Oracle Appliance Manager setup.

26 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

27 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

28 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

29 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

User IDs, Group IDs shall be carefully selected. Blank items will cause SPWM to choose default values.

30 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Set the Oracle SID.

Select RAC on Oracle ASM, “type” becomes “RAC on Engineered Systems”.

31 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

32 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

33 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

34 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

35 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

36 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

37 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Set the ORACLE_HOME for GRID and the ASM instance according to actual values having deployed earlier via

Oracle Appliance Manager setup.

38 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

39 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Here we need to ensure that actual hostnames fit to Oracle Instance ID’s. Thus, on lsoda01 we run instance 001 whereas we run on lsoda02 instance 002.

40 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Next 5 screenshots show the full install review screens; please check carefully and if needed revise. Portions of screens distinguish by the vertical scrollbar.

41 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

42 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

43 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

44 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

45 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Install complete window.

Repeat this

step “Database Instance Preparation” on the second node. Note we still do not have an SAP database installation yet even when completed preparations on both hosts. Covered in the next steps.

46 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

SWPM: ASCS Instance installation

Before we can move on and create a database instance SAP requires to have a Application Server ABAP Central

Services instance. For later HA awareness of the ASCS Instance we follow SAP Note 1877857. HA aware ASCS installations need to be on a shared location, namely /usr/sap/<SAPSID>, here we consume /sapmnt for this, and put this under /sapmnt/share from the first host. Ideally you’d use a separate ACFS or other shared filesystem.

# mkdir -p /sapmnt/share ; cd /usr/sap ; tar cvf ADO.tar ADO

# cp ADO.tar /sapmnt/share ; cd /sapmnt/share ; tar xvf ADO.tar

# cd /usr/sap ; rm ADO.tar ; mv ADO was.ADOlocal

# ln -s /sapmnt/share/ADO ADO ; chown adoadm:sapsys ADO

Repeat the last 2 lines for the second host. Thus, host file system equivalence for /usr/sap/<SAPSID>.

On the first host we start the VIP:

# crsctl start ip -A 10.20.88.62/255.255.252.0/bond0

And invoke SWPM on the virtual host using ./sapinst SAPINST_USE_HOSTNAME=lsadoascs

47 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

48 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

49 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

50 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

51 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

52 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

53 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

54 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

ASCS installation completed at this point.

As we’re still in the context of SAP Note 1877857 next we install the

Enqueue Replication Server (ERS), on both hosts locally. As this is pretty straightforward slides are omitted here.

Once ERS installations have been completed, next steps are as <sidadm> on the installation hosts of ASCS: lsoda01: adoadm> sapcontrol –nr 00 –function Stop lsoda01: adoadm> sapcontrol –nr 00 –function StopService

Switch to root on this host, issue:

[root@lsoda01]# crsctl stop ip –A 10.20.88.62/bond0

Login as root to the 2nd clusternode, restart the IP there:

[root@lsoda02]# . oraenv

+ASM2

[root@lsoda02]# crsctl start ip -A 10.20.88.62/255.255.252.0/bond0

[root@lsoda02]# /usr/sap/hostctrl/exe/saphostctrl -function RegisterInstanceService sid ADO -nr 00 -saplocalhost lsadoascs

[root@lsoda02]# /etc/init.d/sapinit stop

55 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Edit /etc/init.d/sapinit, comment lines 438-444 (including) according to the whitepaper of SAP Note 1877857.

Repeat the steps sapinit stop and edit /etc/init.d/sapinit back on the first node.

Eventually on the first node restart sapinit as root: # /etc/init.d/sapinit start and start ASCS services manually for the subsequent SAP Database Instance installation. lsoda01: adoadm> sapcontrol –nr 00 –function StartService ADO lsoda01: adoadm> sapcontrol –nr 00 –function Start lsoda01: adoadm> sapcontrol –nr 00 –function GetProcessList

Later on we complete the HA integration. At this point we are finished with the content of SAP Note 1877857.

SAP Oracle Home Naming Requirements

The successful installation and operation of any SAP utility such as SWPM 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, SWPM looks for the ORACLE_HOME directory. If there is a suitable installation with the Oracle RDBMS software correctly installed SWPM will not extract the RDBMS install media; it will use the existing installation.

SWPM looks for the RDBMS software in /oracle/<SID>/<release> - standard path of SAP for the Oracle RDBMS software. The Oracle Database Appliance Software deployment installs the RDBMS software under

/u01/app/oracle/product/12.1.0.2/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>

[root@lsoda01 /]# mkdir /oracle

[root@lsoda01 /]# chown oracle:oinstall /oracle

[root@lsoda01 /]# su – oracle

Create the symbolic link:

[oracle@lsoda01 /]$ mkdir -p /oracle/ADO

[oracle@lsoda01 /]$ ln -s /u01/app/oracle/product/12.1.0.2/dbhome_1 /oracle/ADO/121

Repeat above steps on the second node.

At this point we’re ready for the Oracle Database installation.

56 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

SWPM: Oracle Database Instance

Depending on your deployment scenario and as outlined in the SAP Installation Guide it is required to install the necessary ABAP central services instance (ASCS) first, plus, having created the symbolic links for

ORACLE_HOME. We have done these in the previous two steps.

Keep following media handy:

» SAP NetWeaver 7.40 SR2 OS dependent kernel

» Installation Export SAP NetWeaver 7.40 SR2, EXP1

» Oracle Client 12c

SAP Database instance installation is described on the next pages. These steps need to be performed on one of the nodes of Oracle Database Appliance only.

Caveat: Database Instance Installation may fail if the shared profile value for SAPDBHOST is not matching the installation host: grep SAPDBHOST /sapmnt/ADO/profile/DEFAULT.PFL

In that case, correct SAPDBHOST setting towards the local hostname.

57 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Login to the first node lsoda01 and invoke SPWM:

./sapinst SAPINST_USE_HOSTNAME=lsadodb

Navigate right away to the shown item below.

58 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

This time we have profiles available, however we correct their location towards /sapmnt/ADO/profile.

59 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

60 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

61 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

62 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

RAC Installation Type needs to match RAC on Engineered Systems.

The database hostname lsadodb refers to the invocation of SPWM ( ./sapinst

SAPINST_USE_HOSTNAME=lsadodb ). This hostname is consumed by profile settings.

63 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

This Installation Export EXP1 will be used as input data for R3Load during this installation step.

64 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Advanced DB Configuration ticked. Offers various options on initial settings.

65 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Memory values derived from host query, should be adjusted when running more than one database on the Oracle

Database appliance.

Toggling between Install MCOD and / Install Database allows an editable sidadm user (adoadm vs. oraado)

66 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

67 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

68 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Before you press “Next” ensure that the OS user oracle is a member of the OS group sapinst.

For example, on a unix shell: id oracle shall return sapinst as well. Do not continue if this criteria is not met.

Also, provide correct path for ORACLE_HOME and ORACLE_SID for Oracle Grid Infrastructure.

69 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Parameter “compatible” in init.ora refers to the Oracle RAC instances compatible settings – RDBMS runtime settings. Compatible controls feature availability on the highest level. We have to adjust this value becoming

12.1.0.2.0.

Diskgroup compatibility refers to Oracle ASM and means here that it’s permitted to operate database software down to Oracle Database 11.2.0.2.0, if not being on Oracle Database Appliance X5-2.

Note: X5-2 deployments MUST have a diskgroup compatibility of 12.1.0.2.0.

70 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

71 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Adjust hostnames at the upper screen section as indicated by SWPM.

At the bottom screen section change local_listener parameters for both Oracle instances towards:

ADO001.local_listener = lsoda1-vip:1521

ADO002.local_listener = lsoda2-vip:1521

72 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

You may tick less options depending on your deployment scenario. init.ora Parameter discussion is covered later in this whitepaper.

73 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

74 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

75 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

It is suggested not to tick “Mirror Redo Log Files”. We keep redo logs in the +REDO ASM diskgroup on SSDs with 3way mirroring each. Mirroring them against +DATA diskgroup at the same time would impact runtime performance.

In this dialog we changed also the amount of redo log groups to 5 and their size from 4GB each towards 8GB

(formula for diskgroup size is: diskgroupsize [MB] > number of redo log group x size of a single redo log file [MB]).

76 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

2 logical controlfiles, each of them is 3-way mirrored at ASM level.

77 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

78 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

79 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

80 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

81 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

82 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

83 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

84 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

85 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

86 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

87 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

88 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

89 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

90 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

91 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Database installation complete at this point.

92 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Post SWPM Installation Steps

/etc/oratab adjustments

Verify the environment for your new database on each node, check the file /etc/oratab, on both nodes it should should read like below. The syntax is <db_unique_name>:<oracle home directory>:startup on host boot (Y vs N).

ADO:/oracle/ADO/121:N

Setup orabtt – Ora BaseTabTool

Navigate to SAP Note 1521371, download OraBaseTabTool, and run it.

Copy init<SID>.ora file to remote host

SWPM runs only on one node; hence we have to copy some files from the installation node to the second node.

SWPM already created the necessary files. Say on node 1 we refer to initADO001.ora file then we need to refer to initADO002.ora on node 2. This init<ORACLE_SID>.ora file essentially contains a pointer to the stored parameter file (spfile) in Oracle ASM.

Login to installation node as oracle

,

change to directory <ORACLE_HOME>/dbs scp initADO0002.ora <node2>:/<ORACLE_HOME>/dbs/initADO0002.ora

Verify correct database parameter settings, and correct if needed

Download and execute the parameter_check_12 script from SAP Note 1171650. Those settings shall reflect recommended values from SAP Note 1888485 Database Parameter for 12.1.0.2.

$ sqlplus “/ as sysdba”

SQL*Plus> @parameter_check_12.txt

Aside of the recommendations of above script ensure following parametrization is effective:

_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_block_checking = "FULL" db_lost_write_protect = "TYPICAL" db_create_file_dest = "+DATA" db_create_online_log_dest_1= "+REDO"

Also, correct local_listener settings, e.g. from sqlplus level and verify them instance by instance: alter system set local_listener="(ADDRESS = (PROTOCOL=TCP) (HOST=lsoda1vip)(PORT=1521))" SID='ADO001' scope=both; alter system set local_listener="(ADDRESS = (PROTOCOL=TCP) (HOST=lsoda2vip)(PORT=1521))" SID='ADO002' scope=both; show parameters local_listener

Database Service scripts on PAS / subsequent Application Server instance(s)

When installing SAP Primary Application Server (PAS) and further Application Server instances which require a database service which hasn’t been deployed yet SWPM halts it’s activities until you confirm having both copied and ran a generated script for the database service. This script needs to be executed in the database environment. Once

93 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

completed SWPM can resume installation of the SAP Application Server Instance installation. The script generates following additional service as a cluster resource: ora.ado.ado_dvebmgs00.svc

1 ONLINE ONLINE lsoda01 STABLE

Clean up install space – TMP

SWPM generates significant footprint in /usr/sap/tmp. It’s advisable to pack and transfer this content towards an alternative storage location. Once unpacking and crosschecking at the alternate storage location it’s fine to clean up

/usr/sap/tmp.

SAP PAS, subsequent Application Servers require uuid and uuidd packages

Ensure you meet SAP Application Server Operation System requirements. In case of packages uuid and uuidd are not installed on Oracle Linux 6 environments, please add them, plus starting the uuidd demon. Also make sure uuidd is checked for startup at OS startup (matching all runlevels that SAP application server starts at). See also

SAP Note 1635808.

Virtual host names for SAP PAS and subsequent SAP Application Servers

For high availability reasons, say you run SAP Primary Application Server Instance or, subsequent SAP Application

Server Instances in an HA capable environment (such as Oracle Cluster Ready Services), install them on virtual hostnames outside of the Oracle Database Appliance. Invoke SPWM by ./sapinst

SAPINST_USE_HOSTNAME=<virtual_host_name> to do so.

Complete the HA awareness for ASCS and ERS instances

ASCS Instance and ERS instance require own VIPs. Follow SAP Note 1496927 Protection of SAP instances through Oracle Clusterware

– use the v8.1 from the download section. Our scenario uses 10.20.88.62 and

10.20.88.64 as VIPs for ASCS and ERS, respectively. The sapctl create command create the necessary CRS resources including their dependencies on an ora.net2.network. It is noteworthy to mention to correct the invidual instance profiles from “Restart_Program_00” towards “Start_Program_00”.

[root@lsoda01]# ./sapctl create -sapsid ADO -if bond0 -nm 255.255.252.0 -net

10.20.88.0 -nodes lsoda01,lsoda02 -abapenq ASCS00 -abapvip 10.20.88.62 -abapmsport

3600 -abaprep ERS10 -aersvip 10.20.88.64

[root@lsoda01]# ./sapctl start all -sapsid ADO sapctl version 8.1 Patch 0 Production Copyright 2016 Oracle. All rights reserved

Starting SAP ABAP Enqueue service

Starting SAP ABAP Replication service

The CRS output of the additional resources created and running is listed in Appendix B.

Verify environment for user oraado

Login to each of the nodes as oraado, and env | grep ORACLE.

This should read as:

ORACLE_SID=ADO

ORACLE_HOME=/oracle/ADO/121

ORACLE_BASE=/oracle/ADO

94 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

If this is not correct, check in the environment scripts which are the correct ones. Before you move files around, please backup them. .dbenv_<hostname>.<shellname> takes precedence over the files without hostname.

SAP Database Administration with BR*Tools

The installation and configuration of BR*Tools is done by the above described Database Instance step of SWPM and installs BR*Tools 7.40 Patch 12. Usage of BR*Tools on Oracle Database Appliance to manage the Oracle database for SAP is supported. SAP Note 2087004 instructs that full support is provided with BR*Tools 7.40 Patch

14. Further information on BR*Tools can be found in SAP Notes 2087004,1598594 and 1627541.

95 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Lifecycle Management for SAP Databases

An Oracle Database Appliance requires regular patching at several levels of its software stack:

» Oracle RDBMS software

» Oracle Grid Infrastructure software

» Oracle Appliance Kit (OAK) software

» Operating system and firmware

This section describes how to install patches for the above components of an Oracle Database Appliance running databases for SAP applications. For more general information on the Oracle Database Appliance components and patches refer to My Oracle Support Note 888888.1 ("Oracle Database Appliance

– 12.1.2 and 2.x Supported ODA

Versions & Known Issues").

An Oracle Database Appliance requires the following patches and bundle patches for a complete update (with the mentioned patch versions current at the time of this write-up):

» Oracle Database Appliance Bundle Patch 12.1.2.6.0

» Oracle Database SAP Bundle Patch 12.1.2.0.2.160119 – 201602 for Oracle Database Appliance

Oracle tests and certifies these patches and their successors for SAP databases on a regular basis and makes them available for SAP customers on My Oracle Support and the SAP Service Marketplace. You can find up-to-date release information on the patches and their download locations in SAP Note 2145651 (

“Oracle Database

Appliance: Patches for 12.1.0.2

”).

Note: Each SAP Bundle Patch for the Oracle Database Appliance is certified for exactly one

particular Oracle Database Appliance version.

Hence you cannot combine SAP Bundle Patches and Oracle Database Appliance versions that are not certified to operate together. See SAP Note 2145651 for information on certified combinations of SAP Bundle Patches for ODA and Oracle Database Appliance versions.

In a nutshell, install the above mentioned patches in the following order:

1. Refer to SAP Note 2145651 to determine the required patches and their download locations.

2. Download the Oracle Database Appliance Bundle Patch and install its operating system and firmware patches.

3. Download and install the SAP Bundle Patch for ODA.

Note: Do not install the Grid Infrastructure patches and the RDBMS patches from the Oracle Database

Appliance Bundle Patch.

Instead, apply these via the SAP Bundle Patch for the Oracle Database Appliance.

Installation of the Operating System and Firmware Patches

To install the operating system and firmware patches perform the following steps:

1. Download the Oracle Database Appliance Bundle Patch to both Oracle Database Appliance nodes

2. On both Oracle Database Appliance nodes, verify your current Oracle Database Appliance version:

/opt/oracle/oak/bin/oakcli show version

3. On both Oracle Database Appliance nodes, unpack the Oracle Database Appliance Bundle Patch:

96 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

/opt/oracle/oak/bin/oakcli unpack -package <absolute_path_to_ODA_bundle_patch>

4. On the first Oracle Database Appliance node, start installation of the operating system and firmware patches of the Oracle Database Appliance Bundle Patch. The oakcli utility installs the patches automatically on both nodes.

/opt/oracle/oak/bin/oakcli update –patch <version_of_ODA_bundle_patch> \

--server

Depending on which components of the Oracle Database Appliance are getting updated this command may reboot the nodes.

See section "Patching the Infrastructure Components" in the Readme of the Oracle Database Appliance

Bundle Patch for complete information on the installation of its operating system and firmware patches.

Note: Do not install the Grid Infrastructure patches and the RDBMS patches from the Oracle

Database Appliance Bundle Patch.

Install them as described in the next section from the SAP Bundle Patch for Oracle Database Appliance instead.

Note: Installation of the Oracle Database Appliance Bundle Patch and the SAP Bundle Patch for

Oracle Database Appliance is not RAC-rolling.

Installation of the SAP Bundle Patch for the Oracle Database Appliance

Ensure that the operating system environment requirements are met on both Oracle Database Appliance nodes as described in section "Operating System Environment Requirements" of the SAP Bundle Patch Readme.

Then follow the instructions from section "SAP Bundle Patch Installation" to install the SAP Bundle Patch for the

Oracle Database Appliance. This usually comprises:

1. Installation of the latest OPatch and MOPatch utilities (self-contained)

2. Installation of the Grid Infrastructure patches in the GI homes.

3. Installation of the RDBMS patches in the RDBMS homes.

4. Execution of post-installation instructions, most notably of the catsbp.sql script, plus setting the updated

RDBMS event triggers and fix_control settings

Note: Installation of the Oracle Database Appliance Bundle Patch and the SAP Bundle Patch for Oracle

Database Appliance is not RAC-rolling.

97 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

SAP Notes

2290084

1760737

1877857

2133079

527843

1677978

1888485

2087004

2145651

1825328

1914631

1496927

2157904

819829

1171650

1680045

1627541

1635808

1521371

Documentation References

[1] Oracle Database Appliance Documentation http://www.oracle.com/technetwork/server-storage/engineered-systems/databaseappliance/documentation/index.html

[2] Upgrade of SAP NetWeaver installation to Oracle Grid Infrastructure 12.1.0.2 and Oracle Real Application

Clusters 12c Release 1 http://scn.sap.com/community/oracle

[3] Providing High Availability for SAP Resources with Oracle Clusterware 11g Release 2 and Clusterware 12c

Release 1 http://scn.sap.com/community/oracle

[4]

Relevant SAP Notes, Oracle Notes

SAP Notes

SAP Related Notes

SAP Software and Oracle Database Appliance Version 12.1

SAP Software and Oracle Database Appliance Versions 2.x (ODA)

Installation and Configuration of SAP HA ASCS/ERS on ODA

Oracle Database 12c Integration in SAP Environment

Oracle RAC support in the SAP environment

Mixed GI/RDBMS Versions or Mixed SAP/Non-SAP Environments on Exadata

Database Parameters for 12.1.0.2

BR*Tools Support for Oracle 12c

Oracle Database Appliance: Patches for 12.1.0.2

Oracle ASM and NW MDM

Oracle 12c: Central Technical Note for Oracle 12c

Protection of SAP instances through Oracle Clusterware

Oracle 12c: Conversion of compressed tables

Oracle Instant Client Installation and Configuration on Unix

Automated Oracle DB parameter check

Release Note for Software Provisioning manager 1.0 SP10

BR*Tools support for Oracle ASM and Exadata/ODA

Oracle Linux 6.x SAP Installation and Upgrade

Setting of ORACLE_BASE in SAP environments

98 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

ORACLE NOTES

Oracle Note

888888.1

1409835.1

1934030.1

337737.1

Oracle MOS Note Title

Oracle Database Appliance - 12.1.2 and 2.X Supported ODA Versions & Known Issues

ODA (Oracle Database Appliance): Deployment & Cleanup Steps

ODA (Oracle Database Appliance): HowTo export ACFS (cloudfs) using HANFS

Oracle Clusterware (CRS/GI) - ASM - Database Version Compatibility

99 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Appendix A

– crsctl output after a fresh deployment

# crsctl stat res –t

--------------------------------------------------------------------------------

Name Target State Server State details

--------------------------------------------------------------------------------

Local Resources

-------------------------------------------------------------------------------- ora.ASMNET1LSNR_ASM.lsnr

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.ASMNET2LSNR_ASM.lsnr

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.DATA.dg

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.LISTENER.lsnr

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.RECO.ACFSVOL.advm

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.RECO.DATAFSVOL.advm

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 Volume device /dev/a

sm/datafsvol-511 is

online,STABLE ora.RECO.dg

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.REDO.dg

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.net1.network

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.ons

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.proxy_advm

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.reco.acfsvol.acfs

ONLINE ONLINE lsoda01 mounted on /sapmnt,S

TABLE

ONLINE ONLINE lsoda02 mounted on /sapmnt,S

TABLE ora.reco.datafsvol.acfs

ONLINE ONLINE lsoda01 mounted on /odadataf

s,STABLE

ONLINE ONLINE lsoda02 mounted on /odadataf

s,STABLE

100 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

--------------------------------------------------------------------------------

Cluster Resources

-------------------------------------------------------------------------------- ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE lsoda02 STABLE ora.LISTENER_SCAN2.lsnr

1 ONLINE ONLINE lsoda01 STABLE ora.MGMTLSNR

1 ONLINE ONLINE lsoda01 169.254.107.203,STAB

LE ora.asm

1 ONLINE ONLINE lsoda01 Started,STABLE

2 ONLINE ONLINE lsoda02 Started,STABLE ora.cvu

1 ONLINE ONLINE lsoda01 STABLE ora.lsoda01.vip

1 ONLINE ONLINE lsoda01 STABLE ora.lsoda02.vip

1 ONLINE ONLINE lsoda02 STABLE ora.mgmtdb

1 ONLINE ONLINE lsoda01 Open,STABLE ora.oc4j

1 ONLINE ONLINE lsoda01 STABLE ora.scan1.vip

1 ONLINE ONLINE lsoda02 STABLE ora.scan2.vip

1 ONLINE ONLINE lsoda01 STABLE

--------------------------------------------------------------------------------

Appendix B - Additional Local + Cluster Resources after HA awareness

Local: ora.net2.network

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE

Cluster

: sap.ADO.ASCS00.abapenq

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.ASCS00.startsrv

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.ERS10.abaprep

1 ONLINE ONLINE lsoda01 STABLE sap.ADO.ERS10.startsrv

1 ONLINE ONLINE lsoda01 STABLE sap.ADO.abapvip

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.aersvip

1 ONLINE ONLINE lsoda01 STABLE

101 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

Appendix C

– Full CRS output after configuration

--------------------------------------------------------------------------------

Name Target State Server State details

--------------------------------------------------------------------------------

Local Resources

-------------------------------------------------------------------------------- ora.ASMNET1LSNR_ASM.lsnr

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.ASMNET2LSNR_ASM.lsnr

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.DATA.dg

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.LISTENER.lsnr

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.RECO.ACFSVOL.advm

ONLINE ONLINE lsoda01 Volume device /dev/a

sm/acfsvol-86 is onl

ine,STABLE

ONLINE ONLINE lsoda02 Volume device /dev/a

sm/acfsvol-86 is onl

ine,STABLE ora.RECO.DATAFSVOL.advm

ONLINE ONLINE lsoda01 Volume device /dev/a

sm/datafsvol-86 is o

nline,STABLE

ONLINE ONLINE lsoda02 Volume device /dev/a

sm/datafsvol-86 is o

nline,STABLE ora.RECO.dg

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.REDO.dg

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.net1.network

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.net2.network

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE

102 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

ora.ons

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.proxy_advm

ONLINE ONLINE lsoda01 STABLE

ONLINE ONLINE lsoda02 STABLE ora.reco.acfsvol.acfs

ONLINE ONLINE lsoda01 mounted on /sapmnt,S

TABLE

ONLINE ONLINE lsoda02 mounted on /sapmnt,S

TABLE ora.reco.datafsvol.acfs

ONLINE ONLINE lsoda01 mounted on /odadataf

s,STABLE

ONLINE ONLINE lsoda02 mounted on /odadataf

s,STABLE

--------------------------------------------------------------------------------

Cluster Resources

-------------------------------------------------------------------------------- ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE lsoda01 STABLE ora.LISTENER_SCAN2.lsnr

1 ONLINE ONLINE lsoda02 STABLE ora.MGMTLSNR

1 ONLINE ONLINE lsoda02 169.254.106.65 192.1

68.16.25 192.168.17.

25,STABLE ora.ado.ado_dvebmgs00.svc

1 ONLINE ONLINE lsoda02 STABLE ora.ado.db

1 ONLINE ONLINE lsoda01 Open,STABLE

2 ONLINE ONLINE lsoda02 Open,STABLE ora.asm

1 ONLINE ONLINE lsoda01 Started,STABLE

2 ONLINE ONLINE lsoda02 Started,STABLE ora.cvu

1 ONLINE ONLINE lsoda02 STABLE ora.lsoda01.vip

1 ONLINE ONLINE lsoda01 STABLE ora.lsoda02.vip

1 ONLINE ONLINE lsoda02 STABLE ora.mgmtdb

1 ONLINE ONLINE lsoda02 Open,STABLE ora.oc4j

1 ONLINE ONLINE lsoda02 STABLE ora.scan1.vip

103 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

1 ONLINE ONLINE lsoda01 STABLE ora.scan2.vip

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.ASCS00.abapenq

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.ASCS00.startsrv

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.ERS10.abaprep

1 ONLINE ONLINE lsoda01 STABLE sap.ADO.ERS10.startsrv

1 ONLINE ONLINE lsoda01 STABLE sap.ADO.abapvip

1 ONLINE ONLINE lsoda02 STABLE sap.ADO.aersvip

1 ONLINE ONLINE lsoda01 STABLE

--------------------------------------------------------------------------------

Oracle Corporation, World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065, USA

Worldwide Inquiries

Phone: +1.650.506.7000

Fax: +1.650.506.7200

104 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

C O N N E C T W I T H U S blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle oracle.com

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided

for

information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0116

Using SAP NetWeaver with Oracle Database Appliance Software 12.1.2.6.0

March 2016

Author: Torsten Grambs

Contributing Authors: Christoph Kurucz, Jens Schmidt, Kurt Brög, Andreas Becker, Jan Klokkers, Martin Sautter (in remembrance)

2 | USING SAP NETWEAVER WITH THE ORACLE DATABASE APPLIANCE 12.1.2.6.0

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Download PDF

advertisement