Replication Guide and Reference

Rules for index types

Because TYPE 2 indexes do not lock index pages, you can avoid deadlock and timeout problems in your applications if you specify TYPE 2 indexes. TYPE 2 indexes also enable you to use other functions, such as parallel query central processor (CP) processing, improved partition independence, row locking, and the ability to read through locks. If you specify TYPE 2 indexes, all specifications of SUBPAGES are ignored, and an error message is issued.

If you do not specify an index type, the index type is determined as follows:

• If the LOCKSIZE is ROW, the default index type is TYPE 2, regardless of the type specified on the installation panel DSNTIPE.

• If the LOCKSIZE is not ROW, the default index type is the type specified in the field DEFAULT INDEX TYPE on the installation panel DSNTIPE. The default value for that field is TYPE 2.

Recommendations:

• Specify TYPE 2 as the index type for all table indexes. For best performance, bind the Capture program and the Apply packages using isolation UR. When you specify isolation UR, all indexes on the control tables are required to be created as TYPE 2 indexes. If source views are being used in replication subscriptions, and the Apply package is bound using isolation UR, only TYPE 2 indexes over the source tables involved in the source view can be used by the Apply program.

• For DB2 for OS/390 source servers, specify TYPE 2 on every generated CREATE INDEX statement and every CREATE INDEX statement in the DB2 Control Center file DPCNTL.MVS. (DRJA creates TYPE2 indexes automatically.)

[ DB2 List of Books | Search the DB2 Books ]