The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into

Transcription

1

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

3 11gR2 Best Practice for SAP Stefan Menschel Senior Leitender Systemberater BU Server Technology Germany

4 DATABASE 11!R2

5

6 SAP Note (11.2 Integration in SAP) SAP Note (11.2 SecureFiles) SAP Note (Corrections BRTOOLS720) SAP Note (LOB Umsetzung und Tab Komp mit BRSPACE720) SAP Note (Oracle 11.2 Upgrade Scripts) SAP Note (Oracle 11.2 Troubleshooting SoftwareInstall) SAP Note (Oracle 11.2 Database Parameter) SAP Note (MOPatch) SAP Note (Oracle 11.2 Troubleshooting DBUpgrade) SAP Note (Oracle 11.2 Current Patch Set) SAP Note (11.2 Integration in SAP) SAP Note (Oracle 11.2 Instant Client) SAP Note (Oracle 11.2 Patches Patchcollections) SAP Note (BRTools support for Oracle 11.2) SAP Note (Oracle 11.2 Central Technical Note)

7

8 Sind Sie sich sicher, dass unser SAP mit der 11.2 genauso performant und stabil ist?

9 Oracle Real Application Testing can help to get clarity

10 Operations and Infrastructure Top Concerns Managing change effectively is a strategic imperative!

11 Real Application Testing Why? Businesses want to adopt new technology Extensive testing and validation is expensive Despite extensive testing success rate low Many issues go undetected System availability and performance are negatively impacted Cause of low success rate Current tools provide inadequate testing Simulate unrealistic synthetic workload Provide partial workflow coverage Real-Application Testing makes real-world testing possible

12 Real Application Testing Overview Feature Capture From Test Changes In SQL Performance Analyzer 9i R2 10g R2 10g R2 or 11g 10g R2 or 11g Database Replay 9i R2 10g R2 11g 11g SAP Note :

13 Testing Today Production 1,000s of Real Online Users PRODUCTION

14 Testing Today Test 1-2 testers trying to be 1,000s of users Batch PRODUCTION TEST

15 Database Replay Workload for 1,000s of online users captured PRODUCTION Capture Workload

16 Database Replay Test your system changes at production levels Replay Capture Workload PRODUCTION TEST

17 Database Replay Test your system changes at production levels Replay Capture Workload PRODUCTION TEST

18 Real Application Testing Summary Database Replay Replay production workload in test environment Identify, analyze and fix potential instabilities before making changes to production Capture Workload in Production Capture full production workload with real load, timing & concurrency characteristics Move the captured workload to test system Replay Workload in Test Make the desired changes in test system Replay workload with full production characteristics Honor commit ordering Analyze & Report Errors Data divergence Analysis & Reporting Performance divergence

19 Clients Database Replay for SAP Workflow Production ( ) Test ( 11.2) Replay Clients * Mid-Tier DB-Instance Storage Capture Process Replay Analysis & Reporting * no middle/client tier setup required

20 Database Replay Step1 :Workload Capture Client Client Client Minimal overhead Platform and protocol independent Workload filters Backup Capture interesting workload OS Directory File 1 Server 1 Server 2 Server N Capture Infrastructure File 2 Background Production System File N

21 Workload Capture Options Workload can be filtered to customize what is captured Inclusion Filters: Specifies which sessions should be captured Exclusion Filters: Specifies which sessions should NOT be captured Filter Attributes: Any of the following session attributes can be used for filtering User Program Module Action Service Session ID Workload capture can be run ondemand or scheduled to run at later time

22 Workload Capture Overhead Performance overhead Workload dependent Proportional to the data sent from the client TPC-C throughput degradation about 4.5% Workload capture size TPC-C 20min 100 users 10 warehouses: 1.2G Enable capture for few minutes to assess size DSS OLTP LOW Overhead HIGH Long Running SQL Short SQL/DML Insert Intensive Large LOBs

23 Database Replay Step 2: Process Workload Files Setup test system Application data should be same as production system as of capture start time Use RMAN, Snapshot Standby, imp/exp, Data Pump, etc. to create test system Make change: upgrade db and/or OS, change storage, migrate platforms, etc. Processing transforms captured data into replayable format Once processed, workload can be replayed many times For RAC copy all capture files to single location for processing File 1 File 2 File n Capture Files Test System File 1 File 2 File n Metadata Replay Files

