Implementing Siebel Business Applications on DB2 UDB for z/OS > Understanding Siebel Partitioning > Partitioning Strategies for Special Types of Tables >

Siebel Remote Transaction Logging Tables

This topic explains the special considerations you must take into account when partitioning tables that support Siebel Remote.

Siebel Remote uses the S_DOCK_TXN_LOG table for transaction logging. All user changes on the Siebel Server are logged in this table. Changes are then routed to mobile users according to their responsibilities and user privileges.

To reduce the performance impact on the coupling facility in such a data sharing environment, avoid giving multiple members ReadWrite access to the same partition. You can do this by partitioning the table S_DOCK_TXN_LOG by the MEMBER_NAME column. The MEMBER_NAME column is populated by the CURRENT MEMBER special register, thereby ensuring that all write processes associated with the member affect only one partition.

Partitioning by MEMBER_NAME is not the default for the S_DOCK_TXN_LOG table, because such partitioning is only required for a data sharing environment. Therefore, the names of the data sharing members are not known by the Siebel application.

To specify MEMBER_NAME as the partitioning key, create a PartitionBase object for the table in the storage control file using the syntax in the following example.

[Object 8837]
Type = PartitionBase
Partitions = 10
Column 1 = MEMBER_NAME

Turning Off Transaction Logging

If you do not have mobile users or if you intend to use your mobile users for extract only, it is recommended that you turn off transaction logging to improve performance.

To turn off transaction logging using Siebel Tools

  1. Choose Screens > System Administration > System Preferences.
  2. In the System Preference column, select Docking:Transaction Logging.
  3. Change the value in the System Preference Value column to FALSE.
Implementing Siebel Business Applications on DB2 UDB for z/OS Copyright © 2008, Oracle. All rights reserved.