Oracle Integration at SAP Dr Christian Graf SAP

Oracle Integration at SAP Dr. Christian Graf SAP AG

Topics ã Ø Introduction Ø my. SAP. com Product Strategy Ø my. SAP. com Release Strategy Ø Oracle Release Integration at SAP Ø MCOD Ø Brconnect 6. 10 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 2

Introduction ã Ø More than 12 years SAP – Oracle collaboration Ø More than 10, 000 SAP customers on Oracle DB Ø 70% of SAP installations run on Oracle DB Ø Joint SAP & Oracle development (platform) team in Walldorf Ø Support teams in Rot (Germany) & USA Ø SAP & Oracle Partner & Presales teams in Walldorf SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 3

Topics ã Ø Introduction Ø my. SAP. com Product Strategy Ø my. SAP. com Release Strategy Ø Oracle Release Integration at SAP Ø MCOD Ø Brconnect 6. 10 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 4

my. SAP. com Product Strategy Until 1996/1997: mainly SAP R/3 Today: ã Ø SAP R/3 Core Application Ø SAP BW Business Warehouse Ø SAP APO Advanced Planner & Optimizer Ø SAP BBP/CRM Business to Business Proc. & Customer Relationship Management Ø SAP KM Knowledge Warehouse Ø . . . SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 5

my. SAP. com Product Strategy BBP/CRM Workplace KM BW APO SAP R/3 Web Application Server (WAS) Database (Oracle, SAPDB, Others) ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 6

my. SAP. com Product Strategy Currently supported releases: 3. 1 I, 4. 0 B, 4. 5 B, 4. 6 x, 6. x Since SAP R/3 Release 4. 6 x: WEB Application Server (WAS), formerly R/3 Basis, is now a separate product/component: Ø Serves as infrastructure component for SAP applications Ø Load balancing/dispatching Ø Covers platform dependencies Ø ABAP workbench, batch, spool, monitoring, security, . . . Ø Provides common features required by the SAP product family ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 7

Upcoming: SAP R/3 Enterprise Add On SAP R/3 Enterprise Core Add On Web Application Server (WAS) Database (Oracle, SAPDB, Others) ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 8

Topics ã Ø Introduction Ø my. SAP. com Product strategy Ø my. SAP. com Release strategy Ø Oracle Release Integration at SAP Ø MCOD Ø Brconnect 6. 10 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 9

my. SAP. com Release Strategy Original SAP release/maintenance schedule Kernel/WAS Version ã BW Support until 31 I 8/2003 40 B 8/2003 45 B (1. 2 B) 8/2003 WAS 4. 6 C/D Kernel 2. 0 B/2. 1 C 3/2005 WAS 6. 10 3. 0 A TBD WAS 6. 20 3. 0 B TBD SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 10

my. SAP. com Release Strategy New SAP release/maintenance schedule Kernel/WAS Version BW Extended Support 31 I 12/2003 40 B 12/2003 45 B (1. 2 B) 46 B 12/2003 WAS 4. 6 C/D Kernel 2. 0 B/2. 1 C 3/2006 No additional maintenance fee ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 11

my. SAP. com Release Strategy Extended SAP release/maintenance schedule Kernel/WAS Version BW Extended Support 31 I 12/2004 40 B 12/2004 45 B (1. 2 B) 46 B 12/2004 + 2% points additional maintenance fee ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 12

my. SAP. com Release Strategy SAP OS platform coverage: 31 I – 46 C 32 Bit ã 64 Bit AIX: (4. 3) X X HP-UX: (11/11 I) X X DEC True 64: (5. 1) --- X Reliant Unix: (5. 45 B) X X Solaris: (8. 0) X X Linux (>=40 B): (Glibc 2. 2. 2) X --- WIN: X --- (4. 0/W 2 K) SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 13

my. SAP. com Release Strategy SAP OS platform coverage: WAS 6. 20 ã 32 Bit 64 Bit AIX: (5. 1) --- X HP-UX: (11/11 I) --- X DEC Tru 64: (5. 1) --- X Reliant Unix: (5. 45 B) --- X Solaris: (8. 0) --- X Linux: (Glibc 2. 2. 2) X --- WIN: (W 2 K) X TBD SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 14

my. SAP. com Release Strategy SAP OS platform coverage: WAS 6. 20 ã AIX: 5. 1 64 Bit Ø Oracle 9. 2 required Ø Scheduled for May/2002 Ø SAP 46 D kernel certification process starts immediately after 9. 2 availability on AIX 5. 1 (pretests are already running) Ø 46 D kernel based pilot phase planned until end of June/2002 Ø Planned GA/Ramp. Up during Q 3/2002 Ø WAS 6. 20 certification during Q 3/2002 Ø See OSS note 502513 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 15

my. SAP. com Release Strategy SAP OS platform coverage: General info Ø Ø SAP Kernel Release Note Number 31 I 23875 40 x/45 x 85838 46 x 156548 6 x 407314 SAP Service Marketplace Ø http: //www. service. sap. com/platforms ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 16

Topics ã Ø Introduction Ø my. SAP. com Product strategy Ø my. SAP. com Release strategy Ø Oracle Release Integration at SAP Ø MCOD Ø Brconnect 6. 10 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 17

Oracle Integration SAP certified Oracle versions for 31 I – WAS 6. 20 SAP Oracle Support 31 I 8. 1. 7 12/2003 40 B 8. 1. 7 12/2003 45 B 8. 1. 7 12/2003 WAS 4. 6 C 8. 1. 7 12/2003 WAS 6. 10 8. 1. 7 12/2003 WAS 6. 20 ã Oracle planned SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 18 8. 1. 7+9. 0. 1? /9. 2 12/2002|6/2004

