Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning Siebel Remote > Tuning Siebel Remote Server Components > Tuning the Transaction Router ComponentThis topic is part of Tuning Siebel Remote Server Components. It describes how to resolve or avoid performance issues for the Transaction Router component. Performance issues for Transaction Router can arise from the following sources:
For more information about Transaction Router performance issues, consult the following documents:
Visibility-Related TransactionsIf you diagnose the root cause of the Transaction Router performance issue to be visibility-related transactions, then consider the following two possible solutions:
Docking Rules and Data DistributionIf you diagnose the root cause of the Transaction Router performance issue to be docking rule related transactions, then it is advisable to request assistance from Global Customer Support. Create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. When you log the SR, provide the following pieces of information:
Slow-Running QueriesIf you diagnose the root cause of the Transaction Router performance issue to be slow-running queries, then consult your database administrator to determine the following:
Increasing Transaction Router ThroughputThe following factors can impact throughput for the Transaction Router component:
In both instances, you need to decide if an increase in throughput for the Transaction Router component is more important than a decrease in throughput for the Siebel EIM and Siebel Assignment Manager components before you make changes. Setting the Id Db Size ParameterIncreasing the size of the visdata.dbf file has been shown to help performance in certain situations. This file is a cached file used by the Transaction Router and Transaction Processor components. The size of the visdata.dbf file is determined by the value of the parameter Id Db Size, which is available for both of these components. The value for this parameter must be the same in both components. If the value of the Id Db Size parameter is increased in one component, such as to 204800 (200 MB), then it must be changed in the other component. |
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |