Using SAP NetWeaver With The Oracle

An Oracle White Paper November 2012
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 only...64 Migration Approach 3: Oracle RMAN and Transportable Tablespaces. 65 Documentation References:................................................................... 66
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 .! are certi"ied and supported to be used #ith the Oracle Database Appliance. There"ore SAP products such as SAP $%P &.!' SAP $(( &.!' SAP )W .!' SAP (%* .! ' SAP S%* .! or SAP Solutions such as SAP )an+ing Services version .! can be used #ith the Oracle Database Appliance. SAP products #hich are not based on SAP NetWeaver Technology such as SAP )usiness Ob,ects cannot be used #ith the Oracle Database Appliance. The Oracle Database Appliance provides the "ollo#ing capabilities "or an SAP environment .ighly available active/active clustered database server "or SAP Applications .ighly available "ile server "or SAP re0uired shared "ile systems such as 1sapmnt (omplete clustering solution "or SAP .igh Availability %esources such as (entral Services "or both A)AP and 2AVA stac+
The Oracle Database Appliance cannot be used to run SAP application instances. SAP application instances have to run on separate machines #hich use the $thernet net#or+ to exchange data #ith the database3s4 on the Oracle Database Appliance. 5n SAP terminology this is called a three tier architecture. This "lexible three tier architecture allo#s "or any combination o" hard#are and operating systems running the SAP instances to be used #ith the Oracle Database Appliance. So "or example you can run or +eep existing SAP Application servers on A56 or .P/76 plat"orms connected to the Oracle Database Appliance. This "lexibility allo#s "or an easy introduction o" the Oracle Database Appliance in existing SAP environments as it leaves the SAP application layer unchanged. The only SAP components #hich are supported to run on the Oracle Database Appliance are the SAP database administration tools 3)%8Tools4 and the SAP (entral Services 3S(S and AS(S4. The "ollo#ing table sho#s the minimum re0uired versions o" Oracle so"t#are #hen running SAP applications #ith the Oracle Database Appliance-
Oracle Database Appliance Version
$nd 7ser 9rid Database )undle Version 5n"rastructure Version Version ==.:.!.>.; ==.:.!.>.; Single 5nstance ==.:.!.>.; %A(
:.;.!.!.! plus :.;.!.!.! OA< Patch :.;.=.!.! "or SAP 384

384
The OA< Patch "or SAP is only available on the SAP Service *ar+etplace. Please chec+ SAP Note = ?@>@> "or more details.
When using SAP applications #ith the Oracle Database Appliance you can either use single instance Oracle Database ==g %elease : or Oracle %eal Application (lusters ==g %elease :. Oracle %eal Application (lusters One Node is not supported #ith SAP products and there"ore cannot be used. The paper describes the SAP speci"ic deployment and con"iguration o" necessary Oracle so"t#are settings on the Oracle Database Appliance' SAP speci"ic database re0uirements' in"ormation on ho# to install SAP re0uired database patches "or the Oracle Database Appliance and suggestions "or the implementation o" shared "ile systems "or SAP installations. SAP Note = &! > #ill be updated on a regular base to re"lect any changes on using SAP Applications #ith the Oracle Database Appliance. Overall this document complements the existing Oracle Database Appliance documentation A=B and there"ore it is assumed that the reader is "amiliar #ith the Oracle Database Appliance documentation. To understand the re0uirements and steps outlined in this document it is necessary that the reader is also "amiliar #ith the SAP speci"ic support notes and #hite papers on Oracle %A( A:B and Oracle AS* A>B. SAP support notes A;B are available on the SAP Service *ar+etplace "or authoriCed users.
Oracle Database Appliance Installation Overview

