System Migration with Triple-O used for Carl Zeiss

Size: px

Start display at page:

Download "System Migration with Triple-O used for Carl Zeiss"

Alfred Miles
5 years ago
Views:

1 An example for minimized downtime transition System Migration with Triple-O used for Carl Zeiss Stefan Greß St. Leon Rot, Siemens IT SolutionsGmbH and Services Rechte vorbehalten. Siemens IT Solutions and Services Alle Alle Rechte vorbehalten. Seite 1

2 An example for minimized downtime transition Starting situation by Carl Zeiss Major challenge: P10 Evaluation of different migration methods Reasons for choosing Triple-O Description of the Triple-O procedure Conclusion SIS GO ICS G SAP 1, Stefan Greß Seite 2

3 Starting situation by Carl Zeiss Decision of Carl Zeiss for SIS as new IT provider Transformation of 7 SAP system lines with 19 systems in total Add-on components as for example SAP Webdispatcher, Business Connector, Solution Manager SAP systems are based on Oracle Switch of OS platform from HP-UX to AIX Preferred migration tool: R3load with migration monitor SIS GO ICS G SAP 1, Stefan Greß Seite 3

4 An example for minimized downtime transition Starting situation by Carl Zeiss Major challenge: P10 Evaluation of different migration methods Reasons for choosing Triple-O Description of the Triple-O procedure Conclusion SIS GO ICS G SAP 1, Stefan Greß Seite 4

5 Major challenge: P10 Globally used production system (EMEA, USA, APEC) SAP ECC 6.0 based on Oracle DB size at the time of delivery : 2,9 TB Largest table 170 GB (DBTABLOG) 1800 concurrent user 200 inbound and outbound interfaces Maximum downtime: Friday 9 pm to Sunday 10 pm Downtime includes: final activties on source system, technical migration, adjustment of interfaces, post activities application management, user acceptance test, troubleshooting, fallback SIS GO ICS G SAP 1, Stefan Greß Seite 5

6 An example for minimized downtime transition Starting situation by Carl Zeiss Major challenge: P10 Evaluation of different migration methods Reasons for choosing Triple-O Description of the Triple-O procedure Conclusion SIS GO ICS G SAP 1, Stefan Greß Seite 6

7 Evaluation of different migration methods R3load with migration monitor R3load Export Source System R3load Import Target System Pros Prefered migration method No additional effort for coordination with KPMG and former provider No additional costs Cons Runtimes for export and import are not acceptable The pure technical migration will take up to 48 hours Experience with R3load and migration monitor SIS GO ICS G SAP 1, Stefan Greß Seite 7

8 Evaluation of different migration methods O2O Transition directly from source to target system O2O O2O Source System O2O Target System Pros Low additional costs for O2O activation key Experience with O2O Cons Small network bandwidth No experience regarding the runtime of O2O in this environment Increased effort for coordination with KPMG and former provider SIS GO ICS G SAP 1, Stefan Greß Seite 8

9 Evaluation of different migration methods 2 step approach: shadow database combined with O2O O2O Source System Shadow Database Interim System O2O O2O Target System Pros Short downtime for final synchronisation and opening the interim database Fast O2O transition to target system within SIS data center Cons High costs for providing temporary hardware for interim system Increased effort for coordination with KPMG and former provider SIS GO ICS G SAP 1, Stefan Greß Seite 9

10 Evaluation of different migration methods Triple-O O2O O2O Source System Capture (OGG) Replicat Target System Pros Online transition with minimal downtime Cons High costs for license key and Oracle consultant Permanent monitoring necessary Risc of performance impact on productive system Increased effort for coordination with KPMG and former provider No experience with Triple-O SIS GO ICS G SAP 1, Stefan Greß Seite 10

11 An example for minimized downtime transition Starting situation by Carl Zeiss Major challenge: P10 Evaluation of different migration methods Reasons for choosing Triple-O Description of the Triple-O procedure Conclusion SIS GO ICS G SAP 1, Stefan Greß Seite 11

12 Reasons for choosing Triple-O Decisive reason: method with the shortest Downtime for technical migration Enough time for troubleshooting remaining The migration is accomplished by experienced Oracle consultants Close cooperation between SIS and Oracle consultant Minimal impact on productive system during test migrations SIS GO ICS G SAP 1, Stefan Greß Seite 12

13 An example for minimized downtime transition Starting situation by Carl Zeiss Major challenge: P10 Evaluation of different migration methods Reasons for choosing Triple-O Description of the Triple-O procedure Conclusion SIS GO ICS G SAP 1, Stefan Greß Seite 13

14 Description of the Triple-O precedure timeline June 2010 July 2010 August 2010 September 2010 October 2010 Nov Testmigration P10 Triple-O 2. Testmigration P10 Triple-O Final migration P10 Triple-O Hom. Copy Prod-System to Qual.-System Migration Dev-System R3load SIS GO ICS G SAP 1, Stefan Greß Seite 14

15 Description of the Triple-O procedure Prerequisites Provide Oracle Golden Gate (OGG) software on source and on target system Provide Oracle-to-Oracle (O2O) software on source and on target system Request activationkey Provide filesystem for trail files with enough space Enable ports activate supplemental logging on source system Create database link from target to source database SIS GO ICS G SAP 1, Stefan Greß Seite 15

16 Description of the Triple-O procedure Lessons learned after testmigrations Consider mount options for OGG filesystem Network bandwidth is a bottleneck consider more time for O2O transition Minimize impact for productive operation increase SAPS on source system Increase tablespace PSAPUNDO Keep offline redologs longer in the filesystem Transfer table DBTABLOG with multiple copy processes (MCP) No further adjustments at O2O software after finishing 2. testrun successfully SIS GO ICS G SAP 1, Stefan Greß Seite 16

17 Description of the Triple-O procedure Final migration in detail Monday Tuesday Wednesday Thursday Friday Saturday Sunday OGG: Capture O2O OGG: Replicat Postactivities SAP BASIS, Interfaces Postactivities application management UAT prod. operation SIS GO ICS G SAP 1, Stefan Greß Seite 17

18 An example for minimized downtime transition Starting situation by Carl Zeiss Major challenge: P10 Evaluation of different migration methods Reasons for choosing Triple-O Description of the Triple-O procedure Conclusion SIS GO ICS G SAP 1, Stefan Greß Seite 18

19 Conclusion Triple-O keeps its promises: minimal downtime for pure technical migration Triple-O doesn t automatically guarantee success: at least one test transition required Before choosing Triple-O: analyse costs and benefit SIS GO ICS G SAP 1, Stefan Greß Seite 19

Thank you for your attention Please don't

Straße 121 90766 Fuerth Phone: +49 911 978 3579

20 Thank you for your attention Please don't hesitate to contact us Stefan Greß Principal System Engineer SAP Siemens IT Solutions and Services GmbH SIS GO ICS G SAP1 Wuerzburger Straße Fuerth Phone: stefan.gress@siemens.com SIS GO ICS G SAP 1, Stefan Greß Seite 20

Triple-O migration scenarios. Dr. Stephan Bühne Senior Principal Technical Consultant, SAP Solution Center Walldorf

Triple-O migration scenarios. Dr. Stephan Bühne Senior Principal Technical Consultant, SAP Solution Center Walldorf Triple-O migration scenarios Dr. Stephan Bühne Senior Principal Technical Consultant, SAP Solution Center Walldorf Topics Triple-O technology and prerequisites Triple-O architecture Online migration with