Copyright 2013, Oracle and/or its affiliates. All rights reserved. DOAG 2013

Transcription

1 1

2 Cloning of Oracle Homes on Oracle 11.2 Cluster Nodes after Linux Upgrade Andreas Becker, Principal Member Technical Staff Oracle Server Technologies, SAP Dev.

3 Program Agenda The Project The Plan The Big Picture DelNode/AddNode vs. Oracle Home Cloning Summary 5

4 The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle. 7

5 The Project 9

6 Project Description Current Situation and Project Target SAP System on Oracle Oracle Cluster with 4 nodes Oracle Release Oracle Linux Release 6.1 on SAP Application Server Oracle Linux Release 5.8 on Oracle nodes ASM + ACFS Target: Oracle Linux Release 6.1 on all Oracle nodes 10

7 Project Description SAP System + Oracle System Overview SAP User SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP Instances S1 S2 S3 Instance Instance Instance S4 Instance Node #1 OL5.8 ASCS ERS Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Instances ASM / ACFS Nodes SAP Oracle Services OL5.8 Database Database 11

8 Linux OS Upgrade Oracle Linux In-place upgrading from a major version of Oracle Linux 5 or earlier is not supported. Although Anaconda provides an option to perform an upgrade, fresh installation is strongly recommended. Oracle Linux Release Notes for Release _sup_64rn.html 12

9 Linux OS Upgrade Red Hat Linux Red Hat does not support in-place upgrades between any major versions of Red Hat Enterprise Linux. Red Hat Enterprise Linux 6 Installation Guide US/Red_Hat_Enterprise_Linux/6/html/Installation_Guid e/ch-upgrade-x86.html 13

10 Project Description Restrictions and Requirements Technical restrictions Linux upgrade requires fresh installation of all nodes SAP System HA requirements SAP application must remain available, no longer downtimes Downtimes due to SAP application server restarts are acceptable 2 of the 4 nodes are sufficient run the SAP system 14

11 Project Description Restrictions and Requirements Project goal: Linux OS Upgrade No other requirements or changes No hardware replacement No host name change No network configuration change, no IP change 15

12 The Plan 18

13 The Plan 2-Phase-Approach 2 nodes are sufficient to run the SAP load (for a while) 2-phases Phase 1: OS upgrade of nodes 1 and 2 Phase 2: OS upgrade of nodes 3 and 4 19

14 The Plan 2-Phase-Approach Between Phase 1 and Phase 2 the system would run with different OS versions (for a while) MOS For Oracle Database 11g Release 2, Oracle Clusterware and ASM binaries are combined into a single OLE_HOME called the grid infrastructure home. This home fully supports rolling upgrades for patches, bundles, patchsets and releases. (If you are upgrading ASM from Oracle Database 10g to 11g Release 2, you will not be able to upgrade ASM in a rolling fashion.) The Oracle Clusterware and Oracle Real Application Clusters both support rolling upgrades of the OS software when the version of the Oracle Database is certified on both releases of the OS (and the OS is the same, no Linux and Windows or AIX and Solaris, or 32 and 64 bit etc.). This can apply a patch to the operating system, a patchset (such as EL4u4 to EL4u6) or a release (EL4 to EL5). 20

15 The Plan -Rolling Grid Home Patching Oracle Database SAP Bundle Patch for Grid Infrastructure If you restrict installation of GI-PSU and this SBP to the grid homes and the non-sap homes as described above, you can also keep the SAP databases on the cluster and the SAP applications running on these available. However, due to limitations in Oracle's connection handling such a -rolling grid home SBP installation is not transparent to the SAP applications connected against the databases of the cluster. To avoid transaction or other errors in the SAP applications when installing this SBP in a rolling manner, follow the additional instructions in section 2.4, "Maintaining SAP Applications during a -Rolling Patch Installation". To avoid transaction or other errors in the SAP applications when installing GI-PSU and the Grid Infrastructure patches of this SBP in a rolling manner, you must follow the installation instructions below on each of the cluster nodes in turn: All connections from SAP applications to SAP database instances running on the cluster node must be terminated by the SAP application before installing GI-PSU and the Grid Infrastructure patches of this SBP on the cluster node. Any SAP application component (for example, the Enqueue Server) which is dependent on the Oracle Clusterware on a cluster node must be stopped by the SAP application before installing GI-PSU and the Grid Infrastructure patches of this SBP on the cluster node. 22

