Enabling Oracle Applications on DB2 an Early User Experience
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Enabling Oracle Applications on DB2 an Early User Experience

on

  • 719 views

 

Statistics

Views

Total Views
719
Views on SlideShare
719
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Until DB2 9.7, there was a large divide between Oracle and the rest of the Relational World. Syntax was one obstacle, and Concurrency approach was another. Now there’s DB2 9.7. This presentation discusses Anixter’s early user experiences, including: Datatypes Syntax Concurrency Data Migration DB2 pureXML DB2 9.7 beta
  • The major points of the presentation will be given in the context of Anixter’s business, technology stack, and 3 major applications. Two in particular will be discussed in depth: the Warehouse Management System (WMX), and the Product Content Management System (PCM). The Value Added Tax (VAT) system will be discussed to make the point about what DB2 9.7 means for Independent Software Vendors (ISVs) – possibly maintaining one codebase and set of test scripts for Oracle and DB2 platforms. The convergence of features between different platforms for DB2 may also mean it’s possible for IBM customers to have one codebase that’s portable between DB2 for Linux, UNIX, Windows and DB2 for z/OS. Finally – the DB2 9.7 (Cobra) beta – what a great experience!
  • Here’s some business information about Anixter to set the stage for our business needs and our technology decisions.
  • The competitive landscape for any company helps determine its technology choices. One way to learn about a company and its competitive environment is to look at sites like Yahoo and Hoover’s. Hoover’s is a D&B company. This is a free portion of the site, which also has a paid subscription with additional information. You can see something about Anixter as a company, its business, international competition and its Competitive Landscape. For those of you working to align your technology initiatives to your business needs, this is a good place to gather the facts and concepts needed to gain the insights to develop useful opinions.
  • Zooming in on the competitive landscape, you can see that efficiency is a major driver. Margins are close, and this is a highly automated industry. Note that average revenue per work is close to $775,000. In cases where automation and efficiency are both requirements for success, paying careful attention to expenses can help define a winning strategy. Avoiding multiple enterprise technology stacks, along with redundant hardware, software and staff, can be a major tactical advantage.
  • To drive home the point about the importance of managing expenses
  • Anixter is accomplished at WebSphere, MQ Series, DB2. We’re trying to focus our Enterprise Applications on that Software stack. Does that mean we won’t have a heterogeneous environment? No, we expect to support a variety of App Servers and Data Servers for departmental applications. Some of those are from other vendors, and some of those applications are based in Lotus Notes. What we want to do is stay focused on DB2, MQ and Websphere for Enterprise Applications, which require a high degree of skill to achieve Scalability, Availability and Recovery—we are focused on the IBM technology stack. That’s because personnel are the biggest portion of our IS budget. Avoiding redundant staffs on competing technologies avoids redundant costs.
  • These three application migration experiences provide a vehicle for discussing the major technical points outlined in the 5 Key Points and the agenda.
  • Anixter decided to build a Warehouse Management System. It seemed useful to contract with an experienced vendor to build a system that Anixter could use, but the vendor could also sell to other customers. This would diffuse the cost of building the solution by providing multiple customers for a product that would otherwise be built to spec. Unfortunately for all on this project, the interests of the two companies diverged to the point where the code that was delivered was built in JBoss / Oracle instead of WebSphere / DB2. We were confident that we could port the JBoss App Server to WebSphere. However, we wondered what our options were for the application calls to the Oracle database. It will become evident in the following slides that the DB2 9.7 (Cobra) beta gave us a chance to explore a port of native Oracle syntax to DB2.
  • This is a very significant application, as evidenced in the complexity of the solution and the lines of code delivered.
  • The migration from Oracle to DB2 was successful! In particular, the Concurrency model was one we knew could be a challenge. Read Currently Committed worked!
  • A few of the datatype conversions were related to the immaturity of the tools, and may be improved now. However, even if they are not, it’s easy to identify the minor problems and fix them in the scripts.
  • Some expected problems were non-problems.
  • Just because we got the port to work didn’t mean we were home free. Unfortunately, the application design was flawed and needed extensive rework. That work is proceeding.
  • This departmental application had an enterprise role. However, it was stuck on a back-level version of the Oracle DBMS and a back-level version of the Windows Operating System. Could DB2 9.7 create an opportunity to improve the application performance while making it easier to support? Overcoming the XML hurdle would be necessary to make this happen.
  • The database migration and the data migration went well. The problem was with the XML. The syntax and approach has evolved over the last 10 years. That’s true for both Oracle and for DB2. In addition, our programming skill were not up to speed on this point. The XML needed a POC, and we needed training to be successful.
  • IBM has created an utility named MEET DB2 which can be used to analyze all the objects in your Oracle database and produce an HTML report that summarizes the compatibility of those objects with DB2. You can view the Technical Summary at a high level or click on “Show Details” to drill down to a more detailed level. During the one year beta phase of DB2 9.7, many applications totaling over 750,000 lines of PL/SQL code have been analyzed in detail with an average out-of-the-box transfer rate of 90%-99%.
  • At the time Anixter was starting the PCM enablement to DB2, MEET DB2 was not available to the public. Users interested in having their database analyzed had to contact their IBM account representative or sales contact to run this utility. The tool has since gone public and is available at the link above. Users simply point the tool to the .sql file they want to analyze and click the Start button. The tool does the rest!
  • You can view the Technical Summary at a high level or click on “Click here to show the detailed technical report” to drill down to a more detailed level.
  • Click on “Show Details” to receive a more technical description.
  • You can selectively enable specific compatibility features by setting specific bits or enable all the compatibility features by setting the variable value to ORA.
  • Please see the following URL for this and additional information. http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.apdv.porting.doc/doc/r0052867.html
  • This setting is important in order to take advantage of DB2’s new implicit data type casting feature and avoids errors that might otherwise occur during the PREPARE step when untyped parameter markers are present.
  • The rounding mode used for assignments and casts that happen on the database server depends on the data types that are involved. In some cases, truncation is used. In cases where the target is a binary floating-point (REAL or DOUBLE) value, round-half-even is used, as usual. In other cases (usually involving a DECIMAL or DECFLOAT value), the rounding is based on the value of the DECFLT_ROUNDING database configuration parameter. This parameter defaults to round-half-even, but can be set to round-half-up to match the Oracle rounding mode. The DECFLT_ROUNDING database configuration parameter is not changed dynamically but will become effective only after all applications disconnect from the database. http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.apdv.porting.doc/doc/r0052867.html If you create a new database, by default the AUTO_REVAL configuration parameter is set to DEFERRED. It means that all dependent objects are revalidated the next time that they are accessed. If you set this parameter to DEFERRED_FORCE, it behaves the same as when it was set the DEFERRED and an additional CREATE with error feature is enabled. For example, a procedure will be successfully created even though it relies on a table that does not exist yet. This configuration parameter is dynamic , meaning that a change in its value takes place immediately. http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.apdv.porting.doc/doc/r0052867.html
  • To verify your current Java version, run the java –version command. By default, JAVA is installed as part of DB2 for Windows in SQLLIBjavajdk
  • Enter the following Source Database Information Server Name Port Number Database Name User ID (with appropriate privileges) Password Location of JDBC drivers Test the Connection
  • Split multiple action Triggers – DB2 does not support multiple actions in a single trigger. The tool allows you to split multiple action triggers into separate triggers. Oracle allows “REFERENCING OLD AS OLD” even with a before insert trigger, but DB2 does not. IBM recommends selecting the following options at a minimum: Trim trailing blanks during unload Split multiple action Triggers Extract Partitions Use Generated Constraint Names Use Best Practice Tablespace Definitions You can choose to extract just DDL,DDL and Data, or just generate the data movement scripts. If you choose DDL and Data, the data is unloaded into text files and stored in the folder named data found in the working directory.
  • Various .sql, .db2. and .cmd files are created and stored in the Working Directory. These files wil be used during the deployment step. Examples: db2tables.sql – Creates Tables db2check.sql – Creates check constraints db2cons.sql – Creates primary keys and indexes db2ddl.cmd – Used to call various .sql files (like the three above) db2trigger.db2 – Creates triggers during interactive deployment
  • Click on “Connect to DB2” to establish connection to DB2. Compatibility Settings are displayed for your verification.
  • Since I have chosen to deploy both DDL and Data, db2gen.cmd is executed. The tool will always display the file it is about to execute and ask you to confirm. I found this feature very useful because I like to know what commands are about to be executed.
  • In the example above, as part of the deployment the tool was going to create new tablespaces and bufferpools which I did not need. I modified the db2gen.cmd script to not include those specific commands.
  • You can also view the output in the GUI by clicking on the View File tab.
  • If deployment failed, you can right click in the results pane and choose “Get Detailed error message” to view the entire error message. You can also right click and choose “Get Source” to view the source DDL.
  • Select an object or group of objects and right click and choose “Deploy selected objects in DB2”.
  • Bottom right pane will display deployment results
  • If deployment failed, you can right click in the results pane and choose “Get Detailed error message” to view the entire error message. You can also right click and choose “Get Source” to view the source DDL.
  • The db2gen_OUTPUT.txt file contains the DDL used to create each object. It also specifies whether or not the DDL execution was successful.
  • The db2gen_OUTPUT.txt file contains the load output for each table.
  • The db2gen_OUTPUT.txt file contains the row count for each table.
  • The db2gen_OUTPUT.txt also displays the status of each table after the load.
  • Report showing the success rate of the migration. For those objects that failed to migrate, it was frequently one minor fix. There are a few more challenging things, like Functions in Views, but those were well within the reach of a journeyman DBA or Developer.
  • Anixter has had a very successful Proof of Concept for the port, dramatically decreasing the code for a portion of the application, and improving performance dramatically. The port involved 5 people in reviewing the code, and selecting representative and challenging portions of the application. Based upon this success, we have begun training staff on DB2 pureXML, which is new to Anixter. As of March 1, 2010, we have just completed a training program on DB2 pureXML, and expect to begin coding in earnest by mid-April. Our plan is to employ a senior consultant to take the recently trained programmers and build their experience while completing the port of the PCM application. One example of a performance gain will be eliminating the shredding of the XML. It will no longer be stored in a CLOB that needs to be parsed. It is now a data type that you store natively as a whole and query using SQLXML or XQuery (or XPath, a subset of XQuery).
  • Our application makes extensive use of XML documents. To understand how much we could improve our CPU utilization and I/O throughput in the database, we constructed a test that retrieved 10 documents distributed among 106,015 documents. To simulate the difference between a CLOB and XML Index access, we performed the SLQXML statement using the XMLTABLE function: first without an Index, and second with an Index. Keep in mind that much of this overhead would have been borne by multiple tiers: the App Server and Messaging Server, along with the Database Server.
  • The problem statement: It takes extra time to port to multiple platforms, and some platforms lag others.
  • This new capability opens up a new world for IBM Customers to run Oracle applications on IBM software. This means Independent Software Vendors have that same option. This decreases the cost of porting code, opening up the IBM customer marketplace for the ISV.
  • The beta program experience was very rewarding. Anixter was able to help IBM identify and fix bugs. IBM was able to respond to requests for functionality and enablement tooling. One prime example of the enablement tooling was the data migration tool. The network of professionals that helped Anixter succeed is worthy of note. They come from the following communities: IBM IDUG IBM Gold Consultant IBM Information Champions
  • The DB2 Emerging Technology team consists of a few highly trained professionals that work with customers in beta and early adoption programs.
  • Question and Answer period….
  • Bernie O’Connor is Director of Information Technology at Anixter Inc., a global distributor of Enterprise Cabling, Security Systems, Wire and Cable, Fasteners, and Supply Chain Services. Bernie is responsible for Technical Architecture, and for Data Services, which includes management of databases and database gateways. The Midwest Database Users group (MWDUG) introduced Bernie to DB2 in 1989. Bernie presented regularly for years, and served on the MWDUG Board from 1998 to 2004. The International DB2 Users Group (IDUG) has been a major focus of Bernie’s volunteer activity since 1995. Bernie is an IDUG Hall of Fame speaker, and has been active as an author, Conference Planning Committee member, Conference Chair, Board Member and also as IDUG President. Bernie is an IBM Information Champion. ----------------------------------------------------------------------------------------- Jason Spencer is a DBA, also at Anixter Inc. Jason has extensive business experience at Anixter in Warehouse Operations, and has worked at Anixter as a programmer and database administrator. Jason is a winner of Anixter’s prestigious Award of Excellence.