Oracle Integration Schedule for upcoming my. SAP. com products Based on WAS 6. 20: Ø SAP R/3 Enterprise Ø BW 30 B Ø my. SAP CRM 3. 1 Start QA Process: ã Ramp. Up/GA: Ø WAS 6. 20: February/2002 May/2002 Ø SAP R/3 Enterprise: May/2002 August/2002 Ø BW 30 B: March/2002 June/2002 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 19

Oracle feature integration Ø Bitmap Tablespaces (available with 8. 1) Ø Default with WAS 6. x. Ø Ø Recommended for BW 2. x General recommendation for SAP environment in preparation Details see OSS Notes: yyyyy, xxxxx For tablespace reorganization, Bitmap Tbls is recommended/default Ø Index rebuild online (Oracle 8. 1 required) Ø Evaluation (9 i) Ø Online Table Reorg Ø Ø Ø Ø ã Undo Tablespaces Automatic PGA Memory Management Bitmap Join indexes (BW) Upsert (BW) Long to LOB migration Incremental Checkpoints CBO CPU costing SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 20

Oracle RAC Ø 2001: Oracle/Compaq Benchmark (not certified) Scaling: 1. 8 (1 -2 -4 nodes) Ø since 2/2002: Oracle/Compaq/SAP evaluation tests on Compaq cluster Ø Start of pilot program/certification procedure will depend on Ø quality & stability of RAC Ø Integration effort Ø Market demand Feedback on RAC perception/expectation? ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 21

Topics ã Ø Introduction Ø my. SAP. com Product strategy Ø my. SAP. com Release strategy Ø Oracle Release Integration at SAP Ø MCOD Ø Brconnect 6. 10 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 22

Multiple SAP Systems on Single DB instance Challenge 1 Currently different my. SAP. com products run on separate database instances. A common recovery scenario (e. g. Point in Time) spanning several SAP systems is hard to realize. Challenge 2 A system landscape with several my. SAP. com products on several database servers can be hard to administrate. Solution Run different my. SAP. components (e. g. R/3, my. SAP CRM, etc. ) in the same database instance ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 23

Multiple SAP Systems on Single Oracle Instance R/3 PRD CRM CR 1 system psap. PRDusr PRD psaproll psaptemp psap. CR 1 Installation Template: psap. CR 1 usr CR 1 Addsys. R 3 S psap. PRD<rel> /oracle/PRD/bin. . . / lib /. . . / sapdata/<files> ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 24 psap. CR 1<rel> DB Instance: Oracle. PRD /oracle/CR 1/sapdata/<files>

Topics ã Ø Introduction Ø my. SAP. com Product Strategy Ø my. SAP. com Release Strategy Ø Oracle Release Integration at SAP Ø MCOD Ø Brconnect 6. 10 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 25

BRCONNECT 6. 10: Motivation Ø Requiremets resulting from Multi Components in One Database Project (MCOD, note 388866) Ø SAP<SID> users replace SAP R/3 in database Ø Multiple SAP<SID> schemas in single database Ø DBA functions (statistics, check, next, . . . ) required for one, many or all schemas of a database Ø Requirements resulting from new functionality of Oracle 8 i Ø Support for Oracle 8 i table monitoring feature Ø Support for Oracle 8 i DBMS_STATS package Ø Decision Redesign of SAPDBA command line options, preserving menu-driven functions ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 26

BRCONNECT 6. 10: Goals Ø Fulfillment of MCOD project requirements Ø Support for new Oracle 8 i features Ø Extented functionality compared to SAPDBA Ø Integration into DBA Planing Calendar (DB 13) Ø Extented logging and tracing (BR tools like) Ø Better support for parallel processing Ø Better quality Ø Better serviceability ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 27

BRCONNECT 6. 10: Main Functions 1. Check and update statistics: brconnect -f stats 1. Replaces sapdba –checkopt | –analyze | –statistics Ø Check database system: brconnect -f check Ø Replaces sapdba –check Ø Adapt NEXT extents: brconnect -f next Ø Replaces sapdba –next Ø Cleanup DBA logs: brconnect -f cleanup Ø Replaces sapdba –cleanup ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 28 | –delete

BRCONNECT 6. 10: Additional Functions Ø Start up database: brconnect -f dbstart Ø Replaces sapdba –startup Ø Shut down database: brconnect -f dbshut Ø Replaces sapdba –shutdown Ø Check database state: brconnect -f dbstate Ø replaces check_db_open Ø Change user password: brconnect -f chpass Ø Replaces sapdba –sapr 3 | –alter_user Ø Create DBA synonyms: brconnect -f crsyn Ø This a new function ã SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 29

Stats: Parallel Update Statistics 1. With parallel threads, especially for large numbers of tables 1. 2. ã Option –p|-parallel <thread_cnt> Parameter stats_parallel_degree = <thread_cnt> Ø With the DBMS_STATS package, especially for large tables Ø Use stats_dbms_stats parameter (patch level 7): stats_dbms_stats = (<table>: R|B: <degree>, . . . ) Ø Adaptions to BW requirements Ø Special treatment of Infocube Tables Ø For details see notes 403713, 408532 & 428212 SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 30

BRCONNECT 6. 10: Check ã Ø Focus on quality Ø Functional enhancements Ø Support of ‚autoextend‘ feature Ø Enhancements for partitioning Ø Monitoring space requirements Ø Adaptions of ‚next extent‘ size SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 31

BRCONNECT 6. 10: Further info Ø OSS Notes Ø Ø SAP Service Market Place Ø ã As mentioned before http: //www. service. sap. com/DBAORA SAP AG 2002, Oracle Integration at SAP, Dr. Christian Graf 32