320 likes | 335 Views
Oracle Integration at SAP. Dr. Christian Graf SAP AG. Topics. Introduction mySAP.com Product Strategy mySAP.com Release Strategy Oracle Release Integration at SAP MCOD Brconnect 6.10. Introduction. More than 12 years SAP – Oracle collaboration
E N D
Oracle Integration at SAP Dr. Christian GrafSAP AG
Topics • Introduction • mySAP.com Product Strategy • mySAP.com Release Strategy • Oracle Release Integration at SAP • MCOD • Brconnect 6.10
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
Topics • Introduction • mySAP.com Product Strategy • mySAP.com Release Strategy • Oracle Release Integration at SAP • MCOD • Brconnect 6.10
mySAP.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 • ...
mySAP.com Product Strategy Workplace BBP/CRM KM BW APO SAP R/3 Web Application Server (WAS) Database (Oracle, SAPDB, Others)
mySAP.com Product Strategy Currently supported releases: 3.1I, 4.0B, 4.5B, 4.6x, 6.x Since SAP R/3 Release 4.6x: 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
Upcoming: SAP R/3 Enterprise Add On SAP R/3 Enterprise Core Add On Web Application Server (WAS) Database (Oracle, SAPDB, Others)
Topics • Introduction • mySAP.com Product strategy • mySAP.com Release strategy • Oracle Release Integration at SAP • MCOD • Brconnect 6.10
mySAP.com Release Strategy 31I 8/2003 40B 8/2003 45B (1.2B) 8/2003 WAS 4.6C/D Kernel 2.0B/2.1C 3/2005 WAS 6.10 3.0A TBD WAS 6.20 3.0B TBD Original SAP release/maintenance schedule Kernel/WAS Version BW Support until
mySAP.com Release Strategy 31I 12/2003 40B 12/2003 45B (1.2B) 12/2003 46B 12/2003 WAS 4.6C/D Kernel 2.0B/2.1C 3/2006 New SAP release/maintenance schedule Kernel/WAS Version BW Extended Support No additional maintenance fee
mySAP.com Release Strategy 31I 12/2004 40B 12/2004 45B (1.2B) 12/2004 46B 12/2004 Extended SAP release/maintenance schedule Kernel/WAS Version BW Extended Support + 2% points additional maintenance fee
mySAP.com Release Strategy HP-UX: (11/11I) X X DEC True 64: (5.1) --- X Reliant Unix: (5.45B) X X Solaris: (8.0) X X Linux (>=40B): (Glibc2.2.2) X --- WIN: (4.0/W2K) X --- SAP OS platform coverage: 31I – 46C 32 Bit 64 Bit AIX: (4.3) X X
mySAP.com Release Strategy AIX: (5.1) --- X HP-UX: (11/11I) --- X DEC Tru 64: (5.1) --- X Reliant Unix: (5.45B) --- X Solaris: (8.0) --- X Linux: (Glibc2.2.2) X --- WIN: (W2K) X TBD SAP OS platform coverage: WAS 6.20 32 Bit 64 Bit
mySAP.com Release Strategy AIX: 5.1 64 Bit • Oracle 9.2 required • Scheduled for May/2002 • SAP 46D kernel certification process starts immediately after 9.2 availability on AIX 5.1 (pretests are already running) • 46D kernel based pilot phase planned until end of June/2002 • Planned GA/RampUp during Q3/2002 • WAS 6.20 certification during Q3/2002 • See OSS note 502513 SAP OS platform coverage: WAS 6.20
mySAP.com Release Strategy • SAP Kernel Release Note Number 31I 23875 40x/45x 85838 46x 156548 6x 407314 • SAP Service Marketplace • http://www.service.sap.com/platforms SAP OS platform coverage: General info
Topics • Introduction • mySAP.com Product strategy • mySAP.com Release strategy • Oracle Release Integration at SAP • MCOD • Brconnect 6.10
Oracle Integration 31I 8.1.7 12/2003 40B 8.1.7 12/2003 45B 8.1.7 12/2003 WAS 4.6C 8.1.7 12/2003 WAS 6.10 8.1.7 12/2003 WAS 6.20 planned 8.1.7+9.0.1?/9.2 12/2002|6/2004 SAP certified Oracle versions for 31I – WAS 6.20 Oracle Support SAP Oracle
Oracle Integration Based on WAS 6.20: • SAP R/3 Enterprise • BW 30B • mySAP CRM 3.1 Start QA Process: RampUp/GA: • WAS 6.20: February/2002 May/2002 • SAP R/3 Enterprise: May/2002 August/2002 • BW 30B: March/2002 June/2002 Schedule for upcoming mySAP.com products
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 (9i) • Online Table Reorg • Undo Tablespaces • Automatic PGA Memory Management • Bitmap Join indexes (BW) • Upsert (BW) • Long to LOB migration • Incremental Checkpoints • CBO CPU costing
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?
Topics • Introduction • mySAP.com Product strategy • mySAP.com Release strategy • Oracle Release Integration at SAP • MCOD • Brconnect 6.10
Challenge 2 A system landscape with several mySAP.com products on several database servers can be hard to administrate. Challenge 1 Currently different mySAP.com products run on separate database instances. A common recovery scenario (e.g. Point in Time) spanning several SAP systems is hard to realize. Solution Run different mySAP.com components (e.g. R/3, mySAP CRM, etc.) in the same database instance Multiple SAP Systems on Single DB instance
psaptemp psaproll Multiple SAP Systems on Single Oracle Instance R/3 PRD CRM CR1 system psapPRD psapCR1 psapPRDusr Installation Template: Addsys.R3S CR1 psapCR1usr PRD psapPRD<rel> psapCR1<rel> /oracle/PRD/bin ... /lib /... /sapdata/<files> DB Instance: OraclePRD /oracle/CR1/sapdata/<files>
Topics • Introduction • mySAP.com Product Strategy • mySAP.com Release Strategy • Oracle Release Integration at SAP • MCOD • Brconnect 6.10
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 8i • Support for Oracle 8i table monitoring feature • Support for Oracle 8i DBMS_STATS package • Decision Redesign of SAPDBA command line options, preserving menu-driven functions
BRCONNECT 6.10: Goals • Fulfillment of MCOD project requirements • Support for new Oracle 8i features • Extented functionality compared to SAPDBA • Integration into DBA Planing Calendar (DB13) • Extented logging and tracing (BR tools like) • Better support for parallel processing • Better quality • Better serviceability
BRCONNECT 6.10: Main Functions • Check and update statistics: brconnect -f stats • Replaces sapdba –checkopt | –analyze | –statistics | –delete • 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
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 –sapr3 | –alter_user • Create DBA synonyms: brconnect -f crsyn • This a new function
Stats: Parallel Update Statistics • With parallel threads, especially for large numbers of tables • 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
BRCONNECT 6.10: Check • Focus on quality • Functional enhancements • Support of ‚autoextend‘ feature • Enhancements for partitioning • Monitoring space requirements • Adaptions of ‚next extent‘ size
BRCONNECT 6.10: Further info • OSS Notes • As mentioned before • SAP Service Market Place • http://www.service.sap.com/DBAORA