Enabling Oracle Applications on DB2 an Early User Experience Presentation Transcript

  • 1. Enabling Oracle Applications on DB2 an Early User Experience Bernie O’Connor Anixter Inc. [email_address] Jason Spencer Anixter Inc. [email_address] Session Code: C03 Tuesday, May 11, 3:00 PM Platform: DB2 for Linux, UNIX, Windows
  • 2. 5 Key Points
    • Datatype differences in migration to DB2 from Oracle
    • Syntax
      • Most of the migration worked without intervention.
    • Concurrency
      • No problems with the major differences between approaches.
    • Moving Data between Oracle and DB2
      • Major improvements from the early beta to now.
    • Participation in the DB2 9.7 (Cobra) beta
      • a great experience!
  • 3. Agenda
    • Anixter’s Competitive Landscape
    • DB2 9.7 Business Driver: to hold down costs
    • Warehouse Management System
      • real parts, not a data warehouse
    • Product Content Management System
      • Data, Syntax, and DB2 pureXML
    • Value Added Tax
      • Unified Code Base and Testing Scripts?
    • Other advantages: one codebase for LUW and z/OS?
    • The DB2 9.7 beta
  • 4. Anixter’s Business See www.anixter.com (NYSE: AXE)
    • Anixter is a leading global supplier of communications and security products, electrical and electronic wire and cable , fasteners and other small components.
    • We help our customers specify solutions and make informed purchasing decisions around technology, applications and relevant standards.
    • Throughout the world, we provide innovative supply chain management services to reduce our customers' total cost of production and implementation.
    • Fiscal Year ended January 1, 2010, Anixter reported sales: $5 billion
    • To more than 100,000 customers in 52 countries, Anixter is more than a distributor: we are a business partner.
  • 5.  
  • 6. Competitive Landscape: Efficiency, Service, Automation
  • 7. Competitive Landscape: IT as a Percentage of Revenue source: InformationWeek
  • 8. Why DB2 9.7? Business Driver to hold down costs
    • Key business driver: hold down personnel costs
      • by maintaining skilled professionals for one enterprise software stack, instead of two or more.
      • we already have specialists in WebSphere, MQ Series and DB2
    • Difference between departmental and enterprise applications.
      • We can be “good enough” to support heterogeneous departmental applications
      • Enterprise Applications require Scalability, High Availability, Recovery
    • Personnel, even more than hardware and software, is a critical cost to be considered.
  • 9. Three Application Migration Experiences
    • Warehouse Management
    • Product Content Management
    • Value Added Tax
  • 10. Warehouse Management Nature of the Opportunity to Migrate
    • Warehouse Management System
      • Contracted to be done in WebSphere / DB2
      • Delivered in JBoss / Oracle
      • We still wanted WebSphere / DB2
    • Why the mismatch between spec and delivery?
      • Vendor skill-sets
        • Originally intended to hire FTEs or Contractors
        • Vendor was acquired and reacquired
        • Vendor team lost FTEs and budget for contractors
        • Remaining team had a JBoss / Oracle skill-set
  • 11. Warehouse Management Application Profile
    • Application Profile
      • RF Gun is the primary UI
      • Message-based solution internally
    • Lines of code
      • Java: 2501 files with 171,285 lines of code
      • JSP: 387 files with 19,101 lines of code
      • XML: 400 files with 153,897 lines
      • XSD:   63 XSD files with 4,898 lines
      • JS (Javascript): 60 files with 21,350 lines
      • Tables: 223
      • Views: 194, many nested
  • 12. Warehouse Management Ease of Migration to DB2 9.7
    • It migrated successfully!
    • We ran the exact same tests as with JBoss / Oracle
    • With WebSphere / DB2 9.7:
      • Read Currently Committed worked
        • Concurrency Control was a very big deal!
        • Writers didn’t block readers for the application
        • Serge is the right person to tell you about the how this works
        • ...I can tell you this means we now can run more than 1 person
      • Equivalent Performance
        • Some normal tuning using indexes
  • 13. Warehouse Management Some Extra Effort: Datatypes, Unique Constraints with Nullable Columns
    • Datatypes
      • Current Issues
        • Float(126) had to be changed to Float(51)
        • Number(38,0) had to be changed to Number(31,0)
        • Columns with the LONG data type caused syntax errors. This data type is now deprecated in both Oracle and DB2.
      • Issues encountered during beta program that were fixed
        • Raw(nnn)
        • /* .. */ comments caused syntax errors.
        • TO_CHAR(NULL)
    • Unique Constraints with Nullable Columns
      • Unique constraints containing nullable columns caused syntax errors.
        • Our workaround was to remove the constraint and create a unique index instead.
  • 14. Warehouse Management Some Non-Problems
    • “ Non-problem” differences upon review:
      • Timestamp Manipulation: Microseconds
      • Varchar2: No problem for our application
  • 15. Warehouse Management “Refactor-writing” for Application Challenges
    • Did we all live happily ever after? Well...
    • DB2 can’t fix Application Design Challenges
    • Design problems impact performance in any software:
      • Workflow and History mixed with Transactional Data:
        • We need to separate these
      • Four touches for each message is being revised:
        • Synchronous calls internally
        • Asynchronous calls externally
      • Inconsistent approaches:
        • Need to be implemented consistently
    • In brief, Application Design is still critical to success
      • We are “refactor-writing” as we speak
  • 16. Product Content Management Nature of the Opportunity to Migrate
    • Product Content Management (PCM)
      • Originally designed for Catalog Publishing
      • Now also a System of Record
        • Integration with Legacy Systems via MQ Series
      • An Unusual Topology
        • Microsoft Access Client
        • Oracle Database
    • The Problem Statement:
      • Proprietary XML Publishing impedes upgrades
        • OS upgrade is stuck behind the DBMS upgrade
        • DBMS upgrade is successful except for XML
  • 17. Product Content Management Basic Application Port OK – XML is the wrinkle
    • Anixter’s Product Content Management (PCM)
      • The basic application migrates fairly easily
      • XML conversion is currently WIP
        • If we’re converting the application for XML
          • We can convert to a DBMS we can more easily support
  • 18. Product Content Management Three key steps to enablement
    • Sizing up the enablement to DB2.
      • How much re-factoring will be necessary?
    • Laying the migration foundation.
      • What steps are needed to successfully migrate the objects/data from Oracle to DB2?
    • Migrating the objects/data.
      • What tools are available to help us migrate?
  • 19. Product Content Management DB2 9.7 – Sizing up the enablement to DB2
  • 20. Product Content Management DB2 9.7 – Sizing up the enablement to DB2
    • MEET DB2 Tool is now Public!
      • Download site https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=swg-meetdb2&S_TACT=meetdb2&lang=en_US
  • 21. Product Content Management DB2 9.7 – Sizing up the enablement to DB2
  • 22. Product Content Management DB2 9.7 – Sizing up the enablement to DB2
  • 23. Product Content Management DB2 9.7 – Sizing up the enablement to DB2
  • 24. Product Content Management DB2 9.7 – Sizing up the enablement to DB2
  • 25. Product Content Management DB2 9.7 – Laying the Migration Foundation
    • DB2_COMPATIBILITY_VECTOR
      • Used to enable one or more DB2 compatibility features introduced since DB2 9.5.
      • To enable all the supported compatibility features, set the registry variable to the value ORA. This is the recommended setting.
  • 26. Product Content Management DB2 9.7 – Laying the Migration Foundation
    • Compatibility Features Example
  • 27. Product Content Management DB2 9.7 – Laying the Migration Foundation
    • DB2_DEFERRED_PREPARE_SEMANTICS
      • When set to YES, dynamic SQL statements will not be evaluated at the PREPARE step, but rather on OPEN or EXECUTE calls.
      • Changes to the registry variables will not take effect until after the instance is stopped and then restarted.
  • 28. Product Content Management DB2 9.7 – Laying the Migration Foundation
    • Create Database
    • DECFLT_ROUNDING
      • It is also recommended to adjust the rounding behavior to match that of Oracle.
    • AUTO_REVAL
      • Changing this value to deferred_force will allow you to deploy objects out of dependency order.
  • 29. Product Content Management DB2 9.7 – Laying the Migration Foundation
    • Additional Information
      • Redbook – Oracle to DB2 Conversion Guide: Compatibility Made Easy (Chapter 2. Language Compatibility Features)
      • http://publib-b.boulder.ibm.com/abstracts/sg247736.html?Open
  • 30. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • IBM Data Movement Tool
      • Prerequisites
        • DB2 V9.7 should be installed on your target server if you are enabling an Oracle application to be run on DB2 LUW.
        • Java version 1.5 or higher must be installed on your target server.
        • Location of JDBC drivers for your source database and DB2.
  • 31. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Launching IBM Data Movement Tool
  • 32. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Choose Options for DDL Extract
  • 33. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Monitor progress of extract through console window or look through the IBMDataMovementTool.log located in the output directory.
  • 34. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Working Directory
  • 35. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Deploying Objects and Data
  • 36. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Three Different Deploy Options
      • Deploy DDL/DATA
      • Interactive Deploy
      • Deploy using command line script db2gen.cmd
  • 37. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Deploy DDL/DATA
  • 38. Product Content Management DB2 9.7 – Migrating the Objects and Data
  • 39. Product Content Management DB2 9.7 – Migrating the Objects and Data
  • 40. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Interactive Deploy
  • 41. Product Content Management DB2 9.7 – Migrating the Objects and Data
  • 42. Product Content Management DB2 9.7 – Migrating the Objects and Data
  • 43. Product Content Management DB2 9.7 – Migrating the Objects and Data
  • 44. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Deploy using command line script db2gen.cmd
  • 45. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • View db2gen_OUTPUT.txt
      • Verify Object Creation
  • 46. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • View db2gen_OUTPUT.txt
      • Verify Data Load
  • 47. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • View db2gen_OUTPUT.txt
      • Row Count
  • 48. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • View db2gen_OUTPUT.txt
      • Table Status
  • 49. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • PCM Migration Results
      • 93.3% of Objects Migrated Successfully!
  • 50. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • XML Conversion – Work In Progress
      • The XML piece of the current Oracle solution has over 33,000 lines of code.
      • Using DB2 v9.7, Anixter plans on eliminating all the DOM processing and replacing it with shorter SQL/XML statements (ex. XMLTABLE, XMLGROUP..etc).
      • We also plan on trying to convert as much of the XSLT transformation code as possible.
      • Completing both objectives mentioned above should help us achieve a maximum performance gain and maximum reduction in memory consumption.
    Shredding of an XML document is no longer needed with the use of the native XML data type!
  • 51. Product Content Management DB2 9.7 – XML Conversion Return 10 rows. Data randomly distributed among 106,015 XML Documents. 99.99% 99.55% 98.67% Percentage Improvement 11 0.0624 0.221175 After: XML Index Access 106,016 13.930889 16.60056 Before: No XML Index (Simulated CLOB) I/O (Rows Read) CPU (User + System) Elapsed (Local Client)
  • 52. Product Content Management DB2 9.7 – Migrating the Objects and Data
    • Enablement Tools
      • IBM Data Movement Tool
      • http://www.ibm.com/developerworks/data/library/techarticle/dm-0906datamovement/
      • IBM Optim Development Studio
      • http://publib.boulder.ibm.com/infocenter/idm/v2r2/index.jsp?topic=/com.ibm.datatools.dwb.nav.doc/topics/cprodover_dwb.html
      • Additional DB29.7 Information
      • http://www.ibm.com/developerworks/views/data/libraryview.jsp?search_by=db2%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%209.7%20content
  • 53. Value Added Tax Nature of the Opportunity to Migrate
    • Value Added Tax Application
      • Provides correct Tax calculations
      • Maintains tax districts
      • Manages Certificates
        • such as Tax Exempt status
    • There is a DB2 version of VAT...
      • ...but the Vendor performs more rigorous testing on the primary development platform
  • 54. Value Added Tax Works well – 9.7 can simplify development, test
    • Value Added Tax already works
    • ...but the Opportunity for the ISV is:
      • One code base
      • One set of test scripts
      • More rapid delivery of new releases
  • 55. DB2 9.7 Beta Program was a great experience! Thanks to IBM, IDUG, Gold Consultants
    • Beta program experience was very good!
    • Thanks to IBM, the DB2 Community, and Consultants:
      • IBM
        • Maria Schwenger (IBM – DB2 enablement advocate)
        • Eric Christy (IBM – Enterprise Data Management Sales)
      • IDUG
        • Chris Eaton (IBM – Toronto Lab – DB2 Technical Evangelist)
        • Martin Hubel (Gold Consultant and Information Champion)
          • Martin Hubel Consulting
      • IBM DB2 Gold Consultants and Information Champions
        • Dave Beulke (Gold Consultant and Information Champion)
          • Pragmatic Solutions (PSI)
        • Ingo Muller (former Gold Consultant)
  • 56. Interested in participating in an IBM beta program?
    • To check out beta availability, send an email to: [email_address]
    • Special thanks to the IBM DB2 Emerging Technology team!
      • Twitter Account
        • Username: DB2EmergingTech
        • Profile: http://twitter.com/DB2EmergingTech
  • 57. Questions?
    • ?
  • 58. Bernie O’Connor Anixter Inc. [email_address] Jason Spencer Anixter Inc. [email_address] Thank You! Session Code: C03