Fast Start Workshop Technical Consultants

Dirk Biehler, SME Solution Center EMEA Melanie Handreck, MaxDB

OVERVIEW

1 2 3 4
SAP 2008 / Page 2

SAP Business All-in-One Installation Wizard VMware Run SAP Business All-in-One Installation Wizard under VMware NetWeaver Business Client Technical Setup

OVERVIEW

1 2 3 4
SAP 2008 / Page 3

SAP Business All-in-One Installation Wizard VMware Run SAP Business All-in-One Installation Wizard under VMware NetWeaver Business Client Technical Setup

CONTENTS

SAP Business All-in-One Installation Wizard

Details about the SAP Business All-in-One Installation Wizard Used Technology and functions Used Software releases

SAP 2008 / Page 4

SAP Business All-in-One Installation Wizard Unit Objectives 1

After completing this unit, you will be able to
explain what the SAP Business All-in-One Installation wizard is and which technology is used. describe the benefits of the SAP Business All-in-One Installation wizard. differentiate between the different versions of the SAP Business All-in-One Installation wizard. use SAP Business All-in-One Installation wizard for setting up your own System.

SAP 2008 / Page 5

SAP BAiO Installation Wizard High Level Overview

SAP BAiO installation wizard

SAP BAiO installation wizard

Activated Best Practices Solution

Linux and MaxDB as preferred combination for SME Based on SAP EPR 6.0 Full Best Practices scope activated

SAP Best Practices Demo assistant*

SAP ERP 6.0 (test/productive)

Downloadable via service market place Flexible installation on different Platforms (Laptop or Server) through T-shirt sizing Enabled for the usage of Enhanced User Experience (NetWeaver Business Client)

MaxDB

Linux

* New tool that allows for quick and easy personalization of system demos
SAP 2008 / Page 6

What is the SAP BAIO Installation Wizard High Level Overview

SUSE Linux ES 10 (Operating System) Installs all necessary SAP components

YAST - Tool

Installation Master SAP ERP 6.0

SAP Kernel 7.0

Details The Export deliver the content for the SAP ERP System.

MaxDB 7.6

Export DVDs include SAP Best Practices technical add-ons

SAP 2008 / Page 7

Deliverables of the SAP BAIO Installation Wizard

DVD 0 Linux Installation CD incl. Suse Linux Sles 10 SP 1 CD 1 SAP Installation Master incl. all SAP installation CDs Kernel SAP master MaxDB . DVD 2 System Export CD 1 incl. System export of the Best practices solution

1
DVD 3 System Export CD 2 incl. System export of the Best practices solution

Installation is possible native on a empty PC or server as well under VMware.

SAP 2008 / Page 8

SAP Business All-in-One Installation Wizard Benefits 1

The SAP Business All-in-One installation wizard reduces the installation effort by 90% and requires a significantly lower skill level.

Classical installation

Installation wizard for SAP BAiO solutions

No explicit SAP skills e.g. Hardware Technician

Required skill set for the installation Duration of Installation process (core system: ERP, OS, Database) Upgrading system according to the Quick Guide from Best Practices Installation of SAP Best Practices technical add-ons Best Practices content activation

Technical Consultant (Expert)

Average 5 days - 1 day (depending of the hardware)

Average 8 days

30 minutes Average 2 - 5 days Included

SAP 2008 / Page 9

Different Types of the SAP BAIO Installation Wizard

Demo Installation Wizard
Who can get it ? Every Partner can order it via Note

1
Productive Installation wizard
Only available for Hardware Vendors A clean system which needs to be customized by SAP VAR No Limitation

Difference between the two version Usage of the system

Full Best Practices scope installed Only for Demo and evaluation purposes

SAP 2008 / Page 10

Demo Installation Wizard for SAP BAiO Solutions Ordering Process

SAP Business All-in-One installation wizard can be ordered via SAP message. All necessary informations can be found in the SAP note 1161734. SAP medias will be delivered via DVDs. Linux media can be downloaded from Novell Homepage.

SAP 2008 / Page 11

Installation Wizard Steps Overview

1
During the installation with the Installation Wizard, the following steps need to be executed
Installation of Linux SUSE Enterprise Installation of SAP MaxDB and SAP Best Practices During the installation, some customer data need to be entered so that the installation runs successfully. Customer data need to be available before the installation starts (only for productive Version).

SAP 2008 / Page 12

Installation Wizard Customer Data Overview

1
These are the customer data that are to be entered during the installation process. The SAP software partner provides these data.

SAP 2008 / Page 13

Installation Wizard Customer Data Explanation

Further details are available about the customer data.

SAP 2008 / Page 14

Installation Wizard Steps 1-8

SAP 2008 / Page 15

Installation Wizard Steps 9-14

SAP 2008 / Page 16

Summary

1
Description A pre-tested, auto-installable stack that includes Linux, SAP MaxDB, a tested ERP system instance and SAP Best Practices Stack ownership and responsibilities clearly defined between SAP and infrastructure partner. Two different version one for Productive use and one for Demo Usage General Value Statement 6-10 days of less efforts to install complete SAP system. As it is pre-tested customer gets highest quality at lower price. SAP can position and deliver strategic assets as MaxDB or push Novell Linux to lower TCO and reduce royalties to 3rd party DB vendors. Influencer Prospect / Customers Reduced TCO because of very easy to handle SAP installation Always latest up to date SAP installation VAR Channel Partner No effort with time consuming SAP installation Up to date SAP installation SAPs default option for Pre-installation Large Player Ecosystem Partner Easy install of SAP stack incl. OS and DB No special SAP skills required for the installation Tested ERP SW stack SAP Reduced incidents during installation phase Reduced complexity and proved combination of SAP stack Strengthen the cooperation with the Ecosystem of the Large Players

SAP 2008 / Page 17

VMware

1
You should now be able to
explain what the Sap Business All-In-One installation Wizard is. explain the two different types of the SAP Business All-in-one installation wizard. understand the process and steps that are executed with the Installation Wizard. execute the installation with the Installation Wizard. understand how to order your own Demo version.

SAP 2008 / Page 18

OVERVIEW

1 2 3 4
SAP 2008 / Page 19

SAP Business All-in-One Installation Wizard VMware Run SAP Business All-in-One Installation Wizard under VMware NetWeaver Business Client Technical Setup

CONTENTS

VMware
Details about VMware Used Technology and functions Different use cases of VMware

SAP 2008 / Page 20

SAP Business All-in-One Installation Wizard: Unit Objectives 2

After completing this unit, you will be able to
explain what VMware is. describe the benefits and the different use cases of VMware. use VMware together with the SAB Business All-in-One Installation wizard. use VMware for setting up your demo Laptop.