To set up your Oracle Database Appliance "or an SAP database' you must "ollo# the belo# steps=. Re-image the Oracle Database Appliance 5" the Oracle Database Appliance is delivered #ith a "actory image o" version less than :.;.!.!.!' you must re/image the Oracle Database Appliance #ith the OS 5SO 5mage :.;.!.!.! or later. Dou can do#nload the 5SO image "ollo#ing the lin+s in Oracle Support Note ??????.= and install it according to the instructions in the Oracle Database Application documentation. :. Install the Oracle Database Appliance Bundle Patch 5nstall the Oracle Database Appliance )undle Patch corresponding to the Oracle Database Appliance 5SO image you installed in the "irst step 3:.;.!.!.! or later4. 5t is recommended to install the Oracle Database Appliance )undle Patch even a"ter re/imaging the Oracle Database Appliance #ith an 5SO image' since the Oracle Database Appliance )undle Patch may contain "irm#are patches that are not installed by the 5SO image. Dou can do#nload the Oracle Database Appliance )undle Patch "ollo#ing the lin+s in Oracle Support Note ??????.= and install it according to the instructions in the Oracle Database Application documentation. >. Install any additional, SAP-specific required Oracle Database Appliance Patches Eor example' "or the Oracle Database Appliance version :.;.!.!.! it is re0uired to install OA< Patch :.;.=.!.! "or SAP be"ore continuing #ith the Oracle Database Appliance setup. Dou can do#nload the OA< Patch :.;.=.!.! "or SAP "rom the SAP Service *ar+etplace "ollo#ing the instructions in SAP Note = ?@>@> and install it according to the instructions in section F5nstallation o" the OA< Patch "or SAPF o" this #hite paper. ;. Install and deploy the Oracle Database Appliance nd !ser Bundle 5nstall the Oracle Database Appliance $nd 7ser )undle corresponding to your Oracle Database Appliance version and start the database deployment. Dou can do#nload the Oracle Database Appliance $nd 7ser )undle "ollo#ing the lin+s in Oracle Support Note ??????.=. 5nstall and deploy the end user bundle according to the instructions in section FOracle Database Appliance "or SAP DeploymentF o" this #hite paper. "# !se SAPinst to prepare the Oracle Database Appliance for an SAP database %un SAPinst as described in section F7sing SAPinst on the Oracle Database ApplianceF o" this #hite paper to create SAP/speci"ic OS users' create SAP/ speci"ic directories' and other#ise prepare the Oracle Database Appliance "or an SAP database. $# Install the latest SAP Bundle Patch for the Oracle Database Appliance 5t is re0uired that any database instance has the latest SAP/recommended
Oracle grid and database patches installed. Eor the Oracle Database Appliance' these are delivered in the SAP )undle Patch "or Oracle Database Appliance on the SAP Service *ar+etplace. Dou can do#nload the latest SAP )undle Patch "or the Oracle Database Appliance "ollo#ing the instructions in SAP Note = ?@>@> and install it according to the instructions in section F5nstallation o" the SAP )undle Patch "or ODAF o" this #hite paper. %# &reate or migrate an SAP database instance %un SAPinst as described in section F7sing SAPinst on the Oracle Database ApplianceF to create a ne# SAP database instance. That database instance #ill use the Oracle database so"t#are deployed by the Oracle Database Appliance $nd 7ser )undle above. Alternatively' you can migrate an existing SAP database to the Oracle Database Appliance as described in section F*igration o" SAP DatabasesF o" this #hite paper.
ASM Disk Groups for SAP Databases

The de"ault AS* dis+ groups provided by the Oracle Database Appliance should be used "or all SAP databases. Eor SAP production databases a redundancy level o" high should be used to achieve the highest level o" protection against any type o" storage "ailure. Other SAP databases used "or development' test and GA may use a normal AS* redundancy level. 5n line #ith the standard Oracle Database Appliance setup you should use the AS* dis+ groups HIDATAJ' HI%$DOJ and HI%$(OJ. The DATA dis+ group should contain all data "iles' control "iles' sp"iles' O(% and voting dis+s. The %$(O dis+ group should contain temporary "iles' archive logs' "lashbac+ "iles and bac+ups. The %$DO dis+ group should contain all non/multiplexed redo log "iles. When storing more than one SAP database 3"or instance an SAP $%P database and an SAP )W database or an SAP $%P database #ith an SAP (%* database or multiple SAP $%P databases4 on the Oracle Database Appliance all "iles o" each o" these SAP databases should "ollo# the above recommendation and all be stored in the DATA ' %$DO and %$(O dis+ groups. Eor per"ormance and throughput reasons it is recommended "or each SAP database to only have t#o control "iles in the DATA dis+ group and non/multiplexed online redo log "iles in the %$DO dis+ group. As standard SAP installations use three control "iles in the database it is recommended to remove one control "ile "rom the sp"ile or init.ora. Standard SAP installations also use t#o members "or each online redo log "ile. On the Oracle Database Appliance it is there"ore necessary to remove one member o" each online redo log "ile "or each redo thread. The source database #ill have multiple redo threads i" it #as a %A( database. Three control "iles and multiplexed online redo log "iles are not needed on the Oracle Database Appliance as the control "iles and the online redo log "iles are stored in the DATA and %$DO dis+ groups #hich already provide triple mirroring "or each "ile at the Oracle AS* level due to the redundancy level o" high.
Character Set Requirements for SAP Databases

