<Insert Picture Here> Exadata MAA Best Practices Series Session 6: Migrating to Exadata

Transcription

1 <Insert Picture Here> Exadata MAA Best Practices Series Session 6: Migrating to Exadata Doug Utzig Doug Utzig Exadata and MAA Best Practices

2 Exadata MAA Best Practices Series 1. E-Business Suite on Exadata 2. Siebel on Exadata 3. PeopleSoft on Exadata 4. Exadata and OLTP Applications 5. Using Resource Manager on Exadata 6. Migrating to Exadata 7. Using DBFS on Exadata 8. Exadata Monitoring 9. Exadata Backup & Recovery 10. Exadata MAA 11. Troubleshooting Exadata 12. Exadata Patching & Upgrades 13. Exadata Health Check <Insert Picture Here> 2

3 Terminology MAA Oracle Maximum TTS Transportable Availability Architecture tablespaces RAC Oracle Real Application MOS My Oracle Support Clusters OTN Oracle Technology ASM Oracle Automatic Network Storage Management IB InfiniBand RMAN Oracle Recovery IPoIB Internet Protocol over Manager InfiniBand EHCC Exadata Hybrid Columnar Compression DBFS Database File System 3

4 <Insert Picture Here> Key Points 4

5 Migrating to Exadata 1. Exadata migration is the same as migrating g to Oracle Database 11g Release 2 on Linux, but you should Simplify and Optimize 2. There are many ways to migrate to Exadata your best way depends on your environment and goals 3. A fast network is important for quick migration, but other areas may slow you down 5

6 Key Point #1 Exadata migration is the same as migrating to Oracle Database 11g Release 2 on Linux, but you should Simplify and Optimize. 6

7 Migration Goal Move your data Simplify and Optimize Get rid of baggage Better performance Better resource utilization Better stability 7

8 Migration Strategy Learn target environment Oracle Exadata Database Machine No hardware changes allowed Oracle Database 11g Release 2 Upgrade Guide Upgrade Companion (MOS ) Linux 64bit or Solaris x86 Little endian Automatic Storage Management (ASM) Oracle Real Application Clusters (RAC) 8

9 Migration Strategy Simplify and Optimize For Exadata Smart storage Exadata Hybrid Columnar Compression (EHCC) For best practice Init.ora SQL Schema objects Tablespaces and data files Database extent size Character set (MOS ) 9

10 Migration Strategy Plan Prepare source system (optional) Database upgrade to 11.2 Hardware upgrade Drop unnecessary schema objects Evaluate migration methods What : Physical, Logical, Hybrid When: All at once, In stages 10

11 Migration Strategy Test Test migration to non-exadata Linux x ASM Oracle 11g Release 2 Test Latest Exadata patch bundle (MOS ) Test on your Exadata system Test Again for good measure 11

12 Key Point #2 There are many ways to migrate to Exadata - the best way depends on your environment and goals. 12

13 Migration Methods Physical Logical Hybrid combination of Physical and Logical Physical migration Block for block copy Whole tablespace or database Logical migration Unload, reload with SQL Easy to subset 13

14 Physical Migration Method Physical Standby Lowest downtime MOS MOS Transportable Database (TDB) MAA on OTN Transportable Tablespaces (TTS) MAA on OTN Details 11.1 or later Limited cross platform support ARCHIVELOG and LOGGING Oracle 11.2 on any little endian Oracle or later on any platform 14

15 Logical Migration Method Logical Standby MOS MOS MOS GoldenGate Lowest downtime MAA on OTN Data Pump Direct path load Insert As Select (IAS) Direct path load Details Oracle 11.1 or later Limited cross platform support ARCHIVELOG and LOGGING Oracle 9.2 or later ARCHIVELOG and LOGGING Oracle 10.1 or later File or network mode APPEND hint Manually yparallelize if dblink 15

16 Which One? Your best approach Are you Simplified and Optimized? Will you Simplify and Optimize? EHCC? During migration or after? Source platform and source version? Database size? How much downtime? Experience level? Other business requirements? Best may not be fastest 16

17 Scenario From Existing Database Machine Simplified and Optimized already y( (?) EHCC released in 11gR2 Option #1 Physical Standby Option #2 Logical Standby Reduce upgrade downtime if coming from

18 Scenario From 10gR2 / 11gR1 on Big Endian Option #1 Transportable Tablespaces If already Simplified and Optimized Option #2 Data Pump If not Simplified and Optimized Option #3 GoldenGate Reduce downtime 18

19 Scenario From 10gR2 / 11g on Little Endian (Non-Exadata) Option #1 Physical Standby If already Simplified and Optimized on 11g Option #2 - Logical Standby If not Simplified and Optimized i on 11g Reduce upgrade downtime if coming from 11.1 Option #3 - Data Pump Need cross platform support Need full data type support Option #4 GoldenGate Reduce downtime 19

20 Key Point #3 A fast network is important for quick migration, but other areas may slow you down. 20

21 Networks for Moving Data 10 Gb/s 40 Gb/s 1 Gb/s Ethernet InfiniBand Ethernet Best Practice Large MTU IPoIB connected mode Use all database servers 21

22 Bottleneck Not Always the Network Non-network network bottlenecks Slow source system I/O CPU to send and receive e Small I/O 22

23 Moving Data Direct to ASM Databases on Exadata use ASM Direct to ASM network transfer RMAN BACKUP AS COPY AUXILIARY ASMCMD CP DBMS_FILE_TRANSFER XDB FTP Bytes transferred!= bytes written 23

24 Staging Data Staging g space DBFS (MOS ) NFS NOT local disk 24

25 Key Points and Business Takeaways 25

26 Migrating to Exadata Key Points 1. Exadata migration is the same as migrating g to Oracle Database 11g Release 2 on Linux, but you should Simplify and Optimize 2. There are many ways to migrate to Exadata your best way depends on your environment and goals 3. A fast network is important for quick migration, but other areas may slow you down 26

27 Migrating to Exadata Business Takeaways ays Proper migration planning takes into account both your business requirements and the need to Simplify and Optimize, which may involve changing common practices you currently use, in order to get the full value out of Oracle Exadata Database Machine. Proper migration testing requires a well-researched, well-tested migration plan that ensures a successful, predictable migration to Exadata. 27

28 Migrating to Exadata Resources and References e e Latest Exadata Software (MOS ) DBFS (MOS ) Changing Storage Characteristics on Logical Standby (MOS ) Database Machine Migration using Data Guard (MOS ) Data Guard Heterogeneous Support (MOS ) 1) Upgrade Companion (MOS ) 28

29 Best Practices Additional Resources sponsored by MAA and X-Team MAA and Exadata OTN website contains best practices and different architectural solutions MAA OTN website: html Sun Oracle Database Machine and Exadata OTN website Openworld presentations 29

30 Sponsors Exadata MAA Team and X Team Operational and Configuration best practices Optimized and integrated for Exadata Generic practices for other platforms Examples: Migration, Backup/Recovery, Monitoring, Troubleshooting, Patching, MAA, Consolidation, Active Data Guard, Cloning/Reporting, Application Failover Applications MAA and Scalability Optimized and integrated for Exadata and Exalogic Examples: E-Business Suite, Siebel, Peoplesoft, Fusion Middleware Exadata Strategic Reference Program 30

31 31

32 32