Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Understanding Siebel Partitioning > Strategies for Special Types of Tables >
Siebel Remote Transaction Logging Table
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.
TIP: 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
- Choose Screens > System Administration > System Preferences.
- In the System Preference column, select Docking:Transaction Logging.
- Change the value in the System Preference Value column to
FALSE
.Performance Considerations for Data Sharing Environment
To reduce the performance impact on the coupling facility in a data sharing environment, partition table S_DOCK_TXN_LOG by MEMBER_NAME.
To avoid giving multiple members ReadWrite access to the same partition, create a column called MEMBER_NAME that is populated by the CURRENT MEMBER special register, thereby verifying that all write processes associated with the member affect only one partition.
Partitioning by MEMBER_NAME is not a default, because partitioning is only required for a data sharing environment. Therefore, the names of the data sharing members are not known by the Siebel application. Create the new partitioning index using the syntax in the following example.
[Object 7368]
Type = IndexBase
Name = S_DOCK_TXN_LOG_PART
Table = S_DOCK_TXN_LOG
SpecialCol = MEMBER_NAME WCHAR(8)
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS Published: 18 April 2003 |