16 The Plan -Rolling Grid Home Patching To avoid transaction or other errors in the SAP applications 1. All connections from SAP applications to SAP database instances running on the cluster node must be terminated by the SAP application. 2. Any SAP application component (for example, the Enqueue Server) which is dependent on the Oracle Clusterware on a cluster node must be stopped by the SAP application 23

17 The Big Picture 25

18 The Big Picture Target SAP User SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS SAP Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 26

19 The Big Picture Starting Point SAP User SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 28

20 The Big Picture Preparations SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 1. Block SAP instances 1 and 2 for logon and disable batch jobs 2. Inform SAP user to reconnect 3. Inform SAP user about SAP instance restart 4. Relocate database services 5. Restart SAP instance(s) 1 and 2 6. Allow logon on SAP instances 1 and 2 and enable batch jobs again SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 29

21 The Big Picture Preparations SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 1. Block SAP instances 1 and 2 for logon and disable batch jobs 2. Inform SAP user to reconnect 3. Inform SAP user about SAP instance restart 4. Relocate database services 5. Restart SAP instance(s) 1 and 2 6. Allow logon on SAP instances 1 and 2 and enable batch jobs again SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 30

22 The Big Picture Preparations SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 1. Block SAP instances 1 and 2 for logon and disable batch jobs 2. Inform SAP user to reconnect 3. Inform SAP user about SAP instance restart 4. Relocate database services 5. Restart SAP instance(s) 1 and 2 6. Allow logon on SAP instances 1 and 2 and enable batch jobs again S1 $ srvctl relocate service $ srvctl relocate service S1 S2 S2 S3 Instance Instance Instance S4 Instance ASCS ERS SAP Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 31

23 The Big Picture Preparations SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 S1 S2 S3 S4 S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS 1. Block SAP instances 1 and 2 for logon and disable batch jobs 2. Inform SAP user to reconnect 3. Inform SAP user about SAP instance restart 4. Relocate database services 5. Restart SAP instance(s) 1 and 2 6. Allow logon on SAP instances 1 and 2 and enable batch jobs again SAP Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 32

24 The Big Picture Preparations SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 1. Block SAP instances 1 and 2 for logon and disable batch jobs 2. Inform SAP user to reconnect 3. Inform SAP user about SAP instance restart 4. Relocate database services 5. Restart SAP instance(s) 1 and 2 6. Allow logon on SAP instances 1 and 2 and enable batch jobs again SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 33

25 The Big Picture Preparations 1. Relocate SAP ERS instance (sapctl) 2. Relocate SAP ASCS instance (sapctl) SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 34

26 The Big Picture Preparations 1. Relocate SAP ERS instance (sapctl) 2. Relocate SAP ASCS instance (sapctl) SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 35

27 The Big Picture Preparations 1. Relocate SAP ERS instance (sapctl) 2. Relocate SAP ASCS instance (sapctl) SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 36

28 The Big Picture Preparations SAP preparations are completed. SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 37

29 The Big Picture Preparations 1. Stop instances on nodes 1 and 2 $ srvctl stop instance i <instance> -d <db> 2. Stop CRS on nodes 1 and 2 (root) # crsctl stop crs SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 38

30 The Big Picture Preparations completed Preparations for phase 1 complete. SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes OCR Voting Database 39

31 Program Agenda The Project The Plan The Big Picture DelNode/AddNode vs. Oracle Home Cloning Summary 40

32 The Oracle Home Cloning Approach 42

33 The Alternatives Oracle home Cloning Approach 1. Backup Grid home, database home(s), oratab, host configuration files, user home directories, user configuration, /etc/hosts, /etc/passwd, 2. Stop database instances and CRS 3. Install the new Linux version and configure the node exactly as before hostname, IP, accounts, user homes, ). 4. Ensure that installation prerequisites are met 5. Restore backup of Grid home and database home(s) 6. Clone Grid home and database home(s) 7. Start CRS and database instances 43

34 The Big Picture Preparations completed Preparations for phase 1 complete. SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1 Node 2 Node 3 Node 4 OCR Voting Database 47

35 The Alternatives Oracle home Cloning Approach 1. Backup Grid home and database home on each node. 2. Backup /etc/orainst.loc, /etc/oratab 3. Backup OS configuration files like /etc/hosts, /etc/groups, /etc/passwd 4. ASM: mapping of ASM disks SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP gi_home_node1.tar db_home_node1.tar gi_home_node2.tar db_home_node2.tar S3 S1 Instance S4 S2 Instance Oracle Services $ tar cvf $ tar cvf ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1 Node 2 Node 3 Node 4 OCR Voting Database 48

