Migrating an Oracle Database to Dell Compellent Storage Center

Transcription

1 Migrating an Oracle Database to Dell Compellent Storage Center Mark Tomczik, Dell Compellent Oracle Product Specialist October 2013 A Dell Technical White Paper

2 Revisions Date October 2013 Description Initial release THIS WHITE PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. PRODUCT WARRANTIES APPLICABLE TO THE DELL PRODUCTS DESCRIBED IN THIS DOCUMENT MAY BE FOUND AT: Performance of network reference architectures discussed in this document may vary with differing deployment conditions, network loads, and the like. Third party products may be included in reference architectures for the convenience of the reader. Inclusion of such third party products does not necessarily constitute Dell s recommendation of those products. Please consult your Dell representative for additional information. Trademarks used in this text: Dell, the Dell logo, Dell Boomi, Dell Precision,OptiPlex, Latitude, PowerEdge, PowerVault, PowerConnect, OpenManage, EqualLogic, Compellent, KACE, FlexAddress, Force10 and Vostro are trademarks of Dell Inc. Other Dell trademarks may be used in this document. Cisco Nexus, Cisco MDS, Cisco NX- 0S, and other Cisco Catalyst are registered trademarks of Cisco System Inc. EMC VNX, and EMC Unisphere are registered trademarks of EMC Corporation. Intel, Pentium, Xeon, Core and Celeron are registered trademarks of Intel Corporation in the U.S. and other countries. AMD is a registered trademark and AMD Opteron, AMD Phenom and AMD Sempron are trademarks of Advanced Micro Devices, Inc. Microsoft, Windows, Windows Server, Internet Explorer, MS-DOS, Windows Vista and Active Directory are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell and SUSE are registered trademarks of Novell Inc. in the United States and other countries. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Citrix, Xen, XenServer and XenMotion are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware, Virtual SMP, vmotion, vcenter and vsphere are registered trademarks or trademarks of VMware, Inc. in the United States or other countries. IBM is a registered trademark of International Business Machines Corporation. Broadcom and NetXtreme are registered trademarks of Broadcom Corporation. Qlogic is a registered trademark of QLogic Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and/or names or their products and are the property of their respective owners. Dell disclaims proprietary interest in the marks and names of others. 2 Migrating an Oracle Database to Dell Compellent Storage Center

3 Table of contents Revisions Preface Audience Purpose Customer support Introduction Features of Dell Compellent Storage Center Dynamic Block Architecture Storage Virtualization Dynamic Capacity (Thin Provisioning) Data Instant Replay (DIR) Data Progression Fast Track Consistency group Benefits of Oracle on Dell Compellent Storage Center Storage setup and configuration Important migration considerations Migration tools Endianness Migrating a database How to determine supported platforms and endianness Determining database endianness Selecting and executing the migration methodology Conclusion A Additional resources Migrating an Oracle Database to Dell Compellent Storage Center