24 Database Replay Step3: Replay Workload Replay captured workload Replayed operations see the same data and perform the same work Preserve timing and concurrency characteristics Same number of user connections Replay Client Multithreaded OCI Client Drives multiple captured processes Scalable Architecture Interprets capture into sequence of OCI calls Functional replay Replay Clients Timing Preservation Timing Preservation Re-mapping Server Server Server Commit Order Synchronization Sequence Replay Background File 1 File 2 File N Metadata Replay Files

25 Database Replay Step 4: Analysis & Reporting Error Divergence: For each call error divergence is reported New: Error encountered during replay not seen during capture Not Found: Error encountered during capture not seen during replay Mutated: Different error produced in replay than during capture Data Divergence Replay: Number of rows returned by each call are compared and divergences reported User: Application level validation scripts Performance Reporting Capture and Replay Report: Provides high-level performance information ADDM Report: Provides in-depth performance analysis AWR, ASH Report: Facilitates comparative or skew analysis

26 Database Replay Comparison Technology that can only be built by Oracle Workload 3rd Party Load Testing Tools Artificial simulated workload Oracle Database Replay Real application workload Test Coverage 1-5% of workflows 100% of workflows Test Effort Simple app: weeks Complex app:months Simple app: days Complex app: days

27 Database Replay Comparison of DB Replay & LoadRunner Time Taken (Days) Install & Setup 24 0 Understand Application Usage 20 0 Identify Key Transactions 20 2 Generate Workload 5 Run Test 5 DB Replay LoadRunner Total Testing Time DB Replay: ½ month LoadRunner: 7 ½ months

28 SQL Performance Analyzer (SPA) Overview Helps users predict the impact of system changes on SQL workload response time SQL Workload STS Low overhead capture of SQL workload to SQL Tuning Set (STS) on production system Build different SQL trials (experiments) of SQL statements performance by test execution Analyzes performance differences Offers fine-grained performance analysis on individual SQL Integrated with STS, SQL Plan Baselines, & SQL Tuning Advisor to form an end-to-end solution SQL plans + stats Pre-change Trial Compare SQL Performance Analysis Report SQL plans + stats Post-change Trial

29 SQL Performance Analyzer Workflow Production Test Make Change Steps (1) (2) (3) (4) (5) Capture SQL (STS) Transport STS Execute SQL Pre-change Execute SQL Post-change Compare Perf. Reiterate No Done? (6) Production Change / (7) Tuning Deployment Tuned System Yes

30 SQL Performance Analyzer SPA Report

31 Oracle Real Application Testing Best Practices 1 Pre-capture Planning Security: SYSDBA and/or SYSOPER privileges needed Storage Overhead Provide adequate disk space for workload capture files Space depends on size and type of workload Extrapolate storage needed based on running capture for few minutes TPC-C Benchmark: 1.2 GB for 100 users for approx. 20min System Overhead Ensure system has spare capacity (CPU, memory, I/O) for capture System Activity Start Capture Finish Capture Time

32 Oracle Real Application Testing Best Practices 2 Workload Capture Database restart (optional): Recommended to minimize divergence File system for RAC: Use shared file system AWR Data Export Export AWR Data to enable in-depth replay performance analysis Consider impact on production system before exporting Test System Setup Application data in test system must be identical to production to minimize replay data divergence Have strategy in place to duplicate production data on test Use RMAN DUPLICATE or Snapshot Standby features to setup test system

33 Oracle Real Application Testing Best Practices 3 Workload Processing Processing workload has performance overhead and can possibly take a long time Process workload on test system instead of production Workload Replay Isolate test system Modify DB Links, directory objects pointing to production systems Isolate test system LAN (optional) Remap connection strings One-to-One: Allows simple instance-to-instance remapping Many-to-One: Maps several connection strings to a service in the test system (e.g., load balancing listener) System clock setting Reset system clock to same time as production if application logic involves SYSDATE usage Replay client deployment Use Client Calibration Advisor to identify number of replay clients needed to replay workload properly

34 Oracle Real Application Testing Best Practices 4 Full supported by SAP SAP Note Oracle 11g: The Real Application Testing Option Patches , , , must be applied on before using Workload Replay Oracle Enterprise Manager is the recommended tool for RAT

35 Oracle Real Application Testing more Informations &p_referred=undefined&p_width=800&p_height=600

36

37