1. Performance Tuning Guide
  2. Tuning the Transaction Router Component

Tuning the Transaction Router Component

This topic is part of Tuning Siebel Remote Server Components. It describes how to resolve or avoid performance issues for the Transaction Router component (alias TxnRoute).

For more information about component groups that you must enable to use Siebel Remote, see About Siebel Remote.

Performance issues for Transaction Router can arise from the following sources:

  • Visibility-related transactions

  • Docking rules and data distribution

  • Slow-running queries

  • Increasing Transaction Router throughput

  • Setting the Id Db Size parameter

For more information about Transaction Router performance issues, consult the following documents:

  • 476759.1 (Article ID) on My Oracle Support. This document, previously published as Siebel Troubleshooting Steps 8, describes how to diagnose and resolve Transaction Router performance issues.

  • 477816.1 (Article ID) on My Oracle Support. This document, previously published as Siebel Troubleshooting Steps 38, describes how to monitor and manage the transaction backlog for a Siebel Remote implementation.