SAP Mainframe Migration EDP Case-study

Transcription

1 SAP Mainframe Migration EDP Case-study The Company EDP Energias de Portugal is one of Portugal s largest companies and also one of Europe s major electricity generation, distribution and trading. It has a strong presence in Spain, US, Africa and Latin America, mainly in Brazil. In 2007 EDP announced that 39% of its produced energy came from renewable sources and that it was aiming for a 75% target by To achieve that target EDP bought the US company Horizon Wind Energy in what was the largest deal in renewable energy to date, and made EDP the world s fourth largest wind power producer. Beginning 2008 it became clear to EDP s responsibles that they were facing important decisions about the future of their IT systems. At that time, EDP was running their core business in an ERP system within a Mainframe environment: 3-node Parallel Sysplex with 6400 MIPS DB2 v7 for SAP 40 TB databases 5 x IBM P561, 16-core AIX But these systems were facing severe operational challenges: The growth rate of the largest tables was on the verge of becoming blocked by DB/2 v7 partition size limit The processing capacity was, on average, more than 90% usage There was no space to provision for new functionalities To EDP two very different paths laid ahead: Stay with the current Mainframe technology, replacing the existing equipment with new, more powered machines, and then upgrade the database to DB2 v8 and later to DB2 v9 Migrate to Unix/Oracle technology.

2 The Challenge The first path was the easier one, but it was also the most expensive and it was really just a postponing of the problem. The rewards of the second option were many, but the path was not without obstacles: EDP relied on IS-U for all their sales, invoicing, 24x7 customer service (call center) and, as such, downtime had to be minimal. The data on all environments accounted for more than 40 TB of data and IS-U Production is 14 TB in size. The first runs of the SAP unload procedure for IS-U took more than 13 days, which was a totally unacceptable downtime. The IS-U SAP version was 4.6C and had no support for table splitting which made the migration using only SAP tools impossible. Since the single use of standard SAP tools R3Load/Migmon was not viable, two other alternatives were analyzed: To copy the oldest data from the largest tables to temporary tables, would eventually reduce the migration time but required changes in the productive system and was very dependent on application changes. Choosing a hybrid migration strategy using SAP tools for the smaller tables and developing special tools to handle the 8 largest tables. This seemed the best alternative. At the end of July, 2008 a decision was taken to go with the Unix/Oracle migration before the year end. A migration strategy was prepared using direct path unload/load tools, namedpipes, network aggregates and other similar strategies to accelerate this migration speed. The maximum acceptable downtime was 5 days, including a 3 day weekend. In December 5, 18:00 WET, a Friday, the migration began. The Migration The new environment was composed of 2-node cluster Sun Microsystems M core production DB servers 4 x Sun Microsystems T5240, 16-core production application servers 2-node cluster Sun Microsystems M core, quality DB servers 2 x Sun Microsystems T5240, 16-core production application servers. The team used the BMC Unload Plus and Oracle SQL*Loader to migrate the 8 largest tables. Each partition was unloaded in parallel with direct path.

3 When completed, it was transferred by FTP to a Unix named pipe, and immediately loaded into Oracle databases with SQL*Loader direct path. When the loading of the table was finished, its indexes were immediately generated. Unload Table BMC DBUnload Load Table sqlldr Part 1 Part 2... Part n Part 1 Part 2... Part n All remaining tables were migrated using the standard SAP R3load and migmon process. The list of intermediate steps and total duration of the migration were as follows: Tuesday, December 9 at 8:00 AM, the first working day of that week, the system was available to a few restricted users. The next day, Wednesday at 8:00 AM, all users had full system access to the new environment.

4 The Results All the 7 SAP Systems (including productive, quality and development) were migrated in 3.5 months, meeting all milestones on-time and on budget. Significant service improvements were accounted for: Overall dialog response time reduced by 35% Database response time reduced to 1/3rd IS-U batch reduced in 3 hours Seven times more invoices produced per minute Online full backup (and restore) in half the time of before No downtime needed to perform backups Average processing utilization of less than 10% on the new environment compares with more than 90% of the previous 6400 MIPS 3-node Mainframe cluster 1/20th of direct infrastructure cost. Before: After:

5 Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA U.S.A. Published by Oracle Corporation, Oracle Database for SAP Global Technology Center X Copyright 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd