Using SAP NetWeaver with the Oracle Database Appliance · 2019. 11. 12. · Oracle Database...
Transcript of Using SAP NetWeaver with the Oracle Database Appliance · 2019. 11. 12. · Oracle Database...
An Oracle White Paper November 2012 Update September 2013
Using SAP NetWeaver with the Oracle Database Appliance
A Best Practices Guide
Preface .............................................................................................. 3
Oracle Database Appliance Installation Overview .............................. 5
ASM Disk Groups for SAP Databases ............................................ 7
Character Set Requirements for SAP Databases ............................... 8
Non-Unicode SAP Installations .......................................................... 8
Shared File Systems in SAP Environments ....................................... 9
Oracle Database Appliance for SAP Deployment ............................. 10
SAP Oracle Home Naming Requirements ....................................... 21
Using SAPinst on the Oracle Database Appliance ........................... 22
SAPinst: Oracle Database Instance ................................................. 36
Post SAPinst Installation Steps ........................................................ 58
SAP Database Administration with BR*Tools ................................... 59
Lifecycle Management for SAP Databases ...................................... 60
Installation of the Operating System and Firmware Patches ............ 61
Installation of the OAK Patch for SAP .............................................. 62
Installation of the SAP Bundle Patch for the Oracle Database Appliance .. 62
Migration of SAP Databases ........................................................... 63
Migration Approach 1: Oracle-to-Oracle (O2O) ACS Service and Customer
Self-Service ..................................................................................... 63
Migration Approach 2: Oracle-to-Oracle (Triple-O) ACS Service only64
Migration Approach 3: Oracle RMAN and Transportable Tablespaces65
Documentation References: ............................................................ 66
Using SAP NetWeaver with the Oracle Database Appliance
3
Preface
This document explains all the necessary steps to setup an SAP system based on the SAP
NetWeaver technology using an Oracle Database Appliance.
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).
The following table shows the minimum required versions of Oracle software when
running SAP applications with the Oracle Database Appliance:
Oracle Database Appliance Version
End User Bundle Version
Grid Infrastructure Version
Database Version
2.4.0.0.0 plus OAK Patch 2.4.1.0.0 for SAP (*)
2.4.0.0.0
11.2.0.3.4 11.2.0.3.4 Single Instance 11.2.0.3.4 RAC
(*) The OAK Patch for SAP is only available on the SAP Service Marketplace. Please check
SAP Note 1785353 for more details.
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
Using SAP NetWeaver with the Oracle Database Appliance
4
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.
Using SAP NetWeaver with the Oracle Database Appliance
5
Oracle Database Appliance Installation Overview
To set up your Oracle Database Appliance for an SAP database, you must follow the
below steps:
1. Re-image the Oracle Database Appliance
If the Oracle Database Appliance is delivered with a factory image of version
less than 2.4.0.0.0, you must re-image the Oracle Database Appliance with the OS
ISO Image 2.4.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.4.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 any additional, SAP-specific required Oracle Database Appliance
Patches.
For example, for the Oracle Database Appliance version 2.4.0.0.0 it is required to
install OAK Patch 2.4.1.0.0 for SAP before continuing with the Oracle Database
Appliance setup. You can download the OAK Patch 2.4.1.0.0 for SAP from the
SAP Service Marketplace following the instructions in SAP Note 1785353 and
install it according to the instruction in section "Installation of the OAK Patch
for SAP" of this white paper.
4. 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.
5. Use SAPinst to prepare the Oracle Database Appliance for an SAP
database
Run SAPinst as described in section "Using SAPinst on the Oracle Database
Appliance" of this white paper to create SAP-specific OS users, create SAP-
specific directories, and otherwise prepare the Oracle Database Appliance for an
SAP database.
6. 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 and database patches installed. For the Oracle Database Appliance, these are
delivered in the SAP Bundle Patch for Oracle Database Appliance on the SAP
Using SAP NetWeaver with the Oracle Database Appliance
6
Service Marketplace. You can download the latest SAP Bundle Patch for the
Oracle Database Appliance following the instructions in SAP Note 1785353 and
install it according to the instruction in section "Installation of the SAP Bundle
Patch for ODA" of this white paper.
7. 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.
Using SAP NetWeaver with the Oracle Database Appliance
7
ASM Disk Groups for SAP Databases
The default ASM Disk Groups provided by the Oracle Database Appliance should be
used for all SAP databases. For SAP production databases a redundancy level of high
should be used to achieve the highest level of protection against any type of storage
failure. Other SAP databases used for development, test and QA may use a normal ASM
redundancy level.
In line with the standard Oracle Database Appliance setup you should use the ASM disk
Groups “+DATA”, “+REDO” and “+RECO”. The DATA Group should contain all data
files, control files, spfiles, OCR and voting disks. The RECO Group should contain
temporary files, archive logs, flashback files and backups. The REDO Group should
contain all non-multiplexed redo log files.
When storing more than one SAP database (for instance an SAP ERP database and an
SAP BW database or an SAP ERP database with an SAP CRM database or multiple SAP
ERP databases) on the Oracle Database Appliance all files of each of these SAP databases
should follow the above recommendation and all be stored in the DATA , REDO and
RECO disk groups.
For performance and throughput reasons it is recommended for each SAP database to
only have two control files in the DATA disk group and non-multiplexed online redo log
files in the REDO disk group. As standard SAP installations use three control files in the
database it is recommended to remove one control file from the spfile or init.ora. Standard
SAP installations also use two members for each online redo log file. On the Oracle
Database Appliance it is therefore necessary to remove one member of each online redo
log file for each redo thread. The source database will have multiple redo threads if it was
a RAC database. Three control files and multiplexed online redo log files are not needed
on the Oracle Database Appliance as the control files and the online redo log files are
stored in the DATA and REDO disk groups which already provide triple mirroring for
each file at the Oracle ASM level due to the redundancy level of high.
Using SAP NetWeaver with the Oracle Database Appliance
8
Character Set Requirements for SAP Databases
New installations of SAP systems from NetWeaver 7.0 on only support 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. When deploying the Oracle Database Appliance for an
SAP Unicode system with the oakcli deploy command it is therefore mandatory to specify
UTF8 for the database character set. The national character set is automatically set to
UTF8 when the database character set UTF8 is chosen.
So please make sure that the default database and additional required databases for SAP
systems on the Oracle Database Appliance are always created with the SAP required
UTF8 database character set.
Non-Unicode SAP Installations
Existing Non-Unicode SAP installations can be used with the Oracle Database Appliance.
It is important for these Non-Unicode installations that the character and national
character set of the migrated databases from existing systems to the Oracle Database
Appliance are kept the same as in the original system. The character set will be WE8DEC.
The national character has to be always UTF8.
With the Oracle Database Appliance the national character is automatically set to UTF8
when the database character set WE8DEC is chosen.
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 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.
Using SAP NetWeaver with the Oracle Database Appliance
9
Shared File Systems in SAP Environments
In an SAP environment it is common that all SAP Application Servers have access to a
shared file system (/sapmnt, /usr/sap/trans, ...) which store the SAP kernels, profiles,
trace files and provide the global SAP transport directory. In typical SAP installations such
a shared file system is implemented using a NAS appliance, a cluster file system or through
an NFS exported file system from the database server. For high availability reasons a
cluster file system is being used or the source of the NFS location is protected by special
configurations such as HA-NFS to not be a single point of failure in an SAP environment.
If you already have an existing shared file system solution in your SAP environment not
using an NFS exported file system from the database server it is recommended to
continue to use this solution when moving to the Oracle Database Appliance.
The Oracle Database Appliance offers during the deployment phase the configuration of
a Cloud File System. This file system is based on Oracle's Advanced Cluster File System
(ACFS) and can be used for /sapmnt on all application servers, if it is NFS exported from
the database server.. After the deployment you can add additional file systems like
/usr/sap/trans,..., using Advanced Storage Management Configuration Assistance
(asmca).
Using SAP NetWeaver with the Oracle Database Appliance
10
Oracle Database Appliance for SAP Deployment
This section describes the deployment of the ODA End User Bundle for SAP. The
deployment installs the Oracle Grid and RDBMS software and creates an Oracle Grid
instance and an Oracle database.
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 and any
additional, SAP-specific required Oracle Database Appliance patches installed. See
above section "Oracle Database Appliance Installation Overview" for more details.
The next pages show a step by step deployment.
Login as user root on the first node
Change to directory /tmp
Run the deployment:: /opt/oracle/oakcli/bin/oakcli deploy
Using SAP NetWeaver with the Oracle Database Appliance
11
Using SAP NetWeaver with the Oracle Database Appliance
12
Using SAP NetWeaver with the Oracle Database Appliance
13
Using SAP NetWeaver with the Oracle Database Appliance
14
The Database Class depends on your need. Please use <Help> to verify the possible
database class sizes. For a first dummy database use Very Small.
Using SAP NetWeaver with the Oracle Database Appliance
15
In this example deployment we use the Oracle Cloud FileSystem for the SAP shared file
system /sapmnt.
Do not select button <Install> here, but rather save the configuration to edit it in the next
steps.
Using SAP NetWeaver with the Oracle Database Appliance
16
Using SAP NetWeaver with the Oracle Database Appliance
17
At this point cancel the Oracle Application Manager, edit the configuration file and
change the uid (DBUSERNO, CRSUSERNO) and gid (OINSTGROUPNO,
RACDBAGROUPNO,...) according to your IT needs. Restart the Oracle Application
Manager and load the changed configuration file. Use next and step to the Summary
screen.
Edit the configuration file:
...
# USER/GROUP INFO STANDARDROLE=1 CRSUSR=oracle CRSUSRNO=502 DBUSR=oracle DBUSRNO=502 OINSTGROUP=oinstall OINSTGROUPNO=508 RACDBAGROUP=dba RACDBAGROUPNO=502 RACOPERGROUP=oper RACOPERGROUPNO=507 OSASMGROUP=asmdba OSASMGROUPNO=505 OSASMOPERGROUP=asmoper OSASMOPERGROUPNO=506 OSASMADMINGROUP=asmadmin OSASMADMINGROUPNO=504
...
Restart /opt/oracle/oak/bin/oakcli deploy
Using SAP NetWeaver with the Oracle Database Appliance
18
Use button <Next> to step to the Configuration type, choose SAP Application, and load
the configuration file.
Using SAP NetWeaver with the Oracle Database Appliance
19
Step to the Summary.
Start the deployment using the button <Install>.
Using SAP NetWeaver with the Oracle Database Appliance
20
Using SAP NetWeaver with the Oracle Database Appliance
21
SAP Oracle Home Naming Requirements
The correct installation and operation of any SAP utility such as SAPinst or BR*Tools on
the database nodes of the Oracle Database Appliance requires some preparation for the
correct setting of the ORACLE_HOME environment variable in the SAP environment.
The SAP environment requires the ORACLE_HOME environment variable to be set to
/oracle/<SID>/<release>.
To create an SAP database, SAPinst searches for the ORACLE_HOME directory. If there
is a usable installation with the Oracle RDBMS software correctly installed SAPinst will
not extract the RDBMS DVD, it will use the existing installation.
SAPinst looks for the RDBMS software in /oracle/<SID>/<release> the standard path
of SAP for the Oracle RDBMS software . The ODA deployment installs the RDBMS
software under /u01/app/oracle/product/11.2.0.3/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>
– [root@lsoda01 / ]# mkdir /oracle
– [root@lsoda01 / ]# chown oracle:oinstall /oracle
– [root@lsoda01 / ]# su – oracle
– create the symbolic link
– [oracle@lsoda01 / ]# mkdir -p /oracle/OS1
– [oracle@lsoda01 / ]# ln -s /u01/app/oracle/product/11.2.0.3/dbhome_1
/oracle/OS1/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/OS1
– [oracle@lsoda02 / ]# ln -s /u01/app/oracle/product/11.2.0.3/dbhome_1
/oracle/OS1/112
Using SAP NetWeaver with the Oracle Database Appliance
22
Using SAPinst on the Oracle Database Appliance
SAP has changed the installation utility SAPinst to work on the Oracle Database
Appliance. The next pages show the Oracle Database Appliance related steps from a
perspective of SAPinst. We start SAPinst with the step “Database Instance Preparation”
to create SAP-specific OS users, create SAP-specific directories, and otherwise prepare the
Oracle Database Appliance for an SAP database.
Using SAP NetWeaver with the Oracle Database Appliance
23
Using SAP NetWeaver with the Oracle Database Appliance
24
Using SAP NetWeaver with the Oracle Database Appliance
25
Using SAP NetWeaver with the Oracle Database Appliance
26
Using SAP NetWeaver with the Oracle Database Appliance
27
Using SAP NetWeaver with the Oracle Database Appliance
28
Using SAP NetWeaver with the Oracle Database Appliance
29
Using SAP NetWeaver with the Oracle Database Appliance
30
Using SAP NetWeaver with the Oracle Database Appliance
31
Using SAP NetWeaver with the Oracle Database Appliance
32
Using SAP NetWeaver with the Oracle Database Appliance
33
Using SAP NetWeaver with the Oracle Database Appliance
34
Using SAP NetWeaver with the Oracle Database Appliance
35
Repeat the step “Database Instance Preparation” on the second node.
Using SAP NetWeaver with the Oracle Database Appliance
36
SAPinst: Oracle Database Instance
Dependent on your installation needs, it is required to install the necessary SAP instances
(ASCS, SCS, ...) first, as described in the SAP Installation Guide.
After that you can start the database installation described on the next pages.
Using SAP NetWeaver with the Oracle Database Appliance
37
Using SAP NetWeaver with the Oracle Database Appliance
38
Using SAP NetWeaver with the Oracle Database Appliance
39
Using SAP NetWeaver with the Oracle Database Appliance
40
Using SAP NetWeaver with the Oracle Database Appliance
41
Using SAP NetWeaver with the Oracle Database Appliance
42
Using SAP NetWeaver with the Oracle Database Appliance
43
Using SAP NetWeaver with the Oracle Database Appliance
44
Using SAP NetWeaver with the Oracle Database Appliance
45
Before you choose <Next> verify the OS user oracle belongs to OS group sapinst !
Using SAP NetWeaver with the Oracle Database Appliance
46
Using SAP NetWeaver with the Oracle Database Appliance
47
Using SAP NetWeaver with the Oracle Database Appliance
48
Using SAP NetWeaver with the Oracle Database Appliance
49
Using SAP NetWeaver with the Oracle Database Appliance
50
Using SAP NetWeaver with the Oracle Database Appliance
51
Using SAP NetWeaver with the Oracle Database Appliance
52
Using SAP NetWeaver with the Oracle Database Appliance
53
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"
Using SAP NetWeaver with the Oracle Database Appliance
54
Using SAP NetWeaver with the Oracle Database Appliance
55
Using SAP NetWeaver with the Oracle Database Appliance
56
Using SAP NetWeaver with the Oracle Database Appliance
57
Using SAP NetWeaver with the Oracle Database Appliance
58
Post SAPinst Installation Steps
Setup the environment for your new database on each node, edit the file /etc/oratab and
add the lines:
on first node lsoda01:
OS11:/oracle/OS1/112:N
on second node lsoda02 :
OS12:/oracle/OS1/112:N
the syntax is: database instance name (OS11 or OS12) : oracle home directory
(/oracle/OS1/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] ? OS11
The Oracle base has been changed from /u01/app/grid to /u01/app/oracle
As SAPinst runs only on one node, we do 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
Using SAP NetWeaver with the Oracle Database Appliance
59
SAP Database Administration with BR*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 and 1598868.
Using SAP NetWeaver with the Oracle Database Appliance
60
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, 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.4.0.0.0
• OAK Patch 2.4.1.0.0 for SAP
• SAP Bundle Patch 11.2.0.3.4 - 201211 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 1785353 ("ODA 11.2.0: Patches for 11.2.0.3").
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 Note 1785353 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 1785353 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 OAK Patch for SAP.
4. 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.
Using SAP NetWeaver with the Oracle Database Appliance
61
Install them in the last step from the SAP Bundle Patch for the Oracle Database
Appliance instead.
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:
/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.
Using SAP NetWeaver with the Oracle Database Appliance
62
Installation of the OAK Patch for SAP
To install the OAK Patch for SAP, perform the following steps:
1. Download the OAK Patch for SAP to both Oracle Database Appliance nodes
2. On both Oracle Database Appliance nodes, verify your current Oracle Database
Appliance version:
/opt/oracle/oakcli/bin/oakcli show version
3. On both Oracle Database Appliance nodes, unpack the OAK Patch for SAP:
/opt/oracle/oakcli/bin/oakcli unpack -package
<absolute_path_to_OAK_patch_for_SAP>
4. On the first Oracle Database Appliance node, start installation of the OAK Patch
for SAP. The oakcli utility installs the patch automatically on both nodes.
/opt/oracle/oakcli/bin/oakcli update -patch <version_of_OAK_patch_for_SAP> --infra
See the readme of the OAK Patch for SAP for complete installation instructions.
Installation of the SAP Bundle Patch for the Oracle Database Appliance
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.
Using SAP NetWeaver with the Oracle Database Appliance
63
Migration of SAP Databases
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.
Migration Approach 1: Oracle-to-Oracle (O2O) ACS Service and Customer Self-Service
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)
• 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.
Using SAP NetWeaver with the Oracle Database Appliance
64
• 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.
Migration Approach 2: Oracle-to-Oracle (Triple-O) ACS Service only
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
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
Using SAP NetWeaver with the Oracle Database Appliance
65
• 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 instance by reducing the storage costs with
table/index compression.
Migration Approach 3: Oracle RMAN and Transportable Tablespaces
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.
Using SAP NetWeaver with the Oracle Database Appliance
66
Documentation References:
[1] Oracle Database Appliance Documentation
http://www.oracle.com/technetwork/server-storage/engineered-systems/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
• 1431798 – Oracle 11.2.0: Database Parameter Settings
• 1550133 – Oracle Automatic Storage Management (ASM)
Using SAP NetWeaver with the Oracle Database Appliance
67
Using SAP NetWeaver with the
Oracle Exadata Database
Machine
November 2012
Author: Martin Sautter
Contributing Authors: Anil Nair,
Tammy Bednar, Jan Klokkers,
Jens Schmidt
Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A.
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Copyright © 2013, 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 is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
1112
www.sap.com
© 2013 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP
products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL
Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are
registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials
are provided by SAP AG and its affiliated companies ("SAP Group")
for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express
warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional
warranty. .