system migration with triple-o used for carl zeiss · system migration with triple-o used for ......

Seite 1

© Siemens IT Solutions and Services 2010. Alle Rechte vorbehalten.

System Migration with Triple-O used for

Carl Zeiss

© Siemens IT Solutions and Services GmbH 2011. Alle Rechte vorbehalten.

Stefan Greß

St. Leon Rot, 04.07.2011

An example for minimized downtime transition

SIS GO ICS G SAP 1, Stefan Greß Seite 2

© Siemens IT Solutions and Services GmbH 2011. All rights reserved.


Starting situation by Carl Zeiss

Major challenge: P10

Description of the Triple-O procedure

Evaluation of different migration methods

Reasons for choosing Triple-O

Conclusion




§ 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 10.2.0.4

§ Switch of OS platform from HP-UX to AIX

§ Preferred migration tool: R3load with migration monitor









Conclusion




§ Globally used production system (EMEA, USA, APEC)

§ SAP ECC 6.0 based on Oracle 10.2.0.4

§ 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









Conclusion



Evaluation of different migration methodsR3load with migration monitor

SourceSystem

TargetSystem

R3load Export

R3load Import

Pros§ Prefered migration method

§ No additional effort for coordination with KPMG and former provider

§ No additional costs

§ Experience with R3load and migration monitor

Cons§ Runtimes for export and import are not

acceptable

§ The pure technical migration will take up to 48 hours



Evaluation of different migration methodsO2O Transition directly from source to target system

SourceSystem

TargetSystem

O2O

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

O2O

O2O



Evaluation of different migration methods2 step approach: shadow database combined with O2O

SourceSystem

TargetSystem

O2O

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


O2O

O2OInterimSystem

Shadow Database



Evaluation of different migration methodsTriple-O

SourceSystem

TargetSystem

O2O

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


§ No experience with Triple-O

O2O

ReplicatCapture (OGG)









Conclusion




§ 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









Conclusion



Description of the Triple-O precedure timeline

June 2010 July 2010 August 2010 September 2010 October 2010 Nov. 201022 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46

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



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



Description of the Triple-O procedureLessons 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



Description of the Triple-O procedure Final migration in detail

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

OGG: Capture

O2O

OGG: Replicat

prod. operation

Postactivities SAP BASIS, Interfaces

Postactivities application management

UAT









Conclusion



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



Thank you for your attention

Stefan GreßPrincipal System Engineer SAPSiemens IT Solutions and Services GmbHSIS GO ICS G SAP1 Wuerzburger Straße 12190766 Fuerth

Phone: +49 911 978 3579 E-mail: [email protected]

Please don't hesitate to contact us …

system migration with triple-o used for carl zeiss · system migration with triple-o used for ......

Documents