Ne# installations o" SAP systems "rom SAP NetWeaver .! on only support 7nicode. Eor an SAP 7nicode installation it is re0uired that both the character and the national character set in the database is set to 7TE?. When deploying the Oracle Database Appliance "or an SAP 7nicode system #ith the oa+cli deploy command it is there"ore mandatory to speci"y 7TE? "or the database character set. The national character set is automatically set to 7TE? #hen the database character set 7TE? is chosen. So please ma+e sure that the de"ault database and additional re0uired databases "or SAP systems on the Oracle Database Appliance are al#ays created #ith the SAP re0uired 7TE? database character set.
Non-Unicode SAP Installations

$xisting Non/7nicode SAP installations can be used #ith the Oracle Database Appliance. 5t is important "or these Non/7nicode installations that the character and national character set o" the migrated databases "rom existing systems to the Oracle Database Appliance are +ept the same as in the original system. The character set #ill be W$?D$(. The national character has to be al#ays 7TE?. With the Oracle Database Appliance the national character is automatically set to 7TE? #hen the database character set W$?D$( is chosen. 5t is mandatory that the SAP application o" such a Non/7nicode SAP installation runs on an operating system #hich supports the Non/7nicode runtime re0uirements o" SAP. The Product Availability *atrix 3PA*4 o" SAP 3service.sap.com1pam4 should be chec+ed "or valid operating system support "or Non/7nicode SAP installations. 5n the case o" Non/7nicode installations it is highly recommended to not change the hard#are or operating system "or the SAP application layer. Only the existing database server and storage layer should be changed to the Oracle Database Appliance. 'ote( In the case of 'on-!nicode SAP installations you cannot run the SAP &entral Ser)ices on the Oracle Database Appliance#
Shared File Systems in SAP Environments

5n an SAP environment it is common that all SAP Application Servers have access to a shared "ile system 31sapmnt' 1usr1sap1trans' ...4 #hich store the SAP +ernels' pro"iles' trace "iles and provide the global SAP transport directory. 5n typical SAP installations such a shared "ile system is implemented using a NAS appliance' a cluster "ile system or through an NES exported "ile system "rom the database server. Eor high availability reasons a cluster "ile system is being used or the source o" the NES location is protected by special con"igurations such as .A/NES to not be a single point o" "ailure in an SAP environment. 5" you already have an existing shared "ile system solution in your SAP environment not using an NES exported "ile system "rom the database server it is recommended to continue to use this solution #hen moving to the Oracle Database Appliance. The Oracle Database Appliance o""ers during the deployment phase the con"iguration o" a (loud Eile System. This "ile system is based on OracleKs Advanced (luster Eile System 3A(ES4 and can be used "or 1sapmnt on all application servers' i" it is NES exported "rom the database server.. A"ter the deployment you can add additional "ile systems li+e 1usr1sap1trans'...' using Advanced Storage *anagement (on"iguration Assistance 3asmca4.
Oracle Database Appliance for SAP Deployment