SAP 2008 / Page 21

VMware Benefits

1. Easy to handle, even for non technicians 2. Reliable, reducing your needs for having an appropriate DEMO system 3. Fast, reducing your affords for getting up and usage of your DEMO system 4. Very affordable, free fully functional products available

SAP 2008 / Page 22

SAP on VMware

SAP is going to enable its entire software stack to be supported on virtual machine/server environments. Initially, its software is being tested for use on VMware, and it's planning to enable users to do live migration this way. 451-Group, September 2006

SAP 2008 / Page 23

SAP & VMware Support Status

2
Full support for all production environments
Windows SAP NetWeaver 7.1 (SAP Kernel 7.10) SAP NetWeaver 7.0 (SAP Kernel 7.00) SAP NetWeaver 2004 (SAP Kernel 6.40) Lower SAP versions supportable during an SAP upgrade Linux SAP NetWeaver 7.1 (SAP Kernel 7.10) SAP NetWeaver 7.0 (SAP Kernel 7.00) SAP NetWeaver 2004 (SAP Kernel 6.40) Lower SAP versions supportable during an SAP upgrade 32- / 64-bit SAP Systems 64-bit SAP systems are fully supported 32-bit SAP systems are supportable during an SAP upgrade

SAP 2008 / Page 24

Enterprise Workloads

2
Run the SAP resource intensive enterprise infrastructure including databases and NetWeaver etc. in virtual machines. VMware ESX Server 3.0 / 3.5
SAP NetWeaver SAP BusinessSuite SAP R/3 Enterprise SAP R/3 4.6c, 32-/64-bit 3rd generation of virtualization technology 64bit support ! Up to 4 virtual CPUs per VM / 2 for free server and workstation 16GB RAM per VM with ESX Server 3.0 64GB RAM per VM with ESX Server 3.5 8GB RAM for free server (up to) Support for powerful physical servers with up to 64GB RAM / 32 cores with ESX Server 3.0 256GB RAM / 32 cores with ESX Server 3.5 Support for large memory tables in ESX Server 3.5 and improved I/O

SAP 2008 / Page 25

SAP & VMware Hardware Support Status

2
All SAP certified Hardware is supported
SAP SD Standard Application Benchmark Certificates for Windows Dell on AMD and Intel FSC on AMD and Intel HP on Intel IBM on AMD and Intel Sun on AMD (Linux) HP FSC IBM Sun SAP removed requirement to certify servers specificly with VMware due to stability and performance. Server certificates are no longer necessary.

SAP 2008 / Page 26

SAP Certificates for SAP SD Benchmark on VMware

SAP SD Standard Application Benchmark used for hardware certification Quality of benchmark strongly depends on time and effort spent ~ 1.200 SAPS / core

SAP 2008 / Page 27

VMware Installation

2
VMware installation in short terms
Windows: start setup, follow the assistant Linux: start install script, follow the assistant. Answer all questions with yes or next (stay with the defaults) and your VMware server or workstation will become operational. After finishing the installation wizard reboot to make sure your environment as well services are set appropriate and up and running. Start the VMware Console via the Desktop Icon or path within All Programs.

SAP 2008 / Page 28

VMware Installation

2
Particularities
Only Windows Vista 64 bit: Windows mandatory Kernel Mode and Driver Signing implies that all modules or drivers designed to run at kernel level have to feature digital signatures. This may make your installation fail. In case you use an actual Vista 64 bit, you will have to do a F8 start before installation. While starting Vista 64 press F8 and wait for the advanced boot prompt. You will be asked for several boot options, select Disable Driver Signature Enforcement . Remember to do a F8 start every time you boot Vista 64 in case you use the free VMware products. VMware Workstation features digital signed drivers. There are a lot of hints for avoiding the F8 boot. This is not working for an actual Vista 64 with latest patches. Save your time.

SAP 2008 / Page 29

VMware Installation

2
Select your Setup.exe and make it run. You will be welcomed by the Installation wizard. Always stay with the default selection.

SAP 2008 / Page 30

VMware Installation

2
Dependent on the version and configuration of your Windows you may see a warning. Feel free to ignore it and stay with the default selection OK.

SAP 2008 / Page 31

VMware Installation

2
Go on with the Installation Wizard and stay with the default selection.

SAP 2008 / Page 32

VMware Installation

2
The Installation will be stopped by Windows and a Warning will be generated. The appearance depends on your Version of Windows.

SAP 2008 / Page 33

VMware Installation

2
Change to Install this driver software .

SAP 2008 / Page 34

VMware Installation

2
You will be guided to a screen for applying your serial number:

SAP 2008 / Page 35

VMware Installation

2
Enter your serial and finish your installation.

SAP 2008 / Page 36

VMware Installation

2
You successfully finished. Dependent on the very installation of your OS you will be forced to reboot. Please, if you are not, dont mind, but reboot.

SAP 2008 / Page 37

VMware Preparing Your Virtual Machine

2
Preparing your virtual machine
You did reboot. Start your Virtual Machine Console via the Desktop Icon or the path under programs. You will be welcomed by your login.

SAP 2008 / Page 38

VMware Preparing Your Virtual Machine (Server Installation)

SAP 2008 / Page 39

VMware Preparing Your Virtual Machine (Server Installation)

Preparing your virtual machine
No further information is required, just stay with the default and accept.

SAP 2008 / Page 40

VMware Preparing Your Virtual Machine

2
After successful login your VMware Console starts blanked, but ready for work.

SAP 2008 / Page 41

VMware Preparing Your Virtual Machine

2
Choose New machine. Virtual Machine for starting the Wizard for creating your new virtual

SAP 2008 / Page 42

VMware Preparing Your Virtual Machine

2
And as always you are welcome. Just accept and stay with the default Next.

SAP 2008 / Page 43

VMware Preparing Your Virtual Machine

2
The screens for the free server products and Workstation only differ very little.

SAP 2008 / Page 44

VMware Preparing Your Virtual Machine

2
Stay with the default and accept.

SAP 2008 / Page 45

VMware Preparing Your Virtual Machine

2
You may accept the default naming or choose a name by your own. Just leave the Location as is. The path will depend on your favorite Windows.

SAP 2008 / Page 46

VMware Preparing Your Virtual Machine

2
Change the Network Type to Use host-only networking as it will give as the needed functionality.

SAP 2008 / Page 47

VMware Preparing Your Virtual Machine

2
Change the Disk Capacity to 1 GB and leave the boxes unchecked.

SAP 2008 / Page 48

VMware Preparing Your Virtual Machine

2
You created a definition for your Virtual Machine.

SAP 2008 / Page 49