36 The Alternatives Oracle home Cloning Approach 1. Install new OS version SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP Install Linux OS S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #1 OL5.8 OL5.8 Node #2 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1 Node 2 Node 3 Node 4 OCR Voting Database 49

37 The Alternatives Oracle home Cloning Approach 1. Restore & Clone Grid Home 2. Restore & Clone Database Home SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP gi_home_node1.tar db_home_node1.tar gi_home_node2.tar db_home_node2.tar S3 S1 Instance S4 S2 Instance Oracle Services $ tar xvf $ clone.pl $ tar xvf $ clone.pl ASCS ERS Node #1 OL5.8 OL5.8 Node #2 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1 Node 2 Node 3 Node 4 OCR Voting Database 50

38 The Alternatives Oracle Home Cloning Approach Cloning the Grid home $ su root -c "$OHGRID/crs/install/rootcrs.pl -unlock $ /usr/bin/perl $OHGRID/clone/bin/clone.pl OLE_BASE=$OLE_BASE OLE_HOME=$OHGRID -defaulthomename INVENTORY_LOCATION=/oracle/oraInventory -O'"CLUSTER_NODES={<node list>}"' -O'"LOCAL_NODE=<node>"' CRS=false - O"SHOW_ROOTSH_CONFIRMATION=false su root -c "$OHGRID/rdbms/install/rootadd_rdbms.sh" su root -c "$OHGRID/crs/install/rootcrs.pl -patch" su root -c "chmod 755 /opt/oracle Cloning the Database home $ $OLE_HOME/clone/bin/clone.pl OLE_HOME=$OLE_HOME OLE_BASE=$OLE_BASE -defaulthomename $ $OLE_HOME/oui/bin/runInstaller -updatenodelist OLE_HOME=$OLE_HOME "CLUSTER_NODES={<comma separated list of cluster nodes>}" # $OLE_HOME/root.sh For details, see My Oracle Support note MOS

39 The Alternatives Oracle home Cloning Approach 1. Start CRS on new nodes 2. Start instances on new nodes Next: Rebalance SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP Instance Instance S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1 Node 2 Node 3 Node 4 OCR Voting Database 52

40 The Alternatives Oracle home Cloning Approach 1. Rebalance to complete phase 1 Phase 1 complete Next steps: 1. Start phase 2 2. Rebalance to complete phase 2 SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 Instance S2 Instance S3 Instance S4 Instance Oracle Services ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Zero OCR updates Node 1 Node 2 Node 3 Node 4 OCR Voting Database 53

41 The Alternatives Oracle home Cloning Approach Phase 1 completed. Phase 2 completed. Oracle is running OL 6.1. SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 Instance S2 Instance S3 Instance S4 Instance Oracle Services ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Zero OCR updates Node 1 Node 2 Node 3 Node 4 OCR Voting Database 54

42 The DelNode/AddNode Approach 55

43 The Alternatives DelNode/AddNode Approach 1. Remove a node from the cluster 2. Install the new Linux version 3. Add the node to the cluster again. Repeat steps 1-3 for all nodes that need to be installed. When finished, backup OCR. DelNode: <GRIDHOME>/bin/crsctl delete node -n <nodename> AddNode: <GRIDHOME>/oui/bin/addNode.sh 56

44 The Alternatives DelNode/AddNode Approach 1. Remove nodes 2. Install new OS version 3. Add nodes SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #1 OL5.8 Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1 Node 2 Node 3 Node 4 OCR Voting Database 57

45 The Alternatives DelNode/AddNode Approach 1. Remove nodes 2. Install new OS version 3. Add nodes SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP $ crsctl delete node node 1 S3 S1 Instance ASCS S4 S2 Instance ERS Oracle Services Node #2 OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 2 Node 3 Node 4 OCR Voting Database Node #1 OL5.8 58

46 The Alternatives DelNode/AddNode Approach 1. Remove nodes 2. Install new OS version 3. Add nodes SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S3 S1 Instance S4 S2 Instance Oracle Services $ crsctl delete node node 2 ASCS ERS Node #3 OL5.8 Node #4 OL5.8 Nodes 2 OCR updates Node 3 Node 4 OCR Voting Database Node #1 Node #2 OL5.8 OL5.8 59

