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

Transcription

1

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

3 Topics Triple-O technology and prerequisites Triple-O architecture Online migration with network Online migration with limited network bandwith Online migration without network 3

4 O2O Online / Triple-O Enhancement of the O2O method allows online migrations of databases Minimize needed downtime for database copy to a few minutes (10-15) Independent from the Database size SAP Support Note:

5 Architecture O2O Source system Oracle >= 9.2 PL/SQL Package (Script generator) > 1000 GB/h (calculated on overall Database size) Large tables (>= 50 MB) Transferred directly over network Target system Oracle >= 11g Index Creation parallized Export Import For tables < 50 MB 1 5%of database size in dump files 5

6 How It Works: Modular Architecture Capture: Committed changes are captured (and can be filtered) as they occur by reading the transaction logs. Trail files: Stages and queues data for routing. Pump: Distribute data for routing to multiple targets. Route: Data is compressed, encrypted for routing to targets. Delivery: Applies data with transaction integrity, transforming the data as required. Capture Source Trail Pump Pump LAN / WAN / Internet (TCP/IP) Target Trail Delivery Source Database(s) Delivery Target Trail Bi-directional Source Trail Capture Target Database(s) 6 6

7 Overview Triple-O steps Analyze source system Create empty target system Start GoldenGate process to record changes Perform initial data load while application is running Apply changes recorded on source system Synchronize source and target system Stop application on source system Start application on target 7

8 Triple-O method summary Starting the migration doesn't need a downtime Method is save for the production system. A running Online migration can be stopped at any time, without downtime or harming the production system. Uses Oracle GoldenGate functionality A capture process on the source system analyses REDO- Log and/or archive logs, capturing DDL and DML changes Based on the Log information a logical change record (LCR) is created The LCRs are propagated to the target system. An apply process on the target system executes these LCRs 8

9 Topics Triple-O technology and prerequisites Triple-O architecture Online migration with network Online migration with limited network bandwith Online migration without network 9

10 Technologies Triple-O Initial database load is using standard methods: Oracle CTAS (Create Table As Select) Oracle Export/Import Oracle PL/SQL Oracle DataPump (Network/ Dumpfiles) An automated scheduling program is used to control the migration progress Source and target systems are compared based on DB-objects and row-count Permanent monitoring of the synchronization process (delay time of target, apply errors) 10

11 Prerequisites Triple-O Oracle version >= 9i Available CPU resources (> 30%) Available space for trail files on source: 50 % of Redo log volume/ 24h Available space for trail files on target: 50 % of Redo log volume/ 72h 11

12 Topics Triple-O technology and prerequisites Triple-O architecture Online migration with network Online migration with limited network bandwith Online migration without network 12

13 Network based migration Migration scripts Initial database load Capture Source Trail Pump LAN / WAN / Internet (TCP/IP) >= 1 GBit Target Trail Synchronisation Source Database(s) Pump Target Database(s) 13 13

14 O2O Online Data Flow Last Apply Sun 8:00 am SAP up and running Sa 8:00 am Wed 22:00 Fr 22:00 Initial database load Apply Logs Close time lag Apply Logs OGG SCN OGG Collect 14

15 Summary network migration Database downtime ~ 15 minutes Needs direct network connection Network at least 1 GBit Available space for trail files on source Trail files must be stored on the source system, while script generation is running. Volume of trail files can become very large, if script generation takes a long time (e.g. BW systems) As soon script generation is finished, trail files are transferred to the target. Transferred files are deleted on source (steady state) When initial database load (using O2O) is finished recorded changes are applied. Apply rate is up to 50 GB redo/ hour When time gap is closed, both systems can run in parallel with realt time apply of changes System switch can taken place an any time 15

16 Topics Triple-O technology and prerequisites Triple-O architecture Online migration with network Online migration with limited network bandwith Online migration without network 16

17 Network with limited bandwith Migration scripts Initial database load NAS Transport/ transfer Capture Source Trail Pump LAN / WAN / Internet (TCP/IP) >= 100 MBit Target Trail Synchronisation Source Database(s) Pump Target Database(s) 17 17

18 O2O Online Data Flow Last Apply Sun 8:00 am SAP up and running Sa 8:00 am Wed 22:00 Fr 22:00 Initial database load Apply Logs Close time lag Apply Logs OGG SCN OGG Collect 18

19 Summary network with limited bandwith Database downtime ~ 15 minutes Also 100 Mbit network connection sufficient Available space for trail files on source Trail files must be stored on the source system, while script generation is running. Volume of trail files can become very large, if script generation takes a long time (e.g. BW systems) As soon script generation is finished, trail files are transferred to the target. Transferred files are deleted on source (steady state) When initial database load (using O2O) is finished recorded changes are applied. Apply rate is up to 50 GB redo/ hour When time gap is closed, both systems can run in parallel with realt time apply of changes System switch can taken place an any time 19

20 Topics Triple-O technology and prerequisites Triple-O architecture Online migration with network Online migration with limited network bandwith Online migration without network

21 Migration without network Migration scripts Export NAS 1 Transport/ transfer Import Capture Source Trail Pump Target Trail Source Database(s) NAS 2 Target Database(s) 21 21

22 Migration without network NAS2 Transport/ transfer Source Database(s) Capture Source Trail Pump Target Trail Synchronisation Target Database(s) 22 22

23 Migration without network Migration scripts Transport/ transfer Export NAS 1 Import Capture Source Trail Pump Target Trail NAS2 Source Database(s) Capture Source Trail Pump Target Trail Synchronisation Target Database(s) 23 23

24 O2O Online Data Flow Fr 22:00 Sun 8:00 am SAP up and running Sa 8:00 am Initial database export OGG recording on 2 nd NAS Transpor, database load, apply1st GG trail 2 nd log ship Wed 22:00 Apply 2 nd Logs OGG SCN 24

25 Summary migration without network Database downtime depends on project situation Available space for trail files on source Trail files must be stored on the source system, while script generation is running. Volume of trail files can become very large, if script generation takes a long time (e.g. BW systems) As soon script generation is finished, 1 st set of trail files is transferred with export dumpfiles to the target. On source recording is writing trails files to 2 nd NAS At the desired time, SAP is stopped and 2 nd trail file set is transported to the target system Changes are applied on target System is started on the target 25

26 Questions & Answers Optional Sub Title QUESTIONS & ANSWERS 26

27 Additional Informations, please contact: Global Mail Address: Americas: EMEA: APAC: Japan:

28

29