VMware Preparing Your Virtual Machine

2
Right now you created a definition for your Virtual Machine. You virtual machine mostly equals an empty machine without any software installed, but fully functional. Next we may adjust the settings of your new machine to your needs. In terms of VMware Edit virtual machine settings

SAP 2008 / Page 50

VMware Preparing Your Virtual Machine

2
Under Commands select Edit virtual machine settings.

SAP 2008 / Page 51

VMware Preparing Your Virtual Machine

2
By selecting Edit virtual machine settings you are shown several options, equal to a physical machine. If you now about them feel free to select for your needs. Otherwise, please follow the recommendations.

SAP 2008 / Page 52

VMware Preparing Your Virtual Machine

2
As 384 MB of RAM wont be enough, please select Memory, then adjust memory size to our recommendation on the left side.

SAP 2008 / Page 53

VMware Preparing Your Virtual Machine

2
Next we need more space for the file system of the virtual machine. We may do so easily by adding a new hard disk. Select Add

SAP 2008 / Page 54

VMware Preparing Your Virtual Machine

2
Next we need more space for the file system of the virtual machine. We may do so easily by adding a new hard disk. Select Add

SAP 2008 / Page 55

VMware Preparing Your Virtual Machine

2
Choose Hard Disk, follow the defaults, but adjust the size of your Hard Disk.

SAP 2008 / Page 56

VMware Preparing Your Virtual Machine

2
You finished! Great, isnt it. Your virtual machine equals a machine as recommended for our purposes. We now may go for the installation of the OS and SAP.

SAP 2008 / Page 57

VMware

2
You should now be able to
explain what VMware is. explain the benefits of VMware. create your own VMware environment.

SAP 2008 / Page 58

OVERVIEW

1 2 3 4
SAP 2008 / Page 59

SAP Business All-in-One Installation Wizard VMware Run SAP Business All-in-One Installation Wizard under VMware NetWeaver Business Client Technical Setup

CONTENTS

Run SAP Business All-in-One Installation Wizard under VMware

Setup your own Demo Laptop Combine VMware and SAP Business All-in-One installation Wizard Linux Handling VMware handling for your Demo proposes

SAP 2008 / Page 60

SAP Business All-in-One Installation Wizard Unit Objectives 3

After completing this unit, you will be able to
install a Demo Laptop. use the SAP Business All-in-One installation Wizard under VMware. use SAP within a Linux environment. make use of the Benefits of VMWare for Demo proposes.

SAP 2008 / Page 61

VMware Software Installation

3
As the machine has no initial OS loaded, we will have to help the machine booting. Only once, after the installation went through you will start and stop the machine with one click. For now we should make the machine boot from its CD-Rom. Please start your VMware Console if you havent done so yet.

SAP 2008 / Page 62

VMware Software Installation

3
Select your virtual CD-Rom and choose Edit virtual machine or just doubleclick your selected entry and choose Use ISO Image:

SAP 2008 / Page 63

VMware Software Installation

3
Choose browse and navigate to the location of your ISO files:

SAP 2008 / Page 64

VMware Software Installation

3
Choose browse and navigate to the location of your ISO files:

SAP 2008 / Page 65

VMware Software Installation

You should remember this later, because we will have to change the media of the virtual CD-Rom three more times! Therefore any suggestions?

SAP 2008 / Page 66

VMware Software Installation

3
We are ready to start the installation. Therefore select Power On.

SAP 2008 / Page 67

VMware Software Installation

3
You may do as shown or use the green radio button or select Start the virtual machine under Commands. But please make sure that there is an entry stating your CD-ROM is using an image.

SAP 2008 / Page 68

VMware Software Installation

3
The machine will boot and the initial screen for the installation of the virtual machine will show up.

SAP 2008 / Page 69

How to Work With Linux

3
Logon to Linux
Use the user root with the master password (smesol01). Check IP address Start SAP system Stop SAP System enter ifconfig in the command line su - <sidadm> su - <sidadm> startsap <virtual hostname> stopsap <virtual hostname>

SAP 2008 / Page 70

VMware Handling and Optimization

3
VMware handling
Flexible session creation (please refer to the document BP_Demo_Image_Inst_PartCust_V1.pdf) VMware session started and you want to go out of the session to open the GUI press strg + alt Turn off the session use suspend mode for the session

SAP 2008 / Page 71

VMware Handling and Optimization

3
VMware optimization
VMware After successful installation and startup of the system you should shutdown the whole VMware Instance use sleep mode R/3 Check the instance profile of the system and change the following parameters:
rdisp/wp_no_dia rdisp/wp_no_btc rdisp/wp_no_enq rdisp/wp_no_vb rdisp/wp_no_vb2 rdisp/wp_no_spo abap/buffersize 4 2 1 2 0 1 200000

Check with st02 to get an overview what you should change.

SAP 2008 / Page 72

VMware Handling and Optimization

3
VMware Snapshots are specified points in time to whom you always may go back without the procedure of a point in time recovery. Snapshots may be taken while running the machine! Go to Snapshot. Then Take snapshot.

SAP 2008 / Page 73

VMware Handling and Optimization

3
While taking the snapshot, the machine is slowing down, but functional. You may go back to the taken snapshot by choosing Snapshot, then Revert to Snapshot.

SAP 2008 / Page 74

VMware

3
You should now be able to
explain how to use Sap Business All-in-One installation Wizard under VMware. install a SAP system on a Demo Laptop. start and stop R/3 system under Linux. make the best use of VMware for Demo proposes.

SAP 2008 / Page 75

OVERVIEW

1 2 3 4
SAP 2008 / Page 76

SAP Business All-in-One Installation Wizard VMware Run SAP Business All-in-One Installation Wizard under VMware NetWeaver Business Client Technical Setup

CONTENTS

NetWeaver Business Client Technical Setup

Details about the technical setup of NetWeaver Business Client Used Software releases

SAP 2008 / Page 77

NetWeaver Business Client Technical Setup Unit Objectives 4

After completing this unit, you will be able to
install the NetWeaver Business Client. configure the NetWeaver Business Client. configure the backend System for the usage of NetWeaver Business Client.

SAP 2008 / Page 78

Requirements

4
For legal reasons and sorry for your inconvenience: Please download an additional component for your system. Please go to the Software Distribution Center, you will find it under: https://service.sap.com/swdc then Download then SAP Crypthographic Software or choose Search for all Categories You want the sapcrypto.car.

SAP 2008 / Page 79

Requirements

4
The SAP Cryptographic Library installation package sapcrypto.car contains the following files: The SAP Cryptographic Library (sapcrypto.dll for Windows NT or libsapcrypto.<ext> for UNIX) A corresponding license ticket (ticket) The configuration tool sapgenpse.exe