4 1 Preface This document reviews Dell Compellent features and key migration considerations of migrating Oracle to Dell Compellent. It assumes that the server, hardware architecture, OS, version of Oracle, Oracle features installed and implemented does not change between the source and target platforms, and it should not be considered a how-to or a comprehensive user guide into the migration process. For that type of information, rely upon the plethora of information provided in Oracle documentation and at My Oracle Support ( See the references at the end of this document for additional information. 1.1 Audience The audience for this document is intended for database administrators, system administrators and storage administrators that need to understand some of the key points of interest for migrating an Oracle database to Dell Compellent Storage Center. Readers should be familiar with Dell Compellent Storage Center and have prior experience in configuring and operating the following: Oracle Architecture Oracle 11g Real Application Clusters (RAC) or Single Instance Oracle s Automated Storage Management (ASM) General understanding of SAN technologies OS platform architecture OS Administration 1.2 Purpose This document outlines some of the key steps of migrating an Oracle database to Dell Compellent Storage. It also shows how to combine Oracle with Dell Compellent storage technology, and will describe the features and terminology from Dell Compellent and Oracle. 1.3 Customer support Dell Compellent provides live support EZSTORE ( ), 24 hours a day, 7 days a week, 365 days a year. For additional support, Dell Compellent at support@compellent.com. Dell Compellent responds to s during normal business hours. To acquire Dell assistance with your database migration, please contact your local Dell Sales person. 4 Migrating an Oracle Database to Dell Compellent Storage Center

5 2 Introduction When designing the physical layer of a database, DBAs must consider many server and storage configuration options. The solution must facilitate high performance I/O. It must also protect against failure of hardware, such as disks, host bus adapters (HBAs), and fabric switches. The strains of a growing and ever changing workload imposed upon the storage solution require the server and storage configuration to be dynamic. These same strains also create additional work for the server and storage administrators and require them to be much more responsive to the needs of the business. There are also strains on the business caused by legacy systems that need to be replaced. Sometimes these strains and demanding business needs require IT departments to consider migrating platforms to Dell Compellent so greater efficiencies and cost reductions can be realized. A part of the overall platform migration, is a process called database migration. The database migration is a process that moves a database from one platform (source platform) to a different platform (target platform). The ability to perform a migration in Oracle has always existed, and was historically accomplished with Oracle s export and import utilities. However, as database sizes have increased and maintenance windows have continued to shorten, in some cases the ability to migrate large databases within scheduled windows with export / import cases is no longer practical. Before we discuss the migration options available in Oracle 11g, we ll examine some of the Dell Compellent features which drives the need to migrate to realize greater efficiency and lower total cost of ownership (TCO). 5 Migrating an Oracle Database to Dell Compellent Storage Center

6 3 Features of Dell Compellent Storage Center Dell Compellent provides a number of features that can be taken advantage of in an Oracle environment. Some of these features are discussed below. 3.1 Dynamic Block Architecture Dynamic Block Architecture records and tracks specific information, called metadata, about every block of data, and provides the system intelligence on how every block is being used. Metadata about blocks is gathered without system overhead and can be extensive, including time written, the type of disk drive used, the type of data stored, RAID level, and more. All of this metadata or data about the data enables Storage Center to take a more sophisticated and intelligent approach to storing, recovering and managing data. For example, metadata that describes that specific blocks of data have been accessed the most can be used by Storage Center to move the blocks to a faster tier of storage. Metadata describing inactive blocks can be used by Storage Center to automatically place the blocks on lower cost, lower performance drives. Figure 1 Dynamic Block Architecture 6 Migrating an Oracle Database to Dell Compellent Storage Center

7 3.2 Storage Virtualization Dell Compellent Storage virtualizes enterprise storage at the disk level, creating a dynamic pool of storage resources shared by all servers. Because read/write operations are spread across all available drives within the same tier, multiple requests are processed in parallel, boosting system performance. With Dell Compellent Storage Virtualization, users can create hundreds of volumes in seconds to support any server platform and optimize the placement of applications. Storage Center automatically restripes all data across all drives in the storage pool when adding disks, and can dynamically scale the storage pool without disruptions. Virtualization also allows Storage Center to change RAID levels on the fly. Figure 2 Storage virtualization 3.3 Dynamic Capacity (Thin Provisioning) With traditional storage systems, Administrators must purchase, allocate and manage capacity upfront, speculating where to place storage resources and creating large, underutilized volumes with long term growth built in. This practice leaves the majority of disk space allocated yet unused, and only available to specific applications. Dell Compellent s Thin Provisioning, called Dynamic Capacity, delivers the highest storage utilization possible by eliminating allocated but unused capacity. Dynamic Capacity completely separates storage allocation from utilization, enabling users to create any size virtual volume upfront, yet only consume actual physical capacity when data is written by the application. 7 Migrating an Oracle Database to Dell Compellent Storage Center

8 Figure 3 Dynamic capacity 3.4 Data Instant Replay (DIR) Data Instant Replay is most often compared to "snapshot" technology and provides continuous spaceefficient data protection using a feature called Replays. Replays create point-in-time copies of your volumes where further changes to a volume are journaled in a way that allows the volume to be rolled back to its original state when the replay was created. Replays can be mounted as volumes, called View Volumes, for the sake of partial or full volume data restore. There are various uses of Replays, but with respect to an Oracle database, database backups and cloning are easily performed. Policy based schedules, with varying intervals and expiration, can be created to manage Replays and provide greater recovery capabilities to a previous know state, and there is no limit on the number or Replays taken. Replays, when used in conjunction with another feature call Consistency Groups, provide data integrity of data spanning multiple volumes. Once a Replay is created, an unlimited number of new volumes, called View Volumes, can be created from the Replay. For more information on View Volumes, see section Consistency Group. 8 Migrating an Oracle Database to Dell Compellent Storage Center

9 Figure 4 Data Instant Replay 3.5 Data Progression Fluid data storage or automated tiered storage is another feature, called Data Progression, offered by Dell Compellent. Data Progression automatically migrates enterprise data to the optimal storage tier based on a set of predefined or custom policies or storage profiles. Over time, infrequently accessed data migrates to lower-cost drives (SATA), while the most active, mission-critical data migrates to high-performance (expensive FC/SAS) drives. The number of days used to alert Data Progression to migrate the data can easily be changed. By default, data that has been accessed within the last four progression cycles is stored on the highest tier, comprised of the fastest disks. Data that has not been accessed for the last 12 progression cycles is gradually migrated down to the lowest tier, comprised of slower, cheaper, larger disks. Data progression eliminates the need to manually classify and migrate data to different storage tiers while reducing drive number and cost, and cooling and power costs. Figure 5 Data Progression 9 Migrating an Oracle Database to Dell Compellent Storage Center

10 3.6 Fast Track Dell Compellent Fast Track technology enhances Automated Tiered Storage by dynamically placing the most frequently accessed data on the fastest, or outer, tracks of each disk drive. Meanwhile, the least active blocks of data remain on the inner tracks of all the drives in each storage tier. The result is ready access to frequently used data with fewer drives than conventional storage systems. Figure 6 Fast Track 3.7 Consistency group The Dell Compellent consistency group feature allows storage administrators to take a snapshot of an Oracle database atomically. When creating a snapshot of a running Oracle, make sure that all storage volumes (LUNs) that make up the database be atomically. Without a consistency group, a usable snapshot of a running database cannot be made. If Storage Center is on 4.x code, there is no consistency group available when using data Instant Replay for snapshots. In order to take a snapshot of a database while it is running, the Oracle database online redo log files, and control files must exist on the same volume. Multiplexing online redo logs and control files across volumes cannot be done. If the Storage Center is on 5.x code or higher, then there is no restriction. Also note that testing needs to be done to determine the number of LUNs required for your database for optimal configuration in terms of performance since every operating system is different. 10 Migrating an Oracle Database to Dell Compellent Storage Center

11 Figure 7 Consistency group 3.8 Benefits of Oracle on Dell Compellent Storage Center Some of the benefits of deploying Oracle to a Dell Compellent solution are listed in the below table. Table 1 Benefit Benefits of Oracle on Dell Compellent Storage Details Lower total cost of ownership (TCO) Greater manageability Reduces acquisition, administration, and maintenance costs Ease of use, implementation, provisioning, and management 11 Migrating an Oracle Database to Dell Compellent Storage Center

12 Simplified RAC Implementation High availability and scalability Dell Compellent Information Life Cycle (ILM) benefits Provides shared storage (raw or filesystems) Clustering provides higher levels of data availability and combined processing power of multiple server for greater throughput and scalability Provides tiered storage, dynamic capacity, data progression, thin provisioning, instant replay (snapshot) and more 12 Migrating an Oracle Database to Dell Compellent Storage Center

13 4 Storage setup and configuration When migrating an Oracle database to Dell Compellent, it s important to understand how to configure Dell Compellent Storage Center, and where one should place the different Oracle database files in Storage Center. The information present in the below table is a guideline that can help with the configuration and placement of Oracle files on Dell Compellent. One should understand that the information provided is only a recommendation, and that the actual configuration and placement of files will be dictated by your business needs. It is strongly recommended that the following whitepapers regarding Dell Compellent and Oracle best practices be read and understood before configuring and creating the database on the target platform, and performing the migration of the source database to it: Dell Compellent Oracle Best Practices Dell Compellent Oracle Backup and Recovery Best Practices Dell Compellent Oracle ASM Best Practices Dell Compellent Oracle Data Progression and thin Provisioning Dell Compellent Oracle 11g RAC and Storage Center Dell Compellent Oracle DataWarehouse Best Practices Table 2 Storage setup and configuration Description RAID10 SSD RAID10/FC/SAS 15K rpm RAID10/FC/SAS 10K rpm RAID5/FC/SAS 15K rpm RAID5/FC/SAS 15K rpm RAID5/FC/SAS 10K rpm Data files OK (W) Recommended (W) OK (W) DP DP DP Control files Online redo logs Recommended (W) Recommended (W) OK (W) OK (W) Not required Not required Not required OK (W) OK (W) Avoid Avoid Avoid Archived redo logs Flashback OCR files / Voting Disks Recommended (W) Recommended (W) Recommended (W) OK (W) Not required Not required DP OK (W) Not required Not required DP OK (W) Avoid Avoid Avoid Abbreviations: 1. W Writes 2. DP Data Progression a. If Fast Track is licensed, then it is enabled by default and will be utilized behind the scenes. No manual configuration is required. 13 Migrating an Oracle Database to Dell Compellent Storage Center

14 b. Drives with higher RPM provide higher overall random-access throughput and shorter response times than drives with lower RPM. c. Because of better performance, SAS or Fibre Channel drives with 15K rpm are always recommended for storing Oracle datafiles and online redo logs. d. Serial ATA and lower cost Fibre Channel drives have slower rotational speed and therefore recommended for Oracle archived redo logs and flashback recovery area with Data Progression. 14 Migrating an Oracle Database to Dell Compellent Storage Center

15 5 Important migration considerations Independent of the storage solution, the migration spend by many organization can be a rather expensive and a risky proposition, as about 75 percent of systems fail to meet expectations after a migration. Because of this, it is imperative to institute a comprehensive and well defined migration plan, with adequate funding and resources. The comprehensive plan also needs to include time and resources to gather knowledge of both source and target systems, as transferring data into a new system without this knowledge may perpetuate legacy problems. To assist with the migration plan, it s recommended that the below outline of important tasks / steps be the minimal set of steps to follow 1 1. Planning e. Clearly define migration scope f. Due diligence with other teams g. Define acceptance criteria including expected response times h. Budget (hard and soft resources) and timelines i. Data stewardship and governance 3. Data knowledge and awareness a. Prioritize scope b. Profile and audit data, including tiered storage placement c. Perform cost/benefit analysis 4. Designing and building a. Define mapping rules for migrating data in small phases b. Define acceptance tests i. End of week, month, quarter, year processing ii. Batch and online stress and volume, system, and unit tests iii. Estimate the expected migration time requirements 5. Pre-migration execution establish baselines a. Refine scope b. Generate performance metrics for pre-migrated database, OS, network, storage c. Run acceptance test to set baseline on results 6. Execution a. Perform migration, including any necessary ETL 7. Post-migration execution: Testing, verification and acceptance a. Generate performance metrics for migrated database, OS, network, storage b. Run acceptance test and compare against baseline c. Resolve issues and re-execute post-migration steps d. Perform full database backup of migrated database 8. Follow-up and maintenance Operational requirements should also be included in the above process and should include, but not limited to the following: 15 Migrating an Oracle Database to Dell Compellent Storage Center

16 Changes to the backup/recovery processes Changes to disaster recovery processes Changes to replication processes Changes to database cloning operations Required migration downtime for each application or database Dependencies between applications/schemas within the database Downtime implications to the business Changes to the operational window Additional staff required and considerations (training, migration processes, ) Simultaneous usage of the old and new storage solutions 16 Migrating an Oracle Database to Dell Compellent Storage Center

17 6 Migration tools There is no one migration utility or script that performs platform migrations. But Oracle does provide a number of different tools that are used in combination to simplify migrating a database. Below are some tools that could be used. Which ones you choose will be governed by the OS and Oracle versions on the source and target servers as well as business requirements and constraints 2 : Oracle SQL Developer 3 Oracle Transportable tablespaces Oracle RMAN convert function for transportable tablespaces Oracle ASM mirroring Oracle Datapump Export and Import Oracle Create Tables As Select (CTAS) Oracle Streams replication Oracle Data Guard Heterogeneous Primary and Physical Standbys Oracle GoldenGate and Informatica Dell Quest Shareplex Informatica Data Replication (WisdomForce) Some of these tools can be used when migrating an Oracle database to Dell Compellent. For example, the following tools could be used to perform the following: ASM mirroring: Place one side of the mirror on the old SAN, and the other side on Dell Compellent. Then break the mirror. Oracle Data Guard: Create a standby database on Dell Compellent, and then convert the standby to the primary database. If Oracle hybrid columnar compression (HCC) is not used and Data Guard is run in maximum protection the switchover time is minimized. Data Guard requires the exact same database version and structure on the target, which limits you to same-platform-same-version migrations. This option requires the same endianness between systems. Oracle GoldenGate and Informatica: Migrate from different versions of Oracle without application downtime, and you can run mixed mode (i.e. performing transactions against the old and new database simultaneously because it is bi-directional). Going live then is nothing more than disabling the old environment. 17 Migrating an Oracle Database to Dell Compellent Storage Center

18 7 Endianness A determining factor in the ability to migrate a database, or transport tablespaces across platforms is the endianness of the source and target platforms. Endianness refers to the format of how bytes of numeric values are ordered within memory, and there are several endian formats: little-, big-, or mixed- (middle-) endian. Of the three formats, mixed-endian is rare and is not covered within this document, and does not appear in Oracle s 11gR2 list of supported endian types for platform migrations: SQL> select distinct version, endian_format 2 from v$instance 3, v$transportable_platform; VERSION ENDIAN_FORMAT Big Little SQL> With little-endian a numeric value is written or stored in memory with the smallest part (byte), or least significant part (byte) of the value first, followed by more significant parts (bytes) in successive order. In contrast, with big-endian a numeric value is written or stored in memory with the most significant part (byte) first, followed by lesser significant parts (bytes). For example, given the value (10D7 16 ), and 8- bit memory words, the value would be stored as follows: Figure 8 Little- and Big-endian Because endianness changes how numeric values are represented in memory, failures or corruption can occur during a migration if endianness is ignored. For further information on endian formats and descriptions, refer to the resources located at the end of this document Migrating an Oracle Database to Dell Compellent Storage Center

19 8 Migrating a database Database migrations consist of a set of steps that move a database from one system to a different system. Oracle has always provided tools to accomplish this effort, but as databases grew, the legacy tools (export/import) could require a migration to span days for a very large database, causing unacceptable outages to applications and business units. To overcome this shortcoming, Oracle released the capability to transport tablespaces (TSS) in Oracle 8i to platforms with like endianness. Later Oracle expanded upon this technology in 10g R1 and released new capabilities: cross-platform transportable tablespaces (XTTS), to reduce the amount of time needed to migrate a database between platforms with different endianness, and datapump. Oracle continued to enhance capabilities around migration and in 10gR2 the feature called Transportable Database (TDB) was introduced to transport an entire database between platforms with the same endianness. 8.1 How to determine supported platforms and endianness In 11gR2, platform endianness is determined by executing the following query against dynamic view V$TRANSPORTABLE_PLATFORM. The platforms listed in the output are supported migration platforms for tablespace transports within Oracle. SQL> col platform_name format a36 SQL> set linesize 132 SQL> set pagesize 60 SQL> select * from v$transportable_platform 2 order by platform_id; PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT Solaris[tm] OE (32-bit) Big 2 Solaris[tm] OE (64-bit) Big 3 HP-UX (64-bit) Big 4 HP-UX IA (64-bit) Big 5 HP Tru64 UNIX Little 6 AIX-Based Systems (64-bit) Big 7 Microsoft Windows IA (32-bit) Little 8 Microsoft Windows IA (64-bit) Little 9 IBM zseries Based Linux Big 10 Linux IA (32-bit) Little 11 Linux IA (64-bit) Little 12 Microsoft Windows x86 64-bit Little 13 Linux x86 64-bit Little 15 HP Open VMS Little 16 Apple Mac OS Big 19 Migrating an Oracle Database to Dell Compellent Storage Center

20 17 Solaris Operating System (x86) Little 18 IBM Power Based Linux Big 19 HP IA Open VMS Little 20 Solaris Operating System (x86-64) Little 21 Apple Mac OS (x86-64) Little 8.2 Determining database endianness To determine the endianness of the source 11gR2 database, the following query can be executed against dynamic views V$TRANSPORTABLE_PLATFORM and V$DATABASE in both databases. The below only shows the execution against the source database: SQL> col platform_name format a30 SQL> select d.name, tp.platform_name, tp.endian_format 2 from v$transportable_platform tp 3, v$database d 4 where tp.platform_name = d.platform_name; NAME PLATFORM_NAME ENDIAN_FORMAT MYPROD Linux x86 64-bit Little SQL> If the endianness of the source platform is different than the endianness of the target platform, an additional step must be executed during a database migration to perform the correct data conversion of numeric values 5. If this additional step is omitted during the migration, failures and/or corruption can be experienced and lead to an unsuccessful migration. The additional step can either be executed on either the source platform or the target platform. 20 Migrating an Oracle Database to Dell Compellent Storage Center

21 8.3 Selecting and executing the migration methodology Based upon your findings of the source and target server s endianness, Oracle recommends that a migration is performed using the following methodologies: Table 3 Endianness and migration methodology Endianness If the target platform is found If the target platform is not found If both platforms share the same endianness Migration Methodology Use cross-platform transportable tablespaces (XTTS) Use data pump with a full database export/import Use transportable database (TDB) To execute the migration, please refer to the migration information published by Oracle. See the Additional resources section at the end of this document for a list of recommended readings. The above table assumes that at least the migration involves migrating from one server to another. But not all migrations involve migrating to a different server. Sometimes a migration only involves migrating to a different storage solution, say migrating just the database (not including ORACLE_HOME) from DAS to Dell Compellent, and keeping the same mount points. In this case, much more simplified migration methodologies exist than what is presented above. However, the above migration methodologies could still be used. Assuming only a storage migration is required and the server can support both the old and new storage solutions concurrently, the main point to consider is the type of existing storage devices (raw or cooked) being used for the database. The type of storage devices being used will dictate how the database is migrated, as it involves using different OS and Oracle commands. In contrast, the process used for creating the required LUNs in Dell Complellent Storage Center for either raw or cooked devices does not change. Prior to migrating the database to Dell Compellent, create the new LUNs in Dell Compellent Storage Center for the database, and perform a full database backup. After which choose and execute the migration methodology. For example, if the database is using ASM, which is using either raw or LUNs, a possible migration process could simply be adding the new Dell Compellent block devices to the existing diskgroups, then deleting the old ASM disks from the diskgroups. This would force a rebalance in ASM, after which the database would reside on Dell Compellent. Or if the database uses filesystems (eg: ext3), or LVMs, a possible solution might be to perform a disk copy of the old database mount points to the new Dell Compellent LUNs, make other necessary changes to the OS for the new LUNs, and restart the database. Copying the data is probably the easiest part of this process, and the tool chosen for the copy can make a big difference in how efficiently the data is copied. 21 Migrating an Oracle Database to Dell Compellent Storage Center

22 A partial list of available tools that could be used for the copy is provided below. Which tool is used, depends upon your requirements: tar cpio cp dd pvmove rsync Both examples above provide an abridged outline of the migration process, and illustrate how simple a migration could be if the migration only involves migrating a database to Dell Compellent storage. 22 Migrating an Oracle Database to Dell Compellent Storage Center

23 9 Conclusion Since Dell Compellent storage presents block devices to a server, there s nothing complex that needs to be considered when using Dell Compellent storage with Oracle. Coupling Dell Compellent Storage Virtualization and Dynamic Block Architecture with Oracle best practices makes migrating a database an efficient and an easy process from a storage perspective. All the complexity and work of the migration is driven up to the Oracle an OS layers, making it a complete transparent operation for Dell Compellent storage. Dell Compellent storage is a robust and scalable storage solution for Oracle databases, if additional storage is needed for the migration, adding additional spindles or SSDs to the configuration requires no outage. Storage Center adds the additional benefit of also ensuring that the data is spread evenly across all spindles at all times without having the DBA or storage administrators continually revisit or dedicate certain spindles of the storage to maintain performance of the database during the migration. Additional benefits include dramatically reducing the time and effort required for capacity planning and volume management, as well as the ability to take advantage of Replays to backup and clone databases. Traditional systems are prone to hot spots because there are very few drives allocated to a specific volume for that server. Spreading the access across multiple drives eliminates these hot spots and increases performance. With Dell Compellent, volumes can be created in seconds and performance is optimized with all the drives acting together which allows the DBAs, system and storage administrators to focus their efforts on the migration 23 Migrating an Oracle Database to Dell Compellent Storage Center

24 A Additional resources References used in this document 1: Successful Data Migration An Oracle White Paper October October 2011, Thursday 17 October PDF file. 2: Migration Of An Oracle Database Across OS Platforms (Generic Platform) (Doc ID ). support.oracle.com. My Oracle Support, 29 April 2013, Thursday 17 October : Oracle SQL Developer Migration An Oracle White Paper, (May 2010) PDF file. 4: Endianness. en.wikipedia.org. Wikipedia The Free Encyclopedia. 15-October-2013, Tuesday 15 October : How to Migrate to different Endian Platform Using Transportable Tablespaces With RMAN (Doc ID ). support.oracle.com. My Oracle Support, 24 July 2013, Thursday 17 October Additional references or recommended publications: Dell Compellent Copilot EZSTORE ( ) is committed and focused on your Compellent support needs 24 x 7, every day of the year. Dell Compellent responds to s during normal business hours. Dell Compellent publications on Knowledge Center: - Dell Compellent Oracle Best Practices - Dell Compellent Oracle Backup and Recovery Best Practices - Dell Compellent Oracle ASM Best Practices - Dell Compellent Oracle Data Progression and thin Provisioning - Dell Compellent Oracle 11g RAC and Storage Center - Dell Compellent Oracle DataWarehouse Best Practices Support.dell.com is focused on meeting your needs with proven services and support. DellTechCenter.com is an IT Community where you can connect with Dell Customers and Dell employees for the purpose of sharing knowledge, best practices, and information about Dell products and installations. Changing between 32-bit and 64-bit Word Sizes (Doc ID ). support.oracle.com. My Oracle Support, 01 March April 2013, Thursday 17 October Migrating an Oracle Database to Dell Compellent Storage Center

25 Transporting Tablespaces Between Databases Oracle Database Administrator s Guide 11g Release 1 (11.1), B , (March 2008) docs.oracle.com. 12:30-12:45 PDF file. Platform Migration Using Transportable Tablespaces: Oracle Datbase 11g Release 1 Oracle Maximum Availability Architecture White Paper February N.d., Thursday 17 October PDF file. Oracle Database Data Warehousing Guide 11g Release 2 (11.2) E , (July 2013) docs.oracle.com. PDF file. Oracle Database Administrator s Guide 11g Release 2 (11.2) E , (July 2013) docs.oracle.com. PDF file. Master Note for Transportable Tablespaces (TTS) Common Questions and Issues (Doc ID ). support.oracle.com. My Oracle Support, 23 August 2013, Thursday 17 October Migration Of An Oracle Database Across OS Platforms (Generic Platform) (Doc ID ). support.oracle.com. My Oracle Support, 29-April-2013, Friday 18 October How to Create Transportable tablespaces Where the Source and Destination are ASM-Based (Doc ID ). support.oracle.com. My Oracle Support, 15-Feburary 2013, Thursday 17 October Oracle Database Utilities, 11g Release 2 (11.2), E , (December 2012) docs.oracle.com. PDF file. Data Pump Export Oracle Database Utilities, 11g Release 2 (11.2), E , (December 2012) docs.oracle.com. 2:1-2:60 PDF file. Oracle 3 rd Party Database Migrations, (N.D.) 17-October Website: Oracle Database Backup and Recovery User s Guide 11g Release 1 (11.1) B (August 2008) docs.oracle.com. PDF file. Methods for Upgrading to Oracle Database 11g Release 2, (September 2009) PDF file Migrating an Oracle Database to Dell Compellent Storage Center