You are on page 1of 75

AnOracleWhitePaper

March2014

UsingSAPNetWeaverwiththeOracle
DatabaseAppliance2.9
ABestPracticesGuide

Preface...........................................................................................................................3

OracleDatabaseApplianceInstallationOverview..........................................................5

ASMDiskGroupsforSAPDatabases...........................................................................7

ClusteringSolutionforSAPHAonOracleDatabaseAppliance....................................8

NewerSAPNetWeaverProductsonOracleDatabaseAppliance.................................8

CharacterSetRequirementsforSAPDatabases..........................................................8

NonUnicodeSAPInstallations.......................................................................................8

SharedFileSystemsinSAPEnvironments...................................................................10

OracleDatabaseApplianceforSAPDeployment..........................................................11

SAPOracleHomeNamingRequirements.....................................................................22

UsingSAPinstontheOracleDatabaseAppliance.........................................................23

SAPinst:OracleDatabaseInstance...............................................................................40

PostSAPinstInstallationSteps......................................................................................65

SAPDatabaseAdministrationwithBR*Tools.................................................................66

LifecycleManagementforSAPDatabases....................................................................67

InstallationoftheOperatingSystemandFirmwarePatches..........................................68

InstallationoftheSAPBundlePatchfortheOracleDatabaseAppliance......................69

MigrationofSAPDatabases...........................................................................................70

MigrationApproach1:OracletoOracle(O2O)ACSServiceandCustomerSelfService...70


MigrationApproach2:OracletoOracle(TripleO)ACSServiceonly...........................71

MigrationApproach3:OracleRMANandTransportableTablespaces..........................73

DocumentationReferences:...........................................................................................74

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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:

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Oracle Database End User


Appliance
Bundle
Version
Version

Grid
Database
Infrastructu Version
re Version

2.9.0.0.0

11.2.0.4

2.9.0.0.0

11.2.0.4.0
Single
Instance
11.2.0.4.0
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 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.

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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 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.

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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.

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

ASMDiskGroupsforSAPDatabases
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.

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

ClusteringSolutionforSAPHAonOracleDatabaseAppliance
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-

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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.

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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 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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

OracleDatabaseApplianceforSAPDeployment
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 2.9.0.0 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 2.8.0.0 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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Choose SAP Application.

12

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Set your System Name, with Help you get answers, what is meant
with each input.

14

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

15

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

ODA supports beside the public network other network if needed.

16

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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

17

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

18

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

In case you will use Oracle Database Appliance to provide /sapmnt,


this mask is to setup an Oracle CloudFS/ACFS file system.

19

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Use Install to start the deployment.

20

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

21

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

SAPOracleHomeNamingRequirements
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/11.2.0.4/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/11.2.0.4/dbhome_1 /oracle/ADO/112

Repeat above steps on the second node

[root@lsoda02 / ]# mkdir /oracle


[root@lsoda02 / ]# chown oracle:oinstall /oracle
[root@lsoda02 / ]# su oracle
create the symbolic link
[oracle@lsoda02 / ]# mkdir -p /oracle/ADO

[oracle@lsoda02 / ]# ln -s

/u01/app/oracle/product/11.2.0.4/dbhome_1 /oracle/ADO/112

22

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

UsingSAPinstontheOracleDatabaseAppliance
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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Select Custom Mode.

24

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Deselect Profiles are available, we have no SAP profiles with a


new installation.

25

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

27

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

28

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

29

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Set the Oracle SID, select RAC on Oracle ASM and the type of RAC
on Engineered Systems.

30

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

31

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

32

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

33

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

34

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Set the ORACLE_HOME for GRID and the ASM instance.

35

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

36

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

37

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

38

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Repeat the step Database Instance Preparation on the second


node.

39

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

SAPinst:OracleDatabaseInstance
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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

41

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

42

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

43

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

44

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

45

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

46

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

47

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

48

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

49

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

50

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Before you choose <Next> verify the OS user oracle belongs to OS