SAP 2008 / Page 80

Requirements

4
For your convenience, in case you dont already know the SWDC

SAP 2008 / Page 81

Requirements

4
Feel free to alternatively use the Search for all Categories link, search for sapcrypto.

SAP 2008 / Page 82

Installing Sapcrypto

4
After successfully downloading the sapcrypto.lib has to be copied to your virtual machine. This may be easily done by using winscp an explorer like tool for secure network connections between two machines.

SAP 2008 / Page 83

Installing Sapcrypto

4
As winscp doesnt have to be installed, just start it by a double-click. You are welcomed by a login. Please give the IP of your virtual machine to it and login as root.

SAP 2008 / Page 84

Installing Sapcrypto

4
Winscp will probably ask you to save a key. This is only for remembering the connection between the machines. Do so. After successful login you may copy your data to the virtual machine by browsing the windows and cut and paste.

SAP 2008 / Page 85

Installing Sapcrypto

4
Please browse to your DIR_EXECUTABLE within the remote window which is /usr/sap/<SID>/SYS/exe/run. Select your sapgenpse and sapcrypto.so from your local directory and paste. Please browse to your /usr/sap/SID/<instance>/sec in the remote window. Leave your license ticket, credentials with it.

SAP 2008 / Page 86

Installing Sapcrypto

4
After copying the files you will have to do some additional preparations. There should be a environment variable SECUDIR set to the sec subdir /usr/sap/SID/<instance>/sec. In case not, create it as sidadm by typing setenv SECUDIR=/usr/sap/SID/<instance>/sec.

SAP 2008 / Page 87

Adjusting SAP

4
Log on to SAP. Type rz10 for profile maintenance in your transaction window.

SAP 2008 / Page 88

Adjusting SAP

4
Start the profile selection by choosing the box right to Profiles. Select Default and change checkbox to Extended maintenance.

SAP 2008 / Page 89

Adjusting SAP

4
Select change.

SAP 2008 / Page 90

Adjusting SAP

4
Choose New Parameter (iconified Sheet). Fill in appropriate.

SAP 2008 / Page 91

Adjusting SAP

4
Go for the Back Icon. Accept.

SAP 2008 / Page 92

Adjusting SAP

4
Understand the hint and do as recommended after finishing the adjustments.

SAP 2008 / Page 93

Adjusting SAP

4
Repeat for profile parameter login/accept_sso2_ticket. Set the field value to 1. Change to your Instance Profile. Add profile parameter icm/server_port_0. Add the values PROCTIMEOUT=300,TIMEOUT=900 to the standard.

SAP 2008 / Page 94

Adjusting SAP

4
Change to STRUSTSSO2. System PSE, SAP CryptoLib, SSL Server, SSL Client (Standard) must be implemented. The System Personal Security Environment is created during installation. SAP CryptoLib, SSL Server, SSL Client (Standard) must be implemented.

SAP 2008 / Page 95

Adjusting SAP

4
Check status within STRUSTSSo2.

SAP 2008 / Page 96

Adjusting SAP

4
Change to transaction sicf and do F8.

SAP 2008 / Page 97

Adjusting SAP

4
Open the path as shown and right click the appropriate service. Choose Activate service.

SAP 2008 / Page 98

Adjusting SAP