This section describes the deployment o" the Oracle Database Appliance $nd 7ser )undle "or SAP. The deployment installs the Oracle 9rid and %D)*S so"t#are and creates an Oracle 9rid instance and an Oracle database. The deployment can be divided into t#o ma,or parts. The "irst part is the pre/ installation part' #here all necessary customer speci"ic parameters are collected and be stored into a con"iguration "ile. The second part o" the installation uses the in"ormation "rom the con"iguration "ile. The deployment is divided into :@ automated running steps. )e"ore you can start the deployment o" the Oracle Database Appliance end user bundle' ensure that you have the latest Oracle Database Appliance )undle Patch and any additional, SAP-specific required Oracle Database Appliance patches installed. See above section FOracle Database Appliance 5nstallation Overvie#F "or more details. The next pages sho# a step by step deployment. *ogin as user root on the first node &hange to directory +tmp Run the deployment( +opt+oracle+oa,+bin+oa,cli deplo y
10
11
12
13
The Database (lass depends on your need. Please use L.elpM to veri"y the possible database class siCes. Eor a "irst dummy database use Very Small. Eor any SAP production database use at least the Database (lass Narge.
14
5n this example deployment #e use the Oracle (loud EileSystem "or the SAP shared "ile system 1sapmnt.
Do not select button L5nstallM here' but rather save the con"iguration to edit it in the next steps.
15
16
At this point cancel the Oracle Application *anager' edit the con"iguration "ile and change the uid 3D)7S$%NO' (%S7S$%NO4 and gid 3O5NST9%O7PNO' %A(D)A9%O7PNO'...4 according to your 5T needs. %estart the Oracle Application *anager and load the changed con"iguration "ile. 7se next and step to the Summary screen.
$dit the con"iguration "ile... # USER/GROUP INFO STANDARDROLE=1 CRSUSR=oracle CRSUSRNO=502 DBUSR=oracle DBUSRNO=502 OINSTGROUP=o !"#all OINSTGROUPNO=50$ RACDBAGROUP=%&a RACDBAGROUPNO=502 RACOPERGROUP=o'er RACOPERGROUPNO=50( OSAS)GROUP=a"*%&a OSAS)GROUPNO=505 OSAS)OPERGROUP=a"*o'er OSAS)OPERGROUPNO=50+ OSAS)AD)INGROUP=a"*a%* ! OSAS)AD)INGROUPNO=50, ...
%estart 1opt1oracle1oa+1bin1oa+cli deploy
17
7se button LNextM to step to the (on"iguration type' choose SAP Application' and load the con"iguration "ile.
18
Step to the Summary.
Start the deployment using the button L5nstallM.
19
20
SAP Oracle Home Naming Requirements

The correct installation and operation o" any SAP utility such as SAPinst or )%8Tools on the database nodes o" the Oracle Database Appliance re0uires some preparation "or the correct setting o" the O%A(N$O.O*$ environment variable in the SAP environment. The SAP environment re0uires the O%A(N$O.O*$ environment variable to be set to 1oracle1LS5DM1LreleaseM. To create an SAP database' SAPinst searches "or the O%A(N$O.O*$ directory. 5" there is a usable installation #ith the Oracle %D)*S so"t#are correctly installed SAPinst #ill not extract the %D)*S DVD' it #ill use the existing installation. SAPinst loo+s "or the %D)*S so"t#are in 1oracle1LS5DM1LreleaseM the standard path o" SAP "or the Oracle %D)*S so"t#are . The ODA deployment installs the %D)*S so"t#are under 1u!=1app1oracle1product1==.:.!.>1dbhomeO=. There"ore #e need to create a symbolic lin+ on both nodes. login to the nodes and create the directory 1oracle and 1oracle1LS5DM ArootPlsoda!= 1 BQ m+dir 1oracle ArootPlsoda!= 1 BQ cho#n oracle-oinstall 1oracle ArootPlsoda!= 1 BQ su R oracle create the symbolic lin+ AoraclePlsoda!= 1 BQ m+dir /p 1oracle1OS= AoraclePlsoda!= 1 BQ ln /s 1u!=1app1oracle1product1==.:.!.>1dbhomeO= 1oracle1OS=1==: %epeat steps on the second node ArootPlsoda!: 1 BQ m+dir 1oracle ArootPlsoda!: 1 BQ cho#n oracle-oinstall 1oracle ArootPlsoda!: 1 BQ su R oracle create the symbolic lin+ AoraclePlsoda!: 1 BQ m+dir /p 1oracle1OS= AoraclePlsoda!: 1 BQ ln /s 1u!=1app1oracle1product1==.:.!.>1dbhomeO= 1oracle1OS=1==:
21
Using SAPinst on the Oracle Database Appliance

SAP has changed the installation utility SAPinst to #or+ on the Oracle Database Appliance. The next pages sho# the Oracle Database Appliance related steps "rom a perspective o" SAPinst. We start SAPinst #ith the step HDatabase 5nstance PreparationJ to create SAP/speci"ic OS users' create SAP/speci"ic directories' and other#ise prepare the Oracle Database Appliance "or an SAP database. 'ote( Please chec, al-ays for the latest )ersion of SAPinst on the SAP Ser)ice .ar,etplace as the SAPinst )ersion on the distribution media may be outdated#
22
23
24
25
26
27
28
29
30
31
32
33
34
%epeat the step HDatabase 5nstance PreparationJ on the second node.
35
SAPinst: Oracle Database Instance

Dependent on your installation needs' it is re0uired to install the necessary SAP instances 3AS(S' S(S' ...4 "irst' as described in the SAP 5nstallation 9uide. A"ter that you can start the database installation described on the next pages.
36
37
38
39
40
41
42
43
44
)e"ore you choose LNextM veri"y the OS user oracle belongs to OS group sapinst S
45
46
47
48
49
50
51
52
Veri"y the database parameter compatible. 5" compatible is less than the database compatibility o" your AS* dis+ group' change the parameter to the database compatibility o" your AS* dis+ group compatibility.
53
54
55
56
57
Post SAPinst Installation Steps

Setup the environment "or your ne# database on each node' edit the "ile 1etc1oratab and add the lines-
on "irst node lsoda!=OS==-1oracle1OS=1==:-N
on second node lsoda!: OS=:-1oracle1OS=1==:-N
the syntax is- database instance name 3OS== or OS=:4 - oracle home directory 31oracle1OS=1==:4 - startup on boot 3D or N4 the script oraenv sets the environment dependent on the entries o" 1etc1oratab $xampleM. oraenv O%A(N$OS5D T AIAS*=B U OS== The Oracle base has been changed "rom 1u!=1app1grid to 1u!=1app1oracle
As SAPinst runs only on one node' #e do have to copy some "iles "rom the installation node to the secondary node. logon to installation node change to directory LO%A(N$O.O*$M1dbs scp initLO%A(N$OS5D:M .ora to Lnode:M-1LO%A(N$O.O*$M1dbs1initLO%A(N$OS5D:M.ora
58
SAP Database Administration with BR*Tools

The installation and con"iguration o" )%8Tools is done by the above described Database 5nstance step o" SAPinst. There"ore you can use )%8Tools on the Oracle Database Appliance to manage the Oracle database "or SAP. *ore related in"ormation on )%8Tools can be "ound in SAP Notes =@V?@V; and =@V??&?.
59
Lifecycle Management for SAP Databases

An Oracle Database Appliance re0uires regular patching at several levels o" its so"t#are stac+ Oracle %D)*S so"t#are Oracle 9rid 5n"rastructure so"t#are Oracle Appliance <it 3OA<4 so"t#are Operating system and "irm#are This section describes ho# to install patches "or the above components o" an Oracle Database Appliance running databases "or SAP applications. Eor more general in"ormation on the Oracle Database Appliance components and patches' see *y Oracle Support Note ??????.= 3FOracle Database Appliance / :.x Supported Versions W <no#n 5ssuesF4. An Oracle Database Appliance re0uires the "ollo#ing patches and bundle patches "or a complete update 3#ith the mentioned patch versions current at the time o" this #riting4 ODA )undle Patch :.;.!.!.! OA< Patch :.;.=.!.! "or SAP SAP )undle Patch ==.:.!.>.; / :!=:== "or ODA Oracle tests and certi"ies these patches and their successors "or SAP databases on a regular basis. Dou can "ind up/to/date release in"ormation on the patches and their do#nload locations in SAP Note = ?@>@> 3FODA ==.:.!- Patches "or ==.:.!.>F4. 'ote( ach SAP Bundle Patch for the Oracle Database Appliance is certified for only one specific Oracle Database Appliance )ersion# Dou must not combine SAP )undle Patches and Oracle Database Appliance versions that are not certi"ied to operate together. Eor example' SAP )undle Patches ==.:.!.>.; / :!=:==' :!=:=:' and :!=>!= must be installed on ODA version :.;.=.!.! only' and must not be installed on ODA version :.@.!.!.! or later. (hec+ al#ays SAP Note = ?@>@> "or in"ormation on certi"ied combinations o" SAP )undle Patches "or ODA and ODA versions. 5n a nutshell' you install the above patches in the "ollo#ing steps=. %e"er to SAP Note = ?@>@> to determine the re0uired patches and their do#nload locations. :. Do#nload the ODA )undle Patch and install its operating system and "irm#are patches. >. Do#nload and install the OA< Patch "or SAP. ;. Do#nload and install the SAP )undle Patch "or ODA. 'ote( Do not install the /rid Infrastructure patches and the RDB.S patches from the Oracle Database Appliance Bundle Patch#
60
5nstall them in the last step "rom the SAP )undle Patch "or the Oracle Database Appliance instead.
Installation of the Operating System and Firmware Patches

To install the operating system and "irm#are patches' per"orm the "ollo#ing steps=. Do#nload the Oracle Database Appliance )undle Patch to both Oracle Database Appliance nodes :. On both Oracle Database Appliance nodes' veri"y your current Oracle Database Appliance version1opt1oracle1oa+1bin1oa+cli sho# version >. On both Oracle Database Appliance nodes' unpac+ the Oracle Database Appliance )undle Patch1opt1oracle1oa+1bin1oa+cli unpac+ /pac+age LabsoluteOpathOtoOODAObundleOpatchM ;. On the "irst Oracle Database Appliance node' start installation o" the operating system and "irm#are patches o" the Oracle Database Appliance )undle Patch. The oakcli utility installs the patches automatically on both nodes. 1opt1oracle1oa+1bin1oa+cli update /patch LversionOo"OODAObundleOpatchM //in"ra Depending on #hich components o" the Oracle Database Appliance are updated' this command may reboot the nodes. See section FPatching the 5n"rastructure (omponentsF in the %eadme o" the Oracle Database Appliance )undle Patch "or complete in"ormation on the installation o" its operating system and "irm#are patches. 'ote( Do not install the /rid Infrastructure patches and the RDB.S patches from the Oracle Database Appliance Bundle Patch# 5nstall them as described in the next section "rom the SAP )undle Patch "or Oracle Database Appliance instead. 'ote( Installation of the Oracle Database Appliance Bundle Patch and the SAP Bundle Patch for Oracle Database Appliance is not RA&-rolling#
61
Installation of the OAK Patch for SAP

To install the OA< Patch "or SAP' per"orm the "ollo#ing steps=. Do#nload the OA< Patch "or SAP to both Oracle Database Appliance nodes :. On both Oracle Database Appliance nodes' veri"y your current Oracle Database Appliance version1opt1oracle1oa+1bin1oa+cli sho# version >. On both Oracle Database Appliance nodes' unpac+ the OA< Patch "or SAP1opt1oracle1oa+1bin1oa+cli unpac+ /pac+age LabsoluteOpathOtoOOA<OpatchO"orOSAPM ;. On the "irst Oracle Database Appliance node' start installation o" the OA< Patch "or SAP. The oakcli utility installs the patch automatically on both nodes. 1opt1oracle1oa+1bin1oa+cli update /patch LversionOo"OOA<OpatchO"orOSAPM //in"ra See the %eadme o" the OA< Patch "or SAP "or complete installation instructions.
Installation of the SAP Bundle Patch for the Oracle Database Appliance
$nsure that the operating system environment re0uirements are "ul"illed on both Oracle Database Appliance nodes as described in section FOperating System $nvironment %e0uirementsF o" the SAP )undle Patch %eadme. Then "ollo# the instructions "rom section FSAP )undle Patch 5nstallationF to install the SAP )undle Patch "or the Oracle Database Appliance. This usually comprises 5nstallation o" the latest OPatch and *OPatch utilities. 5nstallation o" the 9rid 5n"rastructure patches in the grid homes. 5nstallation o" the %D)*S patches in the %D)*S homes. $xecution o" post/installation instructions' most notably o" the catsbp.sql script. 'ote( Installation of the Oracle Database Appliance Bundle Patch and the SAP Bundle Patch for Oracle Database Appliance is not RA&-rolling#
62
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 o" the "ollo#ing approaches as these have been success"ully tested.
Migration Approach 1: Oracle-to-Oracle (O2O) ACS Service and Customer Self-Service

This #ay o" database migration exists "or many years and is being used to migrate an SAP database bet#een di""erent systems. The method is also described in the SAP Note =@!?: =. O:O allo#s "or homogenous and heterogeneous system copies. A homogenous system copy is a migration #here the source and target operating system is the same. A heterogeneous system copy is a migration #here the source and target system have di""erent operating systems. With an heterogeneous system copy you can "or instance migrate an existing SAP A56 database to an Oracle Database Appliance Ninux database. O:O supports all operating systems SAP products are certi"ied on. The advantage o" this method is' that you can combine the operating system change #ith multiple options to get most out o" the migration As part o" the database migration' the #hole database is reorganiCed. This can "ree up a signi"icant amount o" space #ithin tables and indexes. The tablespace layout can be changed to the ne# SAP standard or to a customer o#n customiCed one. 5t is also possible to move single tables and indexes to separate tablespaces or to merge them into existing or ne# ones. This allo#s you to uni"y the SAP landscape by using a de"ault tablespace name li+e HPSAPS%>J in all SAP systems The SAP schema name can be changed "or instance to HSAPS%>J to uni"y the SAP landscape. The number o" data "iles and mount points can be signi"icantly reduced' by either optimiCing the tablespace layout or the siCe o" the data "iles and "ile systems Tablespaces are created #ith N*TS and ASS* Data "iles #ill be converted "rom "ile systems to Oracle AS* NO) or NON9 data types can be converted to Secure "iles 3==.: only4 Dou can compress the indexes on the target database by using Oracle index compression. The compression calculation is executed as described in SAP Note ==!V ;>. The correct index compression "or each index is determined automatically. Dou can compress tables on the target system. The compression #ill compress all SAP tables as recommended in SAP Note =;>=:V&.
63
With O:O it is possible to combine a plat"orm migration #ith a release upgrade. The migration method supports every combination o" 7nix' Windo#s or Ninux on source and target system. So you can migrate an existing Oracle =!.: database on .P/76 to an Oracle Database Appliance. 5t is possible to upgrade directly to an higher database release. (urrently #ith the O:O method direct database migrations are possible bet#een di""erent Oracle versions. So it is possible to upgrade directly "rom Oracle Vi to Oracle ==g by using O:O. Dou also do not need the most current patchset o" the lo#er Oracle release to run the migration.
The do#ntime needed to migrate a database #ith the O:O method is depending on the database siCe' the included database ob,ects 3SAP cluster tables' partitioned tables4 and the available hard#are resources3(P7' *emory' Storage' Net#or+4. 7p to =T)1hour is possible.
Migration Approach 2: Oracle-to-Oracle (Triple-O) ACS Service only

5" the do#ntime re0uirements cannot be "ul"illed #ith the O:O o""line method' you can use as an alternative the Triple/O method. The Triple/O method allo#s to migrate an Oracle database #ith a do#ntime "or the database copy o" not more than =@ minutes. The do#ntime is independent "rom the database siCe. The do#ntime is needed to stop the SAP system on the source' chec+ the "inal synchroniCation o" the migrated system and to restart SAP on the target system. The Triple/O method is a "urther development o" the O:O method. This method is certi"ied by SAP to per"orm an online migration and documented in SAP Note =@!?: =. So all systems migrated #ith this method are "ully supported by SAP a"ter the migration. The Triple/O method is using the O:O technology to per"orm the initial data load 3copying the current contents o" the source database to the target database4 #hile the SAP application is up and running. Oracle 9olden9ate is used to synchroniCe all changes applied on the source system' #hile the migration is running. The method "ully supports DDN and D*N operations. There are no limitations "or the usage o" the SAP system during the migration. With the Triple/O method you can ma+e use o" all "eatures listed "or the O:O method. Also heterogeneous database migrations and direct database upgrades are supported. When using Triple/O There is no do#ntime needed to start or stop the online migration No need "or special database patches *igration can be started and stopped at any time #ithout ris+ "or the productive system
64
Do#ntime needed "or the database copy part o" the migration is typically only =@ minutes. The do#ntime is independent "rom the database siCe. Triple/O "ully supports DDN and D*N commands Triple/O is SAP release independent
Prere0uisites "or Triple/O At least Oracle version Vi on source >!X "ree (P7 time in average on database server Additional "ile system space o" @!X o" the redo log amount in :;h on the source Additional "ile system space o" @!X o" the redo log amount in ;?h 3or the duration o" the initial data load4 on the target
Nimitations o" Triple/O Oracle 9olden9ate currently does not support compressed tables on the source system. These tables must be either decompressed be"ore the migration' or must be migrated at the end in a do#ntime #indo#s
5mpact on productive system 5ncreased redo log volume' because supplemental logging must be activated on the source
SummaryThese #ell established methods o""er a "ast and reliable approach' not only to migrate a SAP database "rom any SAP supported OS plat"orm "rom Oracle Database Vi %elease : on to the Oracle Database Appliance' but also to implement a couple o" additional "eatures and bene"its into the migration process. This adds more value to the database migration and #ill increase the %O5 "or instance by reducing the storage costs #ith table1index compression.
Migration Approach 3: Oracle RMAN and Transportable Tablespaces

Through the D7PN5(AT$ DATA)AS$ command o" Oracle %*AN it is possible to copy an existing Ninux' Solaris or Windo#s database running on an x?&O&; plat"orm to the Oracle Database Appliance #ithout any do#ntime. )y using Transportable Tablespaces it is possible to copy an existing database "rom any 7N56 plat"orm to the Oracle Database Appliance. )oth #ays are explained in detail in an AS* migration #hite paper "or SAP databases A@B.
65
Documentation References:
A=B Oracle Database Appliance Documentation http-11###.oracle.com1technet#or+1server/storage1engineered/systems1database/ appliance1documentation1index.html
A:B (on"iguration o" SAP NetWeaver "or Oracle 9rid 5n"rastructure ==.:.!.: and Oracle %eal Application (lusters ==g %elease :- A )est Practices 9uide http-11scn.sap.com1community1oracle
A>B SAP Databases on Oracle Automatic Storage *anagement ==g %elease :(on"iguration 9uidelines "or 7nix and Ninux Plat"orms http-11scn.sap.com1community1oracle
A;B %elevant SAP Notes = &! > R SAP So"t#are and Oracle Database Appliance 3ODA4 = ?@>@> R ODA ==.:.!- Patches "or ==.:.!.> =;>= V? R Oracle ==.:.!- Database Parameter Settings =@@!=>> R Oracle Automatic Storage *anagement 3AS*4
A@B *oving your SAP Database to Oracle Automatic Storage *anagement ==g %elease : R A )est Practices 9uide http-11scn.sap.com1community1oracle
66
Using SAP NetWeaver with the Oracle Database Appliance November 2012 Author: Martin Sautter Contributing Authors: Anil Nair, Tammy Bednar, Jens Schmidt, Christoph Kurucz, Jan Klokkers Copyright 2012, 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 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 9 0!5 "#S#A# Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. 1112 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.
67

Using SAP NetWeaver With The Oracle

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Using SAP NetWeaver With The Oracle

Transféré par

Droits d'auteur :

Formats disponibles

An Oracle White Paper November 2012

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Oracle Database Appliance Version

:.;.!.!.! plus :.;.!.!.! OA< Patch :.;.=.!.! "or SAP 384

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Oracle Database Appliance Installation Overview

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

ASM Disk Groups for SAP Databases

Using SAP NetWeaver with the Oracle Database Appliance

Character Set Requirements for SAP Databases

Non-Unicode SAP Installations

Using SAP NetWeaver with the Oracle Database Appliance

Shared File Systems in SAP Environments

Using SAP NetWeaver with the Oracle Database Appliance

Oracle Database Appliance for SAP Deployment

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

%estart 1opt1oracle1oa+1bin1oa+cli deploy

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Step to the Summary.

Start the deployment using the button L5nstallM.

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

SAP Oracle Home Naming Requirements

Using SAP NetWeaver with the Oracle Database Appliance

Using SAPinst on the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

%epeat the step HDatabase 5nstance PreparationJ on the second node.

Using SAP NetWeaver with the Oracle Database Appliance

SAPinst: Oracle Database Instance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance

Using SAP NetWeaver with the Oracle Database Appliance