250 likes | 404 Views
Migration of a Baggage Operation System from Oracle8 i OPS to Oracle9 i RAC on HP OpenVMS Systems. Fraport AG. Owner and operator of Frankfurt Airport Figures for year 2000: ~50 million passengers ~460,000 aircraft movements ~1.6 million tons airfreight Customer of HP for many years.
E N D
Migration of a Baggage Operation System from Oracle8i OPS to Oracle9i RAC on HP OpenVMS Systems
Fraport AG • Owner and operator of Frankfurt Airport • Figures for year 2000: • ~50 million passengers • ~460,000 aircraft movements • ~1.6 million tons airfreight • Customer of HP for many years Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
BODB application tasks • Application: Baggage Operation System (BODB) • Tasks: • Management and control: • Package and flights dispatch • Management of suspicious and not picked up luggage • Research system • Allocation of luggage conveyors • Passing of information to other system Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
BODB software environment • OpenVMS • Oracle • MQ-Series • MetaObject • Java RTE • Visual Basic-, Java-, and C-applications Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Airline-Host 1 Airline-Host 2 Airline-Host n BOIT ... BOAP-Workstation ......... SITA BOAP-Workstation BODB BOAP BOAP XY Interface Gateway SITA- Interface Fraport-LAN ......... ......... ......... ......... Fraport-LAN Data BOAP TB Interface BRS Interface BOAP OB Interface INFO/FIDS Interface BOAP TR Interface Overview Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
BODB application facts (1 of 2) • Data from external sources are passed as messages to MQ-Series, which writes them into local queues • Background processes process queued messages • Messages contain informationfor package, containers, flights, conveyors... • Control Processes • Control all application, background, MQ-Series and Oracle processes Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
BODB application facts (2 of 2) • Agents • ~ Online users • Interfaces • Central airport information system • Baggage control system • Baggage reconciliation system • Luggage conveyors Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Old production system • OpenVMS Cluster redundant hardware • Two AlphaServer 1200 machines, each with two 533 MHz CPUs • HSZ70 RAID controller • OpenVMS 7.2 • Oracle Database • Oracle8i (8.1.7) • OPS • Active-Active Configuration • All database files reside on shared cluster file system Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Reasons for migration • HW limit reached • Further throughput increase not possible • Single machine cannot handle complete system load in case of failover • Unstable Oracle8i OPS installation • Instance crashes • Problems with inter-instance locking Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Selection criteria for new system • Availability • Cluster • No SPOF • Performance • Single machine must be able to handle complete system load • Transition time< 3 minutes • Scalability • CPU, main memory andstorage • Simple Migration Path • If possible no changes to application code • Fallback • Investment protection Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
New production system • Because of the excellent experience with OpenVMS in terms of availability, performance, and ease of use,Fraport selected: • Two AlphaServer ES45 machines: • Each withone 1GHzCPU • All HW componentsare redundant configured • SAN storage • OpenVMS 7.3 • Oracle Database: • Oracle9i Release 1 • Real Application Cluster RAC Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Migration path • HW + OSinstallation new system • Oracle9iinstallation, configuration, and database setup • Layered product installation • Application porting • Functional tests • Performance tests • Migration of database • Production start Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Migration • HW & SW Installation • Done at HP partner site COS Concat • Adjustments for system environment of Fraport • Oracle 9i Database • Installation and setup • Database creation • Adjustments of Oracle9i and OpenVMS parameters • New Oracle functionality • Oracle and HP • Standard Software • Installation • Setup • Fraport • Application • Installation of development and run-time environment • Functional tests of all software components • Fraport Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Performance tests — remarks • Not possible to do a direct comparison between Oracle8i OPS and Oracle9i RAC • Due to the different HW it is • Goal was to get exact performance information of new HW/SW combination Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Peformance of “old” system • Measurement of CPU saturation for day x • Preparation for performance: • Backup of database for day x • Recording of all messages, type, and number of SQL queries Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Performance of “new” system • Database restore before each test • Writing of collected messages by a background process into queues • Rerun all SQL queries by batch jobs • Measurement of CPU saturation Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Results • Fraport expectations werebased on SPECint comparison • Ratio old to new: 1 to 1.67 • Actual CPU saturation of old system • 51% relative to two CPU • CPU saturation on new system • 20% of one CPU • This is an actual ratio of 2.5 • New machine is 50% faster than expected • Reasons: • System load on new system was a bit less than on old one • Faster I/O sub-system • New Oracle software • New Oracle functionality is used Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Implementation • Just transfer of data was necessary • Export/import • Time needed • Six hours for exp/imp (15 GB); total of 8 hours • Done during normal maintenance window Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Fallback / Productions Fallback • Old system was available • Just transfer of new data Productions • August `02 • Almost no problems Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Production CPU saturation on both machines was 35% • Main reason was that the materialized views for online users were disabled: • Near real time display of system information for online users • Enabling MVies reduced CPU load by about 15% Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Oracle9i RAC configuration and application failover Active-Active Configuration • RO and RW transaction on both instances • Distribution of MQ-Series processes by tasks onto both machines Failover Clients • Visual Basic/OLE-DB applications are using TAF Failover=select, type=basic • MQ-Series Server: automatic by MQ-Series • MQ-Series Client: programmed reconnect within application Failover Server • By cluster functionalityof MQ-Series • Starts interface processes on remaining node • Failover of virtual IP-address for clients • Does fallback Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Problems • Oracle9i RAC installation • Intelligent Agent could not run on both machines • Automatic PMON registration of listener for second network did not work as expected • Problems on Clients • ORA-600 errors on JDBC clients • Resolved by newest JDBC driver • Problems on Server • Startup of second instance does not always work at first attempt • Orphaned Oracle server processes after connection disconnect • Other • No support of WORKAREA_SIZE_POLICY-AUTO for OpenVMS Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Experience • SW Migration • No problems at all • No changes to source code necessary • Just new compile and link run for client and server application • Performance • Very good response times • Processing of message queues is much faster • Oracle • Parting was simple • Stability • Up to now no crash or any other major problem • Oracle9i RAC works without problems • Acceptance of Online Users • Very high • Due to good response times and stability Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems
Conclusions • Successfulmigration without any major problem • Performance goals were met • Careful planning and tests are important • Consultingby HP Consulting & Integration was key success factor • First Oracle9i RAC production siteon OpenVMS in Europe • Fraport is now a reference customer for both Oracle and HP due to the very good experience • HP has the most Oracle9i RAC installations world-wide and therefore possess over excellent experience and knowledge Migration of a Baggage Operation System from Oracle8i OPS to Oracle9iRAC on HP OpenVMS Systems