4
Choose Activate service. Do so for: /default_host/sap /public /bc/icons /icons_rtl /pictograms /ur /webdynpro/* /webicons /bsp/sap/htmlb /public/bc /system

SAP 2008 / Page 99

Adjusting SAP

4
Choose Activate service. Do so for:

SAP 2008 / Page 100

Adjusting SAP

4
Choose Activate service. Do so for: /icf_info /logon_groups /urlprefix /icr_groups /icr_urlprefix /icman /myssocntl

SAP 2008 / Page 101

Adjusting SAP

4
Choose Activate service. Do so for: /bc /bsp/kyk/dal_home /sap/public/bc /system /dal/demoa /demob /igs_data /print/* /smart_forms /webdynpro/kyk/* /sap/lord* /powl* /wdk* /wdhc_application

SAP 2008 / Page 102

Adjusting SAP

4
For details apply to Note 1163891.

SAP 2008 / Page 103

Configure Your NetWeaver Business Client

4
Start the NetWeaver Business Client and navigate to System Preferences.

SAP 2008 / Page 104

Configure Your NetWeaver Business Client

4
In the NetWeaver Business Client Configuration screen choose Add.

SAP 2008 / Page 105

Configure Your NetWeaver Business Client

4
Please enter the data for your System:

Name: System Name Type: SAP All-In-One Protocol: HTTP Host: Full qualified hostname Port: Use Transaction SMICM Path: Always the same

SAP 2008 / Page 106

Resources

4
SAP Notes
674851 Virtualization on Windows Virtualization on Windows: Enhanced Monitoring VMware ESX Server configuration guidelines Linux: VMware ESX Server 3 configuration guidelines Linux: Supported Virtualization technologies with SAP SAP support in virtualized Linux environments 1104578 1056052 1122388 1122387 895807

SAP VMware (and other) benchmarks

http://www.sap.com/solutions/benchmark/sd2tier.epx Your DEMO Cookbook

SAP 2008 / Page 107

Thank You!

SAP 2008 / Page 108

Overview SAP MaxDB The SAP database

SAP MaxDB

1977-1997 Start as a research project at the Technical University of Berlin, subsequently owned by Nixdorf Computer AG, Siemens-Nixdorf Informationssysteme AG, Software AG

1993 1997 2003 2007

DBMS for SAP R/3 Acquisition by SAP AG Rebranding to MaxDB Approved name now: SAP MaxDB

15 years of experience in the SAP database scenario

SAP 2008 / SAP MaxDB / Page 110

SAP MaxDB - Development Rationale

Your requirements

Safety, availability, scalability, performance, Ease of use, automatic administration, adaptiveness

Our vision

The invisible database Self-maintenance is best

Our rationale

Essential, substantial Less is more Do things right Simply elegant Fight complexity Elegant simplicity

Your advantage

Lowest cost of ownership High level of comfort Simplicity

SAP 2008 / SAP MaxDB / Page 111

SAP MaxDB is Affordable, Simple and Reliable

Is affordable (lower cost of ownership)

Lower license costs: as much as 50% of other databases Lower maintenance costs: works out of the box and is optimized for SAP solutions

Is simple to use
Easy-to-use tools: for minimal administration Standards-based: provides familiar SQL92, JDBC and ODBC interfaces Completely integrated: DBA Planning Calendar, Alert Monitor Strongly automated: Important administration tasks like e.g.backing up log entries to ensure that the database can be restored at all times, collecting and managing statistics for future analysis

Is reliable
By SAP, for SAP: rigorously tested with and fully integrated into SAP applications Scalable: works invisibly from desktop to very large servers

SAP 2008 / SAP MaxDB / Page 112

SAP MaxDB is Owned, Developed and Supported by SAP

SAP MaxDB is SAP's own database specifically designed to have lower TCO for SAP applications SAP is investing in the development of SAP MaxDB, a strategic and safe alternative for you SAP MaxDB is a robust and reliable technology, optimized to run on all major SAP solutions SAP MaxDB is SAPs preferred choice for SAP Business All-in-One fast-start program

SAP Business Suite

SAP Business All-inOne

SAP Business ByDesign

NetWeaver

SAP MaxDB

ODBC, JDBC, SQL-92

Tools

Application, platform and DBMS integrated and delivered by SAP

SAP MaxDBs performance is comparable to other databases SAP MaxDB is used in over 13,300 commercial installations at approximately 6,000 customer sites world-wide

SAP 2008 / SAP MaxDB / Page 113

Low License Costs

With only 5% of your SAP application value, SAP MaxDB license costs are considerably lower than license costs for other databases.

SAP MaxDB

Oracle

IBM DB/2 LUW

Microsoft SQL Server

License Costs* (Percentage of SAP Application Value)

5%

11%

8%

8%

* according to SAP Master Pricelist Direct Sales

SAP 2008 / SAP MaxDB / Page 114

Save up to 60% With SAP MaxDB

SAP MaxDB is considerably cheaper in comparison to other available databases (5 year cost estimate for databases as part of SAP Business All-in-One).
Overall system costs on a 5 year line with regards to database used
Licenses (ERP price per user (CU), database), m aintenance fee, adm instration cost, backup space

450000 400000 350000 300000 Currency Units 250000 200000 150000 100000 50000 0 1 2 3 Year
SAP 2008 / SAP MaxDB / Page 115

SAP MaxDB DB Option4 DB Option 2 DB Option 3

Customer Example

SAP MaxDB helps you reduce your database-related IT costs by up to 60%.

Affordable: With only 5% of your SAP application value, SAP MaxDB license costs are considerably lower than license costs for other databases. Litef GmbH: Navigation systems, 700 employees Key benefits: Cost savings Ease of use Integrated SAP solution Reduction in IT costs: 40% in 5 years compared to other databases Simple: SAP MaxDB only requires minimal administration and provides easy-to-use administration tools, resulting in low training and DBA staffing costs. Reliable: As SAPs own database product, SAP MaxDB is optimized for SAP solutions and fully integrated into SAPs maintenance and support infrastructure.

Pharmlog: Distribution of pharmaceuticals, 250 employees Key benefits: Cost savings Ease of use Integration with other applications

SAP 2008 / SAP MaxDB / Page 116

SAP MaxDB Customers (OLTP and BI)

SAP 2008 / SAP MaxDB / Page 117

Recent SAP MaxDB Benchmarks

Visit www.sap.com/benchmark

Vendor

Type

Users

Operating System, Database, SAP Version

Configuration

Operating System central server: SuSE Linux Enterprise Server 10

HP

SD

2275
RDBMS: MaxDB 7.7 SAP ECC Release: 6.0

Configuration: Central server: HP ProLiant DL380 G5, 2 processors / 8 cores / 8 threads, QuadCore Intel Xeon Processor X5460, 3.16 GHz, 64 KB L1 cache per core and 6 MB L2 cache per 2 cores, 32 GB main memory

Operating System central server: Solaris 10

SUN

SD

3550
RDBMS: MaxDB 7.6 SAP ECC Release: 6.0 (Unicode)

Configuration: Central server: Sun Blade Model X8440, 4 processors / 16 cores / 16 threads, Quad-Core AMD Opteron processor Model 8356, 2.3 GHz, 128 KB L1 cache and 512 KB L2 cache per core, 2 MB L3 cache per processor, 64 GB main memory

Operating System central server: SuSE Linux Enterprise Server 10

FSC

SD

2300

RDBMS: MaxDB 7.7 SAP ECC Release: 6.0

Configuration: Central server: Fujitsu Siemens Computers PRIMERGY Model TX300 S4 | RX300 S4, 2 processors / 8 cores / 8 threads, Quad-Core Intel Xeon Processor X5460, 3.16 GHz, 64 KB L1 cache per core and 6 MB L2 cache per 2 cores, 32 GB main memory

SAP 2008 / SAP MaxDB / Page 118

SAP MaxDB on Linux since 2000

Customer Installations on Linux/MaxDB 2000-2008/5
1800 1600 1400 1200 1000
3000 4000 6000

MaxDB Customer Installations 2000-2008/05 (all HW/OS platforms)

5000

800 600 400

1000 2000

200 0 2000 2001 2002 2003 2004 2005 2006 2007 2008
0 2000 2001 2002 2003 2004 2005 2006 2007 2008

Linux by Database (May 2008)

liveCache and Content Server installations (KM) not included

Other 0% MaxDB 26%

DB/2 LUW 7% Oracle 67%

SAP 2008 / SAP MaxDB / Page 119

Beside Fast Start, You Have the Choice: Broad Platform Support, Low Hardware Costs
Hardware is an important cost factor, and it comes with vastly different price tags. SAP MaxDB runs on all major operating systems. This means that you are free to choose the platform that suits your business needs best.

Vendor Hewlett Packard IBM

Operating System HP-UX 11.11, 11.23, 11.31 AIX 5.1, 5.2, 5.3, 6.1 SUSE Linux Enterprise Server 9, 10 Red Hat Enterprise Linux 4 Windows 2000, XP Windows Server 2003 Solaris 9, 10

Architectures PA-RISC, IA64 Power

Linux (Novell, Red Hat)

IA32, IA64, X64, Power

Microsoft SUN

IA32, IA64, X64 Sparc, X64

SAP 2008 / SAP MaxDB / Page 120

Simple Anatomy of a SAP MaxDB Instance

Application
SAP MaxDB Instance

SAP MaxDB Kernel

One pool of DB objects

Log Log Volume Volume

Data Volume Data Volume Data Volume Data Volume

SAP 2008 / SAP MaxDB / Page 121

SAP MaxDB Component Portfolio

Operations

Tools

Interfaces

Database Studio
Installation Manager Database Manager
DBMGUI (Windows) DBMCLI

SQL Studio (Windows) Loader Sync Manager WebDAV SQLCLI

SQLDBC ODBC 3.5 JDBC 3.0 Perl Python PHP

DBAnalyzer

SAP MaxDB Kernel

SAP 2008 / SAP MaxDB / Page 122

SAP MaxDB Installation Manager

Few-clicks-only installation
Mobile clients / Laptop Workstations / PC Embedded DBMS

Template-based installation & configuration

Silent mode Template selection Optional demo data

Automatic operation option

Restart, shutdown Backup, recovery Database extension

GUI
Platform-independent

SAP 2008 / SAP MaxDB / Page 123

Database Studio

Database Studio Integrated Tool-Platform for SAP MaxDB Platform independent Plug-ins for Landscape management User Repositories Database management SQL-Queries, Reporting Loader Synchronization Manager DBAnalyzer

SAP 2008 / SAP MaxDB / Page 124

Integration Into the SAP System

Central Monitoring (DB59), Integrating Systems

SAP 2008 / SAP MaxDB / Page 125

Summary

SAP MaxDB is a low-cost enterprise-class DBMS, developed intensively, fit for the job and tuned for SAP applications, and means one-stop-shopping.

Supportability Self-Tuning Adaptiveness

SIMPLE ROBUST FLEXIBLE

Enterprise Class Database Technology from SAP for SAP

SAP 2008 / SAP MaxDB / Page 126

Further Information

Public Web
SAP Community Network (SDN): www.sdn.sap.com Business Process Expert (BPX) Community: www.bpx.sap.com SAP MaxDB @ SDN: http://www.sdn.sap.com/irj/sdn/maxdb Partner Edge Portal: in the SAP Business All-in-One playground

Related SAP Education Training Opportunities

http://www.sap.com/education/ ADM515, Database Administration MaxDB UMEW50, MaxDB Empowering Workshop Administration UMEW60, MaxDB Empowering Workshop Performance Monitoring and Optimization WB550, MaxDB Internals Workshop

SAP 2008 / SAP MaxDB / Page 127

SAP MaxDB @ SAP Community Network Our Information Pool

http://www.sdn.sap.com/irj/sdn/maxdb
SAP 2008 / SAP MaxDB / Page 128

SAP Partner Edge: Channel Partner Portal

SAP MaxDB & Fast Start

SAP 2008 / SAP MaxDB / Page 129

SAP MaxDB
Administration and Monitoring

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will: Know how to use SDBSETUP to
Upgrade the SAP MaxDB software and the database instance

Know how to use SDBUPD to

Upgrade the SAP MaxDB software and the database instance

Installation Tools

Purpose Installation of an SAP system including the SAP MaxDB Software Installation of a standby instance or system copy Updating an existing database instance to a newer Build Upgrading the database instance to a new major release Removing all SAP MaxDB software from your server

Tool

SAPINST SDBSETUP or SDBINST SDBUPD

see upgrade guide

SDBUNINST

Upgrade Prerequisites

Download SAP MaxDB software

Service Marketplace

Extract SAP MaxDB software Administrator/root

maxdb-server-<OS>-<32/64-Bit>-<PA>-<Build>

Database

Complete Backup

C:\>dbmcli db_enum OK MIDB C:\sdb\MIDB\db MYDB2 C:\sdb\MIDB\db MYDB C:\sdb\MIDB\db

C:\>dbmcli db_enum OK MIDB C:\sdb\MIDB\db MYDB2 C:\sdb\MYDB2\db MYDB C:\sdb\MYDB\db

Upgrade Procedure with SDBSETUP

Upgrade Procedure with SDBUPD

To use SDBUPD for a database upgrade, go to the directory maxdb-all-<os>-32|64bit-<arch>-<version>_<build>, into which you unpacked the installation package. Start the SDBUPD program with the following command: UNIX/Linux:

./SDBUPD d <db_name> -u <dbm_user>,<password>

Microsoft Windows:

sdbupd d <db_name> -u <dbm_user>,<password>

SDBUPD performs the upgrade and displays a success message if the upgrade is completed successfully. It then flags the installation as complete.

Installation Log Files

CALL: SDBINST STDOUT: Installation of MaxDB Software STDOUT: *******************************

STDOUT: starting installation Tu, Jun 06, 2006 at 17:43:04 STDOUT: operating system: Windows I386 NT 5.1 Service Pack 2 STDOUT: callers working directory: C:/temp/Install/760029001 STDOUT: installer directory: C:/temp/Install/760029001 Can't open registry key "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech": No such file or directory STDOUT: archive directory: C:/temp/Install/760029001 STDOUT: STDOUT: existing component groups: STDOUT: 0: Server + Client STDOUT: 1: Client STDOUT: 2: Custom STDOUT: 3: none STDOUT: please enter component group id: STDIN: 0 STDOUT: STDOUT: installation of MaxDB Software finished successfully Tu, Jun 06, 2006 at 17:44:43 STDOUT: Rebooting ensures that the MaxDB software can be started from any command line window!

Summary

You should now be able to understand:

How the SAP MaxDB software and the database instance can be upgraded with SDBSETUP How the SAP MaxDB software and the database instance can be upgraded using SDBUPD

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will be able to explain: How to integrate a database into the Database Studio How to add users to connect to the database How to use the administration section How to execute SQL statements

Database Studio Welcome Page

Add a Database

User Management

Create Login

Administration

SQL SQL Editor

Summary

You should now be able to understand:

How a database can be integrated into the Database Studio How users are added to connect to the database How the administration section can be used How SQL statements can be executed

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will know: Which are the three operational states of SAP MaxDB How to start and stop the database with Database Studio

Operational States

There are three possible operational states of SAP MaxDB:

OFFLINE: SAP MaxDB kernel processes and caches do not exist. No user can use the database. ADMIN: The SAP MaxDB kernel is active (processes are started, caches are initialized). Users cannot connect to the database. Only the DBM operator can connect and perform administrative tasks. ONLINE: The SAP MaxDB kernel is active and ready to work. Users can connect to the database.

Startup and Shutdown with Database Studio

Startup and Shutdown with Database Studio

Startup and Shutdown with Database Studio

Startup and Shutdown with Database Studio

Startup and Shutdown with Database Studio

Summary

You should now be able to understand:

The three operational states of SAP MaxDB, And how the database can be started and stopped with Database Studio

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will be able to create: A complete data backup An incremental backup A log backup with Database Studio.

Backup Basics 1/2

Backups are performed by the database process. Online backups of the volumes made with operating system tools (e.g. dd, copy) can not be used. There are three backup types :
Complete Data Backup: All data pages, configuration and parameter information. Incremental Data Backup: Backs up all data pages changed since the last complete data backup. Log Backup: All pages of log (in units of log segments) that have not already been backed up. Additionally Set AutoLog On automatically backs up the log as soon as a log segment is completed.

Backup Basics 2/2

You should keep several generations of backups. For example tapes containing data or log backups should not be directly overwritten with the next backup. The automatic log backup (autosave log mechanism) should always be active.
If automatic log backup is not active, you must regularly check whether there is enough storage space available in the log area. You should regularly archive the version files written during a log backup to a medium of your choice.

Due to the database converter concept, SAP MaxDB does not support backup / restore of single tables/schemas. However, single tables/schemas can be extracted/loaded using the SAP MaxDB loader.

External Backup Tools

SAP MaxDB supports three kinds of external backup tools: Tivoli Storage Manager Networker Tools which support the Interface BackInt for Oracle or Backint for SAP MaxDB

Creating Backups with Database Studio 1/4

Creating Backups with Database Studio 2/4

Creating Backups with Database Studio 3/4

Creating Backups with Database Studio 4/4

Summary
You should now be able to create: A complete data backup An incremental backup A log backup with Database Studio.

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will be able to: Check the database structure Add volumes Alter the log settings Create and use database snapshots with Database Studio.

Checking the Database Structure with Database Studio

Check Backup with Database Studio

Adding Data Space with Database Studio

Alter Log Settings with Database Studio

Snapshot

Freezing a database image

Create Snapshot (ADMIN) Revert to Snapshot (ADMIN) Drop Snapshot (ADMIN) Ideas of use: Very fast point in time resetting (e.g. during upgrades) Restoring training-systems to a defined status

Master Slave Support with Snapshots

Master
Data 01.01.2006

Slave
Complete Complete
Data

: : : :
Data 07.01.2006

Create Snapshot

:
Restore Snapshot
Incremental Incremental
Data 07.01.2006

: : : :
Data 14.01.2006

: : :
Restore Snapshot
Incremental Incremental
Data 14.01.2006

Snapshots: Database after Setup

Taking a Snapshot

If you would like to create a snapshot, the database has to be in ADMIN mode. DBMGUI allows to create the snapshot with menu Backup -> Create Snapshot.

Some Data Has Been Loaded

Checking Data in SQL Studio

Admin Mode: Revert to Snapshot

If you would like to revert to the snapshot, choose menu Recovery Revert to Snapshot. This can be done in ADMIN mode, only.

After Reverting to Initial State

Handling Snapshots in Database Studio

Summary
You should now be able to: Check the database structure Add volumes Alter the log settings Create and use database snapshots with Database Manager GUI, Database Studio and Database Manager CLI.

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will know how to: Detect a database full or log full situation Monitor the data cache hitrate Detect lock collisions Detect and rebuild corrupted indexes with Database Manager GUI and Database Studio

Monitoring the Database Filling Level in DBMGUI

Monitoring the Database Filling Level in Database Studio

Detecting a Full Data Area 1/3

Detecting a Full Data Area 2/3

Detecting a Full Data Area 3/3

Resolving a Database Full Situation

Monitoring the Log Filling Level

Detecting a Full Log Area

Resolving a Log Full Situation

current log write position

Volume 1

last unsaved log entry

(1) Log full (2) Add log volume (3) Log backup (4) Continue log
Volume 1

Logwriter is still waiting

Volume 2

Volume 1 BACKUP

Volume 1

Volume 2

Cache Accesses in DBMGUI

I/O buffer cache accesses I/O buffer cache hit rate should be >= 98%

Catalog Cache accesses Catalog Cache hit rate should be >= 90%

Note: Each Unsuccessful access to the I/O buffer cache (Data Cache) results in a physical I/O. Access to disk is at least 1000 times more expensive than access to cache.

Cache Accesses in Database Studio

Log Queue in DBMGUI

The Log queue may fill up due to

Many log entries written Slow log disks Misconfigured log queue (parameter LOG_IO_QUEUE)

The log queue temporarily stores log entries to be written to log disk. If the log queue is full, all update transactions must wait until log pages are written to disk and space in the log queue is released. A full log queue is counted as Queue overflow

Log Queue in Database Studio

Enable Detailed Time Measurement

C:\WINNT>dbmcli -d MYDB -u dbm,dbm

dbmcli on MYDB>db_cons time enable

OK --dbmcli on MYDB>

Prerequisite that SAP MaxDB collects detailed time values like I/O times is the enabling of detailed time measurement.

Log I/O Time in DBMGUI

Average log I/O time should be well below 20ms

real average: (rel_dev_wr_tm * dev_write_io + avg_self_wr_tm * self_write_io) / (dev_write_io + self_write_io)

rel_dev_wr_tm = write time of I/O performed by the Dev Thread (not including wait times caused by internal tasking) abs_dev_wr_tm = write time of I/O performed by the Dev Thread (including wait times caused by internal tasking) dev_write_io = number of I/O operations performed by the Dev Thread avg_self_wr_tm = write time of I/O performed by the Log Writer task self_write_io = number of I/O operations performed by the Log Writer task

Log I/O Time in Database Studio

Lock Collisions and Lock Escalations

Collisions on SQL locks can significantly reduce the performance of update transactions. The maximum number of locks on table rows can be configured by parameter MAXLOCKS. If the application locks a large number of rows of a table, single row locks will be transferred to a full table lock. This is called lock escalation. Generally, lock escalations should be avoided, as they prohibit concurrent row locks on this table by other applications.

Identify the Locking Process

If a lock situation occurs, the process holding the lock can be identified. Use the SQL statement SELECT * FROM lock_waits to display a list of all lock collisions. For each collision, the lock holder and requestor is displayed. Use H_TERMID to identify the process that holds the lock.

Monitoring Active Task Status

Corrupted Indexes 1/3

Corrupted Indexes 2/3

Corrupted Indexes 3/3

Disabled Indexes in DBMGUI

Disabled Indexes in Database Studio

Summary

You should now be able to understand: How a database full or log full situation can be detected and resolved How to monitor the data cache hitrate How lock collisions can be detected How corrupted indexes can be detected and rebuilt with Database Manager GUI and Database Studio

Agenda

Software updates Introduction to Database Studio Starting and Stopping the Database Creating Backups Further Administration Monitoring and Troubleshooting Creating a Standby Instance

Objectives

Upon completion of this chapter, you will know: Know how to set up a standby database with DBMGUI. This includes Changing parameters Changing the volume configuration Creating backup templates Restoring data, incremental and log backups Interrupting and resuming the log recovery

Standby Database: Installing Database Instance I

Standby Database: Installing Database Instance II

Standby Database: Installing Database Instance III

Standby Database: Installing Database Instance IV

Standby Database: Installing Database Instance V

Standby Database: Restoring the Initial Backup

Standby Database: Restoring an Incremental Backup

Standby Database: Restoring Log Backups I

Standby Database: Restoring Log Backups II

Standby Database: Restoring Log Backups III

Standby Database: Restoring Log Backups IV

Standby Database: ONLINE

Summary

Now you know how to set up a standby database with DBMGUI. You should also be able to: Change database parameters Change the volume configuration Create backup templates Restore data, incremental and log backups Interrupt and resume the log recovery

SAP MaxDB
Integration into the SAP System

Suitable for SAP environments

Agenda

Introduction to Transaction DB59 and DB50 SQL Performance Analysis

SAP AG 2008

Objectives

Upon completion of this chapter, you will be able to: Integrate your SAP MaxDB databases into your monitoring landscape in transaction DB59 Use transaction DB50 to monitor your SAP MaxDB database Schedule backups and other administrative tasks using the DBA Planning Calendar Use the Alert Monitor for your SAP MaxDB instances

SAP AG 2008

Which Instances Can Be Monitored?

OLTP System SCM System KW System

Application Server

Application Server

Application Server

KPRO Database OLTP Database SCM Database Cache Server

Content Server

SAP AG 2008

Central Monitoring

Application Server

Database

OLTP System
Application layer

SCM System

KW System

SAP MaxDB OLTP Database

SAP MaxDB SCM Database

SAP MaxDB KPRO Database

Content Server

Cache Server

SAP AG 2008

Central Monitoring Transaction DB59

To be able to monitor other SAP MaxDB instances within this system, you have to integrate the corresponding database instance - i.e. you have to enter the user information to connect to this database instance.

SAP AG 2008

Database Integration
To be able to connect to the database instance you have to enter: The name of the database instance. The hostname or IP address of the server on which the database instance runs. The DBM operator and his password. This is the user used to connect to the Database Manager GUI or CLI. Default: control with password control. The Standard Database User, which for SAP applications is SAPR3 or SAP<SID> as the default. Make sure that the checkbox for the central authorization is marked, that the connect information is stored in tables DBCON and DBCONUSR of the monitoring system.
SAP AG 2008

Connection Test

SAP AG 2008

Connection Test

SAP AG 2008

X-Server not Running

SAP AG 2008

Wrong Standard Database User Password

SAP AG 2008

Remote Monitoring
Transaction DB59: Central entry point to monitor SAP MaxDB & liveCache instances

SAP MaxDB Monitoring DB50

Monitoring of remote instances is possible. Even stand-alone databases like small test databases can be monitored in the SAP system.
SAP AG 2008

liveCache Monitoring LC10

Transaction DB50 Properties

Further improvement of transaction DB50 is done continuously. The tree structure in the version your are using might differ slightly from the shown screenshots.
SAP AG 2008

SAP MaxDB and liveCache Directory Structure

Database Software and Configuration Data

/sapdb data wrk config <db_name> bin pgm env etc lib incl misc sap Temporary data programs pgm bin db <db_name>

SAP AG 2008

SAP MaxDB Status and Log Files

SAP AG 2008

Volume Configuration

SAP AG 2008

Task Manager

SAP AG 2008

Memory Areas: Caches

SAP AG 2008

Memory Areas: Data Area

SAP AG 2008

Memory Areas: Log Area

SAP AG 2008

Database Messages

SAP AG 2008

Database Error Messages

SAP AG 2008

Database Terminations

SAP AG 2008

DBA History: Backup/Restore (DBMServer)

SAP AG 2008

DBA History: Backup/Restore Log File

SAP AG 2008

DBA History: Backup/Restore (Kernel)

SAP AG 2008

Parameter Settings

SAP AG 2008

Backup Media

SAP AG 2008

Database Manager (CLI)

SAP AG 2008

DBA Planning Calendar

SAP AG 2008

Scheduling Tasks

SAP AG 2008

DBA Planning Calendar

SAP AG 2008

Alert Monitor RZ20

SAP AG 2008

Creating a Complete Backup

SAP AG 2008

Data Collector

SAP AG 2008

Manual Start of Data Collection for Alert Monitor

SAP AG 2008

Start Data Collection Method

SAP AG 2008

Summary

Transactions DB59 and DB50 help you to monitor and administer all SAP MaxDB databases in your system landscape.
Transaction DB59 is the central entry point where the databases can be integrated into the monitoring system. Using this transaction you can easily switch to the Database Assistant for each of your databases. Transaction DB50 is the Database Assistant which allows to monitor your SAP MaxDB database. The DBA Planning Calendar enables you to schedule important database tasks like backups or consistency checks. In transaction RZ20 a special branch for the SAP MaxDB instances can be created, so that critical situations are reported using the SAP Alert concept.

SAP AG 2008

Agenda

Introduction to Transaction DB59 and DB50 SQL Performance Analysis

SAP AG 2008

Objectives

Upon completion of this chapter, you will be able to: Use the SAP MaxDB performance analysis tools Database Analyzer Command Monitor and Resource Monitor to determine performance bottlenecks.

SAP AG 2008

Starting the Database Analyzer

SAP AG 2008

Database Analyzer Status

SAP AG 2008

Database Analyzer Output

SAP AG 2008

Starting the Command Monitor

You should adapt the default thresholds to your needs. If you are looking for long running SQL statements, it might be good to start only with a threshold for the runtime and to leave the other input fields empty.

SAP AG 2008

Command Monitor Output

SAP AG 2008

Execution Plan

SAP AG 2008

Resource Monitor

SAP AG 2008

Starting the Resource Monitor

SAP AG 2008

Resource Monitor Output

SAP AG 2008

Tables/Views
To determine the best optimizer strategy for an SQL statement you have to analyze all tables involved. You have to check The table definition (especially the primary key definition) The existing indexes and The optimizer statistics. To decrease the runtime of a statement it might be necessary to update the optimizer statistics or to create a new index.
SAP AG 2008

Tables/Views: Properties

For large tables the sample value for optimizer statistics should be set to 10% for smaller tables a sample value of 20000 rows is sufficient (note #808060).
SAP AG 2008

Tables/Views: Definition

SAP AG 2008

Tables/Views: Indexes

SAP AG 2008

Tables/Views: Restore Index

SAP AG 2008

Showing the Execution Plan

SAP AG 2008

Tables/Views: Optimizer Statistics

SAP AG 2008

Summary

Transaction DB50 helps you to monitor and administer all SAP MaxDB database instances in your system landscape. Performance problems can be analyzed and solved using the Database Analyzer, Command Monitor and Resource Monitor in this transaction.

SAP AG 2008

Copyright 2008 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. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.

SAP AG 2008

Copyright 2008 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. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.
SAP 2008 / Page 283