Paso 8: pruebe la función de impresión directa desde USB
P. tras. abierta
Rochester, NY www.kodak.com
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 pro- duced energy came from renewable sources and that it was aiming for a 75% target by 2013. 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 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
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 impos- sible
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 develo- ping 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, named- pipes, network aggregates and other similar strategies to accelerate this migration speed. The maximum acceptable downtime was 5 days, including a 3 day weekend.
On December 5, 18:00 WET, a Friday, the migration began.
S A P M A I N F R A M E M I G R A T I O N E D P C A S E - S T U D Y
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/3 • 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
Mainframe Migration to Oracle Database 59
The Migration
The new environment was composed of • 2-node cluster Sun Microsystems M8000
32 core production DB servers • 4 x Sun Microsystems T5240, 16-core
production application servers
• 2-node cluster Sun Microsystems M5000 24-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. 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 loa- ding of the table was finished, its indexes were immediately generated.
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.
After: Before: Unload Table BMC DBUnload ftp ftp ftp ftp Load Table sqlldr Part 1 Part 2 ... Part n Part 1 Part 2 ... Part n
Profile: National Foods
National Foods with headquarters in Melbourne is one of Australasia’s largest food and beverage companies with a revenue of USD 3.56 billion in 2009, producing household-name brands in milk and dairy beverages, juice, fresh dairy, cheese and soy. National Foods is part of Lion Nathan National Foods, Australasia’s largest food and beverage company.
Today, National Foods employs more than 4,000 people. In addition to direct employ- ment, the company makes a significant con- tribution to the Australian and New Zealand economies. National Foods is also a major supporter of local industry through sourcing of local raw materials and an integral part of the retail economy.
In Australia, National Foods is the only milk business servicing the entire national market and buys 2.3 billion liters of milk that comes from more than 1,000 Australian farms to produce a range of full cream, flavored and modified fresh and UHT milks. The company also produces a range of popular block and premium specialty cheeses and is prominent in the soy beverage market. Over the coming years, National Foods will make a best practice marketing investment and focus on higher potential core brands to drive revenue and mix.
Focus on optimization
Information technology has long been an essential ingredient in day-to-day business at National Foods. Recent years have seen an increase in IT use in almost every area of the company, in a trend which is still continuing. This is due in part to the acquisitions by the well-known Australian food company. National Foods is an established user of core applications such as SAP ERP ECC 6.0, Netweaver BI and SCM and has gradually increased the number of functions it uses in these solutions. At the same time, the IT infrastructure linked to these solutions has steadily expanded. In response, both the server capacities (HP Superdome) and storage systems had to be gradually enlarged. The data volume of the database management system used for the application environment, ECC 6.0 and Oracle Database (Release 10.2.04), was also growing rapidly – eventually peaking at over 7.6 TB. Meanwhile, more than 1,700 users are making intensive use of the application solutions.
“The application environment and the associated IT infrastructure involve enormous costs. This means we’re always looking to increase IT efficiency and use tools or techno- logies with an optimization effect,” says Glenn Cadman, one of the team responsible for SAP at National Foods. Around five months ago the expansion-focused business found just what it was looking for in the database feature Oracle Index Key Compression. “We benefit from Oracle Key Compression in numerous ways,” says Cadman.
Industry:
Food and beverage company producing household-name brands in milk and dairy beverages, juice, fresh dairy, cheese and soy
dd
Workforce:
4,000 in Australia, New Zealand, Malaysia, and Singapore
Oracle products:
Oracle Database 10.2.04, SAP ECC size 7.6 TB before Index Key Compression
Key benefits:
Significant database size reduction of 26.6 percent, index size reduction of 70 percent, fast online implemen- tation in 3 months, reduced backup volume, reduced number of backup tapes
SAP:
SAP ERP ECC 6.0, Netweaver BI 7.0, SCM 5.0 and others, over 1,700 named users
Infrastructure: HP Superdome (HP-UX), HP XP24000 Storage Systems O R A C L E I N D E X K E Y C O M P R E S S I O N F O R S A P A T N A T I O N A L F O O D S A U S T R A L I A : E X C E E D I N G E X P E C T A T I O N S
“The database optimization feature Oracle Index Key Compression exceeded our expectations. Total index size was reduced 2.8 TB to around 875 GB, which meant considerable disk space savings. The total database volume shrank by 26.6% percent.”
– G L E N N C A D M A N ,
Index Key Compression at National Foods Australia 61
Immediate interest
At a regular meeting with Oracle, the conver- sation turned to the success other customers have had with database optimization in asso- ciation with SAP, and it was this that prompted the idea of using Oracle Index Key Compres- sion. The potential for optimization offered by Index Key Compression met with imme- diate interest from National Foods. Oracle Index Key Compression can dramatically reduce index and disk space by shortening individual indexes within index blocks by up to 75%. The tool also offers other benefits from which business users stand to profit, including optimized I/O times, updates and backups, as well as a slimmer database. Cadman explains: “The potential for optimi- zation offered by Oracle Index Key Compres- sion was exactly what we were looking for and it fitted in perfectly with National Foods’ ongoing efforts to increase efficiency.” An archiving project that had been in the pipeline for some time had yet to deliver the urgently required space disk savings. The implementation and roll-out of Oracle Index Key Compression went without a hitch. Even though the company allowed itself plenty of time for the database optimization project with Oracle Index Key Compression, it took just three months from the meeting where the idea was first created until the tool went into productive use for the first time.
The first stage involved identifying the top 20 indexes of 10 GB or more in size. These indexes were then compressed with Oracle Index Key Compression on a test system to analyze the situation before and after compres- sion. “The difference was striking,” Cadman recalls. “The Oracle compression feature achieved reductions of 40% - 90% on these huge indexes, one massive index: VBOX~0 reduced from 1.35 TB to 400 MB. We were very impressed.”
After these tests, optimization was extended to more indexes and performance tests were run. The Australian food giant was then finally able to roll out Oracle Index Key Compression.
Significant savings Looking to the future
National Foods was delighted at the results achieved with Oracle Index Key Compression: “The Oracle database optimization feature exceeded our expectations. We were able to reduce the total index size from 2.8 TB to 875 GB, which meant considerable disk space savings. The database volume shrank by 26.6 percent.”
The company also achieved greater efficiency in another respect. By opting for Oracle Index Key Compression, it has reduced its backup volume at the same time in terms of both business copies and disaster recovery backups. At National Foods these are stored on tapes, and thanks to Oracle Key Compression the company now needs fewer tapes than before. In terms of compression, National Foods is already contemplating further optimization projects – in conjunction with an upgrade to Oracle Database 11g Release 2 for SAP planned for deployment in 2011.
Oracle Database 11g comes with Advanced Compression, a range of additional compres- sion features such as OLTP Compression, SecureFiles Compression, RMAN Compres- sion, Data Guard Network Compression and Data Pump Compression. This means that database compression can be used not only with Warehouse applications but also appli- cations with mixed workloads and OLTP applications. Advanced Compression also provides effective support for unstructured data in the shape of SecureFiles Compression, for example in typical content management or XML applications.
“The potential for optimization offered by Oracle Index Key Compression was exactly what we were looking for and it fitted in perfectly with National Foods’ ongoing efforts to increase efficiency.” – Glenn Cadman, SAP Technical Manager, National Food
SAP platform migration completed over one weekend
Carl Zeiss is one of the world’s leading optical and opto-electronic firms, with a workforce numbering more than 24,000. IT infrastructure is of great importance for such an innovative company with such a global reach. When the company decided to outsource to Siemens IT Solutions and Services, one of its main concerns was an optimum SAP migration process. Carl Zeiss set aside one weekend for the downtime of the key SAP platform for the markets (EMEA, USA and APAC). System stability and reliability also needed to be ensured after migration. Oracle addressed both these concerns with its latest “Triple-O” online migration technology.
The project
Carl Zeiss uses SAP ECC 6.0 with SAP Net- Weaver 7.0 and Oracle Database 10g Release 2 (10.2.04). The largest platform covered in this article is based on a 2.5 TB database. If the traditional approach of SAP LOAD had been used to migrate this hefty database, it would have taken around 40 hours to transfer the data alone. The subsequent interface adaptations and other follow-up work required would have made the original requirement of migrating over one weekend impossible.
This migration project included various challenges:
• Migration of a database of this size, including interface adaptions and corrections, over one weekend
• Large number of interfaces (more than 200) • Inclusion of EMEA, USA and APAC at the
same time
Implementation
The project was started in July and the actual cut over took place in mid-August.
In order to satisfy the requirements of Carl Zeiss, Siemens IT Solutions and Services there- fore used Oracle Triple-O for the migration. This is available for a wide range of system platforms (UNIX, Linux, Windows) which support SAP.
Triple-O consists of two components: • O2O
Migration from the source to the target database is started at a defined time. Once complete, the new database is fully synchro- nized with the old one – although only to the status at the start of migration. But since operations have continued during the migration, there is a delta which is usually very small in terms of the volume of data concerned compared with the actual size of the database.
• This final update for the new target data- base is undertaken online using the Triple-O component. To do this, Triple-O records all the changes which occur during O2O migration in the source database.
O R A C L E T O O R A C L E O N L I N E M I G R A T I O N A T C A R L Z E I S S
Oracle to Oracle Online migration (Triple-O) is a new technical way of carrying out large system migrations. This process enabled Carl Zeiss to migrate its global ERP system in just one weekend and without any note- worthy availability restrictions.
Oracle Online Migration at Carl Zeiss 63
Once the migration is completed with O2O and the IT operation has been closed for the migration – as planned – the database changes recorded are then updated in the target database. It is estimated that this will take around 30 minutes, freeing up a lot of time for interface adaptations, corrections, tests and the decision to go live. A SAP target system was produced. The source system was migrated into this. The corrections expected during a migration at basic SAP level and interface adaptations then had to be undertaken.
To ensure a successful migration, the actual process was tested twice with the assistance of Carl Zeiss experts; once as part of a test migration to the future target system and once to the new test management system. Everyone involved in the project was therefore fully prepared when the actual migration started as planned on Friday. The final posting date was 9 pm. The system was powered down. And it was soon made available again for testing.
Synchronization took 30 minutes. The financial and compliance checks and user acceptance tests required in the APAC, Americas and EMEA regions were then undertaken.
Just before midnight on Saturday, the team decided to go live.
Technological platform: Oracle Triple-O
The new “Oracle Triple-O” online migration technology is recommended when undertaking a whole host of recurring requirements in data centers:
• Migration of large Oracle database environments to new system platforms in short periods of time
• Reorganization of the database environment • Database upgrades
• RAC implementations
• Installation of new and more powerful system platforms
• Realization of new storage solutions Oracle Triple-O offers efficient functions for ensuring the transfer of data from source to target system and uses the Golden Gate component for data synchronization. The Oracle migration can be interrupted at any time. The actual production platform is not restricted in any way at any time.
Oracle Triple-O is SAP-certified.
For more information, please consult SAP Note 1508271 or go to www.oracle.com/sap.
Quote from Siemens
Oracle to Oracle Online migration (Triple-O) is an innovative further development of O2O which allowed us to move several hours of weekend work forward in the week for this project.
The administration and SAP operation was simplified considerably by using IBM GPFS (Global Parallel File System). For the resulting infrastructure at Bauerfeind, GPFS is the re- quired clustered file system for SAP environ- ments running on the AIX operating system to enable the Oracle 10.2.04 RAC nodes to access the same database tables simultaneously. GPFS also enables Bauerfeind to provision SAP systems on different Power servers or LPARs rapidly and flexibly. This landscape delivers excellent price-performance, as demonstrated by a VMS benchmark.
Customer Benefits around the clock
The continuous availability of business appli- cations around the clock is crucial for Bauer- feind. The window for planned downtime is extremely narrow, because the company has international subsidiaries in nine time zones, and users need access to the SAP systems 24 hours 7 days a week. This factor was a major influence on platform selection and architecture from the beginning of the project.
In total, 500-600 people (approximately 50 percent of the 1,100 licensed SAP users) are concurrent users of the SAP ERP system. Additionally, there are many specialized users of other SAP applications such as SAP CRM and SAP NetWeaver BW. Another important contribution to the total load on the infrastruc- ture is made by the approximately 2,000 simultaneous B2B users. By integrating profess- ional users (suppliers of medical equipment, pharmacies, and medical practices) online into the SAP eCommerce system, Bauerfeind can offer a rapid and efficient ordering process, with delivery within 24 hours.
Bauerfeind AG www.bauerfeind.com
Bauerfeind AG, a leading German manufacturer of medical aids, needs to manage data volumes of currently 2.8 TB for production systems such as SAP ERP and SAP CRM, and 2.6 TB for the SAP NetWeaver BW system. A further 0.5 TB is required for other systems that are integrated with the SAP environment. In 2002, the company began designing a modern, centralized; corporate-wide business management strategy based on SAP Business Suite, and initiated a five year project program to implement the solution. In the course of this project, it was necessary to replace legacy systems like Brain AS and MAS 90, and build a completely new network infrastructure as well as a new centralized storage solution. This solution had to be scalable to meet the needs of the company as it continued to grow. Very early in the project, Bauerfeind decided to run the databases for the SAP environment