group sapinst !

51

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

52

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

53

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

54

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

55

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

56

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

All Control Files are located on the ASM Diskgroup +DATA. If plan
more then one Control File you have to use different names.

58

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

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

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

60

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

61

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

62

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

63

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

64

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

PostSAPinstInstallationSteps
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 second node lsoda02 :


ADO2:/oracle/ADO/112:N

the syntax is: database instance name (ADO1 or ADO2) : oracle


home directory (/oracle/ADO/112) : startup on boot (Y or N)
the script oraenv sets the environment dependent on the entries
of /etc/oratab
Example:
>. oraenv
ORACLE_SID = [+ASM1] ? ADO1
The Oracle base has been changed from /u01/app/grid to
/u01/app/oracle

As SAPinst runs only on one node, we have to copy some files from
the installation node to the secondary node.
-login on installation node
-change to directory <ORACLE_HOME>/dbs
-scp init<ORACLE_SID2> .ora to
<node2>:/<ORACLE_HOME>/dbs/init<ORACLE_SID2>.ora

65

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

SAPDatabaseAdministrationwithBR*Tools
The installation and configuration of BR*Tools is done by the above
described Database Instance step of SAPinst. Therefore you can use
BR*Tools on the Oracle Database Appliance to manage the Oracle
database for SAP. More related information on BR*Tools can be
found in SAP Notes 1598594, 1598868 and 1627541.

66

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

LifecycleManagementforSAPDatabases
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, see My Oracle
Support Note 888888.1 ("Oracle Database Appliance - 2.x Supported
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 writing):
ODA Bundle Patch 2.9.0.0.0
SAP Bundle Patch 11.2.0.4.1 - 201402 for ODA
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 1975175 ("ODA 11.2.0: Patches for
11.2.0.4").
Note: Each SAP Bundle Patch for the Oracle Database
Appliance is certified for only one specific Oracle Database
Appliance version.
You must not combine SAP Bundle Patches and Oracle Database
Appliance versions that are not certified to operate together. For
example, SAP Bundle Patches 11.2.0.3.4 - 201211, 201212, and
201301 must be installed on ODA version 2.4.1.0.0 only, and must
not be installed on ODA version 2.5.0.0.0 or later. See SAP Notes
1785353 and 1975175. for information on certified combinations of
SAP Bundle Patches for ODA and ODA versions.
In a nutshell, you install the above patches in the following steps:
1. Refer to SAP Note 1975175 to determine the required
patches and their download locations.
2. Download the ODA Bundle Patch and install its operating
system and firmware patches.
3. Download and install the SAP Bundle Patch for ODA.

67

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

Note: Do not install the Grid Infrastructure patches and the


RDBMS patches from the Oracle Database Appliance Bundle
Patch.
Install them in the last step from the SAP Bundle Patch for the
Oracle Database Appliance instead.

InstallationoftheOperatingSystemandFirmwarePatches
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:
/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> --infra
Depending on which components of the Oracle Database
Appliance are 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.

68

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

InstallationoftheSAPBundlePatchfortheOracleDatabaseAppliance
Ensure that the operating system environment requirements are
fulfilled 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:
Installation of the latest OPatch and MOPatch utilities.
Installation of the Grid Infrastructure patches in the grid
homes.
Installation of the RDBMS patches in the RDBMS homes.
Execution of post-installation instructions, most notably of the
catsbp.sql script.
Note: Installation of the Oracle Database Appliance Bundle
Patch and the SAP Bundle Patch for Oracle Database
Appliance is not RAC-rolling.

69

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

MigrationofSAPDatabases

Although there are several possibilities to migrate an existing SAP


database to the Oracle Database Appliance it is recommended to
choose one of the following approaches as these have been
successfully tested.

MigrationApproach1:OracletoOracle(O2O)ACSServiceand
CustomerSelfService
This way of database migration exists for many years and is being
used to migrate an SAP database between different systems. The
method is also described in the SAP Note 1508271. O2O allows for
homogenous and heterogeneous system copies.
A homogenous system copy is a migration where the source and
target operating system is the same. A heterogeneous system copy
is a migration where the source and target system have different
operating systems. With an heterogeneous system copy you can for
instance migrate an existing SAP AIX database to an Oracle
Database Appliance Linux database.
O2O supports all operating systems SAP products are certified on.
The advantage of this method is, that you can combine the operating
system change with multiple options to get most out of the
migration:

As part of the database migration, the whole database is


reorganized. This can free up a significant amount of space
within tables and indexes.

The tablespace layout can be changed to the new SAP


standard or to a customer own customized one. It is also
possible to move single tables and indexes to separate
tablespaces or to merge them into existing or new ones. This
allows you to unify the SAP landscape by using a default
tablespace name like PSAPSR3 in all SAP systems

The SAP schema name can be changed for instance to

SAPSR3 to unify the SAP landscape.

The number of data files and mount points can be


significantly reduced, by either optimizing the tablespace
layout or the size of the data files and file systems

Tablespaces are created with LMTS and ASSM

Data files will be converted from file systems to Oracle ASM

LOB or LONG data types can be converted to Secure files


(11.2 only)

70

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

You can compress the indexes on the target database by


using Oracle index compression. The compression calculation
is executed as described in SAP Note 1109743. The correct
index compression for each index is determined
automatically.

You can compress tables on the target system. The


compression will compress all SAP tables as recommended in
SAP Note 1431296.

With O2O it is possible to combine a platform migration with


a release upgrade. The migration method supports every
combination of Unix, Windows or Linux on source and target
system. So you can migrate an existing Oracle 10.2 database
on HP-UX to an Oracle Database Appliance.

It is possible to upgrade directly to an higher database


release. Currently with the O2O method direct database
migrations are possible between different Oracle versions. So
it is possible to upgrade directly from Oracle 9i to Oracle 11g
by using O2O. You also do not need the most current patchset
of the lower Oracle release to run the migration. A complete
overview about the upgrade paths between different Oracle
versions is given at the end of this chapter.

The downtime needed to migrate a database with the O2O method is


depending on the database size, the included database objects (SAP
cluster tables, partitioned tables) and the available hardware
resources(CPU, Memory, Storage, Network). Up to 1TB/hour is
possible.

MigrationApproach2:OracletoOracle(TripleO)ACSServiceonly
If the downtime requirements cannot be fulfilled with the O2O
offline method, you can use as an alternative the Triple-O method.
The Triple-O method allows to migrate an Oracle database with a
downtime for the database copy of not more than 15 minutes. The
downtime is independent from the database size. The downtime is
needed to stop the SAP system on the source, check the final
synchronization of the migrated system and to restart SAP on the
target system.
The Triple-O method is a further development of the O2O method.
This method is certified by SAP to perform an online migration and
documented in SAP Note 1508271. So all systems migrated with
this method are fully supported by SAP after the migration.
The Triple-O method is using the O2O technology to perform the
initial data load (copying the current contents of the source
database to the target database) while the SAP application is up and
running. Oracle GoldenGate is used to synchronize all changes

71

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

applied on the source system, while the migration is running. The


method fully supports DDL and DML operations. There are no
limitations for the usage of the SAP system during the migration.
With the Triple-O method you can make use of all features listed for
the O2O method. Also heterogeneous database migrations and
direct database upgrades are supported.
When using Triple-O:

There is no downtime needed to start or stop the online


migration

No need for special database patches

Migration can be started and stopped at any time without risk


for the productive system

Downtime needed for the database copy part of the migration


is typically only 15 minutes. The downtime is independent
from the database size.

Triple-O fully supports DDL and DML commands

Triple-O is SAP release independent

Prerequisites for Triple-O:


At least Oracle version 9i on source

30% free CPU time in average on database server

Additional file system space of 50% of the redo log amount in


24h on the source

Additional file system space of 50% of the redo log amount in


48h (or the duration of the initial data load) on the target

Limitations of Triple-O:

Oracle GoldenGate currently does not support compressed


tables on the source system. These tables must be either
decompressed before the migration, or must be migrated at
the end in a downtime windows

Impact on productive system:


Increased redo log volume, because supplemental logging


must be activated on the source

Summary:
These well established methods offer a fast and reliable approach,
not only to migrate a SAP database from any SAP supported OS
platform from Oracle Database 9i Release 2 on to the Oracle
Database Appliance, but also to implement a couple of additional
features and benefits into the migration process. This adds more
value to the database migration and will increase the ROI for

72

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

instance by reducing the storage costs with table/index


compression.

MigrationApproach3:OracleRMANandTransportableTablespaces
Through the DUPLICATE DATABASE command of Oracle RMAN it is
possible to copy an existing Linux, Solaris or Windows database
running on an x86_64 platform to the Oracle Database Appliance
without any downtime.
By using Transportable Tablespaces it is possible to copy an existing
database from any UNIX platform to the Oracle Database Appliance.
Both ways are explained in detail in the document Moving your
SAP Database to Oracle Automatic Storage Management 11g
Release 2. The document can be downloaded from the SAP
Community Network (SCN) under
http://scn.sap.com/community/oracle.

73

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

DocumentationReferences:
[1] Oracle Database Appliance Documentation
http://www.oracle.com/technetwork/server-storage/engineeredsystems/database-appliance/documentation/index.html
[2] Configuration of SAP NetWeaver for Oracle Grid Infrastructure
11.2.0.2 and Oracle Real Application Clusters 11g Release 2: A Best
Practices Guide
http://scn.sap.com/community/oracle
[3] SAP Databases on Oracle Automatic Storage Management 11g
Release 2: Configuration Guidelines for Unix and Linux Platforms
http://scn.sap.com/community/oracle
[4] Relevant SAP Notes:

1760737 SAP Software and Oracle Database Appliance


(ODA)

1785353 ODA 11.2.0: Patches for 11.2.0.3

1975175 ODA 11.2.0: Patches for 11.2.0.4

1431798 Oracle 11.2.0: Database Parameter Settings

1550133 Oracle Automatic Storage Management (ASM)

1877857 Installation and Configuration of SAP HA

ASCS/ERS on ODA

1496927 - Protection of SAP instances through Oracle


Clusterware

1627541 - BR*Tools support for Oracle ASM and

Exadata/ODA

1973403 - SWPM for Oracle Exadata or Oracle Database


Appliance on Oracle Linux 5

74

UsingSAPNetWeaverwiththeOracleDatabaseAppliance

UsingSAPNetWeaverwiththeOracle
ExadataDatabaseMachine
March2014
Author:MartinSautter
ContributingAuthors:AnilNair,Tammy

Copyright2012,Oracleand/oritsaffiliates.Allrightsreserved.Thisdocumentisprovidedforinformationpurposes

Bednar,JanKlokkers,JensSchmidt,

onlyand

ChristophKurucz

thecontentshereofaresubjecttochangewithoutnotice.Thisdocumentisnotwarrantedtobeerrorfree,norsubject
toanyotherwarrantiesorconditions,whetherexpressedorallyorimpliedinlaw,includingimpliedwarrantiesand

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
OracleCorporation
WorldHeadquarters
500OracleParkway

conditionsofmerchantabilityor
fitnessforaparticularpurpose.Wespecificallydisclaimanyliabilitywithrespecttothisdocumentandnocontractual
obligationsareformedeitherdirectlyorindirectlybythisdocument.Thisdocumentmaynotbereproducedor
transmittedinanyformorbyany
means,electronicormechanical,foranypurpose,withoutourpriorwrittenpermission.
OracleisaregisteredtrademarkofOracleCorporationand/oritsaffiliates.Othernamesmaybetrademarksoftheir
respectiveowners.

RedwoodShores,CA94065
U.S.A.

1112

75

You might also like