47 The Alternatives DelNode/AddNode Approach 1. Remove nodes 2. Install new OS version 3. Add nodes SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #3 OL5.8 Node #4 OL5.8 Nodes 2 OCR updates Node 3 Node 4 OCR Voting Database Node #1n Node #2n OL5.8 OL5.8 60

48 The Alternatives DelNode/AddNode Approach 1. Remove nodes from cluster 2. Install new OS version 3. Add nodes to cluster again SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP $ addnode.sh S3 S1 Instance ASCS S4 S2 Instance ERS Oracle Services Node #1n OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes 3 OCR updates Node 1n Node 3 Node 4 OCR Voting Database Node #2n OL5.8 61

49 The Alternatives DelNode/AddNode Approach 1. Remove nodes from cluster 2. Install new OS version 3. Add nodes to cluster again SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP $ addnode.sh S3 S1 Instance ASCS S4 S2 Instance ERS Oracle Services Node #1n OL5.8 Node #2n OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes 4 OCR updates Node 1n Node 2n Node 3 Node 4 OCR Voting Database 62

50 The Alternatives DelNode/AddNode Approach 1. Start CRS on new nodes 2. Start instances on new nodes SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP Instance Instance S3 S1 Instance S4 S2 Instance Oracle Services ASCS ERS Node #1n OL5.8 Node #2n OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1n Node 2n Node 3 Node 4 OCR Voting Database 63

51 The Alternatives DelNode/AddNode Approach 1. Rebalance again: move SAP users, SAP Database Services, and SAP instances back to instances on nodes 1 and 2 SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 Instance S2 Instance S3 Instance S4 Instance Oracle Services ASCS ERS Node #1n OL5.8 Node #2n OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes Node 1n Node 2n Node 3 Node 4 OCR Voting Database 64

52 The Alternatives DelNode/AddNode Approach Phase 1 completed. Phase 2: next to start Oracle is running OL 6.1 and OL 5.8 (mix). SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 Instance S2 Instance S3 Instance S4 Instance Oracle Services ASCS ERS Node #1n OL5.8 Node #2n OL5.8 Node #3 OL5.8 Node #4 OL5.8 Nodes 4 OCR updates Node 1n Node 2n Node 3 Node 4 OCR Voting Database 65

53 The Alternatives DelNode/AddNode Approach Phase 1 completed. Phase 2 completed. Oracle is running OL 6.1. SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance 4 SAP S1 S2 S3 Instance Instance Instance S4 Instance ASCS ERS Oracle Services Node #1n OL5.8 Node #2n OL5.8 Node #3n OL5.8 Node #4n OL5.8 Nodes 8 OCR updates Node 1n Node 2n Node 3n Node 4n OCR Voting Database 66

54 Program Agenda The Project The Plan The Big Picture DelNode/AddNode vs. Oracle Home Cloning Summary 67

55 Summary 68

56 Summary Comparison DelNode/AddNode vs. Oracle Home Cloning Approach DelNode/AddNode Nodes are removed from cluster and added to cluster Every node add / node remove operation changes the OCR and affects the remaining cluster N-node- 2xN OCR configuration changes OCR configuration before/after is not identical OCR backup required when finished Oracle Home Cloning Zero Addnode/DelNode operations OCR/Cluster configuration remains unchanged 71

57 Summary Comparison DelNode/AddNode vs. Cloning Approach DelNode/AddNode Oracle Home Cloning General approach More specific approach Suitable for Cluster extensions Cluster configuration changes (host names, hardware, IP address) Preparation of new nodes while system is online Hardware exchange Suitable for OS upgrade / OS fresh installations Rolling GI Home Patching 72

58 References SAP Notes Patching of Oracle Homes with Minimal Downtime Rolling Patching Oracle Database SAP Bundle Patch for Grid Infrastructure README 75

59 References MOS Notes Oracle Support Document (Minimal downtime patching via cloning 11gR2 OLE_HOME directories) can be found at: Oracle Support Document (How to remove/delete a node from Grid Infrastructure Clusterware when the node has failed) can be found at: Oracle Support Document (How to Add Node/Instance or Remove Node/Instance in 10gR2, 11gR1 and 11gR2 Oracle Clusterware and ) can be found at: Oracle Support Document (: Frequently Asked Questions) can be found at: 76

60 References Other Red Hat Enterprise Linux 6 Product Documentation US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-upgrade-x86.html Oracle Linux Release Notes for Release 6.4 Supported Upgrade Path 77

61 Questions? 78

62 80

63 81

64 201 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, F, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. 201 SAP AG. All rights reserved.