Best Practice     Banking Services – DatabasePerformance – Settings for DB2/OS390                                         ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Table of Contents1 Management Summary        ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS3901                  Management SummaryBanking ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS3902                  Best Practice2.1          ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Figure 1 Partitioning the table2.3           ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS3903                  Operations and Optimizatio...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Figure 2 Execution Steps for Partitioning3.2 ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Partitioning Index (1), partitioned (2)Table ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Table                           Index (1)    ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Table                                Index (1...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Due to the enhancements in DB2 V8.1, you can ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390SAP_AM_CARD01                                ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Archive info structure            Index of re...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390   - DFKKCOHARC   Change documents   - CDHDR ...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390765506                  DB2/zOS: Reducing num...
Best PracticeBanking Services – Database Performance – Settings for DB2/OS390© Copyright 2007 SAP AG. All Rights ReservedN...
Upcoming SlideShare
Loading in …5
×

Banking services – database performance settings for db2 or os390

950 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
950
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Banking services – database performance settings for db2 or os390

  1. 1. Best Practice Banking Services – DatabasePerformance – Settings for DB2/OS390 Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS customer published DATE VERSION Nov-03 2008 2.1 SOLUTION MANAGEMENT PHASE SAP SOLUTION Operations & Continuous Improvement SAP Banking, SAP Deposits Management TOPIC AREA SOLUTION MANAGER AREA System Management Configuration ManagementBest_Practice_Table_Partitioning_V21.doc – 03.11.2008
  2. 2. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Table of Contents1 Management Summary 3 1.1 Goal of Using This Service 3 1.2 Staff and Skills Requirements 3 1.3 System Requirements 32 Best Practice 4 2.1 Design 4 2.2 Partitioning of a Table 4 2.3 Data Partitioned Secondary Indexes 5 2.4 Clustering Index 53 Operations and Optimization 6 3.1 Execution of Partitioning 6 3.2 Partitioning Recommendations for a Banking Services Solution 7 3.3 Other Non-Standard Settings 12 3.4 Tables to Be Excluded from the Regular Automatic Update of the Optimizer Statistics 14 3.5 Performance-Related SAP Notes 14© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 2/16
  3. 3. Best PracticeBanking Services – Database Performance – Settings for DB2/OS3901 Management SummaryBanking Services is a mass data solution and a maximum throughput and high performance especially ontechnical level is crucial for a smooth operation of the system.The following document contains summarized recommendations for technical table settings (partitioning) ondatabase level for DB2/S390 for Banking Services to ensure a sufficient performance and scalable solution.At the end of the document, several performances-related SAP Notes are mentioned.1.1 Goal of Using This ServiceThe goal of the document is to support you in achieving an optimal performance of a Banking Services/TRBKsystem on DB2 z/OS.1.2 Staff and Skills RequirementsBefore implementing the described approach, it is necessary to ensure the following as regards the skill setand tasks of the project required team: To perform the settings, a technical expert with database DB2/S390 background is needed.1.3 System RequirementsSAP allows partitioning to be used in all releases. Explicit support within the inbuilt database administrativefunctions has been available from SAP Release 4.5.© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 3/16
  4. 4. Best PracticeBanking Services – Database Performance – Settings for DB2/OS3902 Best Practice2.1 DesignPartitioning can improve the manageability of the data, through more effective reorganization (REORG), datamanagement, and backup/recovery strategies, as well as (potentially) improving performance of programsusing this data. Especially for high volumes of data for particular tables, the use of partitioning functionality isrequired.Generally, partitioning should be considered as tables start to approach a certain size of 64 GB for the tablespace.For DB2 there is also a concept of Data Partitioned Secondary Indexes, where secondary indexes on tablescan also be partitioned in separate partitions, in this case corresponding to the set of rows in thecorresponding table space partition.SAP allows partitioning to be used in all releases. Explicit support within the inbuilt database administrativefunctions has been available from SAP Release 4.5. This support is provided by SAP transaction SE14.2.2 Partitioning of a TableWith DB2 partitioning, several physical data sets (partitions) are created to store the data of one table. Thedata is distributed to the partitions by specifying key ranges in a partitioning index that can contain multiplecolumns.The partitioning of a table should be done for the following reasons: Table size exceeds 64 GB Only partitioned tables can have a size greater than 64 GB Table is so large that administrative tasks take a long time DB2 utilities, such as REORG or COPY, can be performed on a single partition Avoidance of contention and improvement of performance In systems with a very high workload, partitioning the tables used for the asynchronous update process by the name of the application server eliminates contentions and improves performance.© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 4/16
  5. 5. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Figure 1 Partitioning the table2.3 Data Partitioned Secondary IndexesThere is the possibility to physically partition secondary indexes. The partitioning scheme is the same as thatof the table space. There are as many index partitions in the secondary index as table space partitions, andthe index keys in partition n of the index reference only the data in partition n of the table space. This indexis called a data partitioned secondary index (DPSI).2.4 Clustering IndexBad transaction response times can be caused by excessive I/O for specific statements.When a row is inserted in a table, DB2 tries to place it near the rows that have a similar key value for theindex known as the clustering index. Placing the rows like this greatly improves subsequent retrievals ofranges of rows that are accessed using the clustering index. The rows can be read with fewer I/O operations:It is likely that the pages read contain more rows that need to be retrieved. In addition to that, DB2 canmaximize effects of its sequential prefetch feature.© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 5/16
  6. 6. Best PracticeBanking Services – Database Performance – Settings for DB2/OS3903 Operations and Optimization3.1 Execution of PartitioningPartitioning is fully supported by the ABAP Dictionary utilities (transaction SE14). DB2 V8 table-controlledpartitioning is exploited by SAP.If a table needs to be partitioned or isolated, use DB2 utilities to move the data in case the table has morethan a million entries or is larger than 100 MB. In such a case, a standard or an incremental conversion wouldtake too much time. Both procedures use SQL SELECT-INSERT to perform the data transfer. Therefore, youwill need to perform the following steps: Determine the number of rows with transaction SE16. Make sure that afterwards no write accesses to the subsystem are carried out apart from the actions described here. In transaction SE14, choose Edit Storage parameters to modify the tables storage parameters. Do not initiate a table conversion. Save the new storage parameters (choose Attributes Save). Copy the table contents to a sequential data set using DB2 utilities, for example, DSNTIAUL or REORG with option UNLOAD EXTERNAL. Recreate the table: Activate and adjust database with the Delete data option in transaction SE14. The SAP system uses the saved storage parameters when creating database, table space, table and indexes. Reload saved table contents into the newly created table (option: LOG NO). As a first backup, carry out a full image copy of the table space. This also cancels the Copy Pending. Execute RUNSTATS on the table and check the number of entries using transaction SE16.Note: You can also execute table partitioning with the program RBCA_PARTITION_TABLES. Settings forthe partitioning have to be performed in development class BCA_FINSERV_Y. In this case, you have toadjust the following tables: BCA_PART_TAB_DET: Set the number of partitions, member cluster and the compression. BCA_PART_TAB_FLD: Fill this table with the fields, for which the partitioning should be performed. BCA_PART_TAB_IND© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 6/16
  7. 7. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Figure 2 Execution Steps for Partitioning3.2 Partitioning Recommendations for a Banking Services SolutionFor large installations, SAP recommends that you partition several tables. This document proposes aprocedure that supports a Banking Services system with data sharing for many batch runs. All tables must bepartitioned in such a way that the first field in the index after the client (field CLIENT, MANDT) is used as apartitioning criterion. For most tables, this is the internal contract ID (usually the field CONTRACT_INT). It canbe assumed that the values are distributed randomly across the entire value set available.With database version 8.1 and higher, all tables are automatically partitioned with table controlled partitioningif you use partitioning. This means that the data can be partitioned independently of the index definition. Youcan then alternatively create indexes as global indexes or partitioned indexes.Below is a list of indexes that should be partitioned in a different manner.1. The tables should be partitioned according to the first two fields (partitioning index).2. The list also contains other indexes that should be partitioned in this way, but you should define the partitioning index as a clustered index (Cluster = Yes).With DB2 V7, partitioning was possible only according to a partitioning index. This means that data and thepartitioning index were partitioned in parallel. All other indexes are global. To define other indexes aspartitioned, you must convert the table in advance according to SAP Note 792649.© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 7/16
  8. 8. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Partitioning Index (1), partitioned (2)Table Index (1) Index (2) PurposePayment itemsBCA_PAYMITEM S02 Payment itemsBCA_PAYMITEM S01BCA_PAYMITEM 0BCA_PAYMITEM S04BCA_PAYMITEM_NT 0 Payment items, Payment notesBCA_GL_PAYMITEM 0 General Ledger: Information about payment itemsBCA_GL_PAYMITEM FKY 1BCA_SB_2BR 0 Savings book update 1BCA_SB_2BR_CHNG 0 Changes to savings book updateAdditional DataBCA_PRENOTE 0 PrenotesBCA_PRENOTE 001 1BCA_NOW_ABS 0 Available balance series of notice on amount 2BCA_TRANSFIG 0 Value date transaction figuresBCA_COUNTER 0 Counters (for example, item counter)BCA_ACCTBAL 0 Account balancePayment orderBCA_PO_HD ACC Payment order headerBCA_PO_IT 0BCA_PO_NT 0Standing orderBKKSOHD 0 Header information1 Only when you use the saving function2 Up to and including DM 4.0, this was the table BKK9B© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 8/16
  9. 9. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Table Index (1) Index (2) PurposeBKKSOIT 0 Recipient item of a standing orderBKKSOIT_VAR_AMNT 0 Standing order: Variable amountsBKKSOITNT 0 Payment notes of recipient itemsBKKSO_PAORN 0 Payment orders of a standing orderGeneral ledger (only if you use this function)BCA_GL_BSPR_PROT 0 Log table balance sheet preparationBCA_GL_BPITEM 0 Transfer postings balance sheet preparation headerBCA_SNITEM 0 Non-balance-changing transactions basic dataBCA_GL_SNITEM 0 Non-balance-changing transactionsBCA_GL_BALCN 0 Balances in FI per accountBCA_GL_TRNTP 0 Account balances per G/L transactionContract master dataBCA_CONTRACT 0 ContractBCA_CN_LINK S01 Contract elements of the contractBCA_CN_EVENT 001 Contract: EventsBCA_CNSP_ACCT 0 Contract: Account specializationBCA_BCT_CN_OBJV 0 BW extraction: contract dataSpecialization cards (only if you use the card function)BCA_CARD_HEADER 0 Card specializationBCA_CARD_ADMIN 001 Administrative data for cardsBCA_CARD_EQUIP 001 Attributes for features of a cardBCA_CARD_TRANS 211 Transaction data for a cardBCA_CARD_LOCK 001 Lock data of a cardBCA_CARD_PRC_CHG 001 Log change of a cardBCA_CARD_CAPTURE 001 Return dataBCA_CARD_CHG 001 Master data changes© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 9/16
  10. 10. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Table Index (1) Index (2) Purpose 3BCA_CARD_CHG_HIS 001 Master data changes for historyBCA_CARD_INFO 001 Information fieldsBCA_CARD_SHIPM 001 Dispatch dataAccount settlement data 3BCA92 0 Settlement dataBKK92_SIM 0 Settlement data - alternative settlementsBKK92_SUMS 0 Settlement data totalsBKK92_SUMS_SIM 0 Settlement data totals - alternative settlementsBKK92_POSTINGS 0 Account settlement data settlement postings 4BCA96 0 Settlement detail dataBKK96_SIM 0 Settlement detail data - alternative settlements 5BCA92_RESTART 0 Settlement restart informationBCA_CN_PER_ACBAL 0 Settlement due datesBCA_CN_EV_ACBAL 1 Settlement datesBank statementBCA_BCAS_DUE 0 Bank statement due datesBCA_BCAS_EVBST 001 Event-controlled bank statementBalance confirmation (only if you use this function)BCA_BANO_DUE 0 Balance confirmation due datesBCA_BANO_EVT 001 Balance confirmation eventsFinancial conditions 6FICOT_CONDI I01 Individual conditions3 Up to and including DM 4.0, this was the table BKK924 Up to and including DM 4.0, this was the table BKK965 As of FSBP 1.0 only6 If you do not use the individual conditions often, you can define the I01 index as a clustering index instead of the partitioning the entiretable.© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 10/16
  11. 11. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Due to the enhancements in DB2 V8.1, you can also partition tables without a partitioning index. Thefollowing list contains the fields for partitioning and any partitioned indexes. For successful partitioningaccording to the fields ADDKEY/FIKEYC, you must activate the totals record optimization (SAP Note494171). As the SELECTS for the tables listed here are not usually included with the partitioning criterion, asmall number of partitions should be selected. As an indication, we recommend four times the number ofmembers. Partitioning PartitionedTable Field IndexBCA_INV_DETAILS (CLIENT,CONTRACT_INT) 100BKKC01B (MANDT,FIKEYC)BCA_RCN_SUMS_IN (MANDT,ADDKEY) A01BCA_RCN_SUMS_OUT (MANDT,ADDKEY) A01BCA_INV_TOTALS (CLIENT, ADDKEY)BANK_MR_LINE_COUNT (CLIENT, ADDKEY)Archive information structuresThe archive information structures are stored in generated tables, which are all called ZARIXIS*. You can findthe repository of all archive information structures in transaction SARI Customizing. To find theassignments of the generated tables to the archive information structures, display an individual informationstructure in the technical data. If you use the F4 input help in transaction SE11 for a ZARIXIS* table, thesystem displays a list containing the information structure tables, and the appropriate archiving object isdisplayed in the short text. The ZARIX tables should be partitioned for the following information structures:Info structure/Field catalog Archiving ObjectBCA_COUNTER COUNTERBCA_DISPORDER DISPORDERBCA_FIGURES FIGURESBCA_PAYMITEM PAYMITEMBCA_PAYMORDER PAYMORDERBCA_PRENOTE PRENOTEBCA_SETTLEMENT SETTLEMENTBCA_STANDORDER STANDORDER© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 11/16
  12. 12. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390SAP_AM_CARD01 AM_CARD 7BCA_INDCOND INDCONDThe tables for all information structures (except for BCA_PAYMITEM) must be partitioned according to theprimary index. Create an additional index (001) with fields MANDT/CONTRACT_INT/DATE_POST forBCA_PAYMITEM according to which this table must be partitioned.Shadow tables for archive information structuresIn release 3.0, there are tables to improve the check whether data has been archived, in addition to thearchive information structures. For these tables, only one entry or few entries per account are expected.SAP recommends partitioning according to the following procedure. IndexBCA_AR_COUNT_CP 0 Max. posting period for arch. counterBCA_AR_FIGRS_CP 0 Max. posting period for arch. transaction figuresBCA_AR_PAYM_MD 0 Max. posting date for arch. payment itemsBCA_AR_SETTL_MTS 0 Max. end-time stamp for arch. settlements3.3 Other Non-Standard SettingsDescending Indices (only required for indexes that were generated under DB2 V7):Table IndexBCA92 0BKK92_SIM 0BCA_GL_BALCN 0BCA_PAYMITEM S01, S02For the following ZARIXIS tables (archive information structures)Archive info structure Index of relevant ZARIXIS tableBCA_COUNTER 0BCA_FIGURES 07 Only if individual conditions are used to a large extent (many entries in FICOT_CONDI)© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 12/16
  13. 13. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390Archive info structure Index of relevant ZARIXIS tableBCA_SETTLEMENT 0BCA_PAYMITEM 001Make sure that the partitions are also defined in descending order of the contract_int intervals.Tables with "Member Cluster": Payment items - BCA_PAYMITEM - BCA_PAYMITEM_ENQ - BCA_PAYMITEM_NT - BCA_SB_2BR - BCA_SB_2BR_CHNG Additional data - BCA_NOW_ABS - BCA_PRENOTE General ledger - BCA_GL_PAYMITEM - BCA_GL_BSPR_PROT - BCA_GL_BPITEM - BCA_SNITEM - BCA_GL_SNITEM - BCA_GL_BALCN Payment order - BCA_PO_HD - BCA_PO_IT - BCA_PO_NT Standing order 8 - BCASO_PAORN General ledger transfer - BCA_GL_BSPR_PROT Account settlement data - BKK92_SUMS - BKK92_SUMS_SIM - BKK92_POSTINGS - BKK96 - BKK96_SIM Spool - TST03 Correspondence tool - DFKKCODCLUST - DFKKCOH - DFKKCOHI8 Up to and including DM 4.0, this was the table BKKSO_PAORN© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 13/16
  14. 14. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390 - DFKKCOHARC Change documents - CDHDR - CDCLS (must be carried out as specified in SAP Note 96515) Application log - BALDATFor the following tables, the clustering index should be defined in a different way to the primary index. Followthe instructions in SAP Note 438727.Table Recommended clustering indexBCA_PAYREF S02 Payment details BCA_DEH_DOC_HEADACC PLM document header3.4 Tables to Be Excluded from the Regular Automatic Update of the Optimizer StatisticsBCA_PAYMITEM_ENQThis option is recommended for tables that temporarily become very large during live operation and whosecontents become very small again afterwards. For a table of this type, the statistics should be generated at atime when the table contains many entries and then never changed again. SAP Note 507824 contains notesabout how to implement this option in DB2.3.5 Performance-Related SAP Notes766012 DB2/390 V7: Real Time Statistics und DSNACCOR765983 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765897 DB2/390 V7: Real Time Statistics and DSNACCOR765790 DB2/390 V7: Real Time Statistics and DSNACCOR765781 DB2/390 V7: Real Time Statistics and DSNACCOR765619 DB2/390 V7: Real Time Statistics and DSNACCOR765617 DB2/390 V7: Real Time Statistics and DSNACCOR765552 DB2/390 V7: Real Time Statistics and DSNACCOR765551 DB2/390 V7: Real Time Statistics and DSNACCOR765509 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765508 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765507 DB2/zOS: Reducing number of DSNACCOR REORG recommendations© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 14/16
  15. 15. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390765506 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765505 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765504 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765503 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765502 DB2/zOS: Reducing number of DSNACCOR REORG recommendations765500 DB2/390 V7: Real Time Statistics and DSNACCOR720733 FICO: Performance improvements - index on FICOT_CONDI507824 DB2/390 V7: Real Time Statistics and DSNACCOR494171 Performance notes FS-AM438727 DB2/390: Changing Clustering Index© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 15/16
  16. 16. Best PracticeBanking Services – Database Performance – Settings for DB2/OS390© Copyright 2007 SAP AG. All Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered tradem arks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of CitrixSystems, Inc.HTML, XML, XHTML and W3C are tradem arks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Allother product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any formor for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreem ent with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP toany particular course of business, product strategy, and/or development. Please note that this document is subject to change and maybe changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringem ent.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you mayaccess through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.© 2008 SAP AG - Best_Practice_Table_Partitioning_V21.doc page 16/16

×