My Oracle Support Banner

Diagnosing Transaction Backlog and Growing Number of Records in the S_DOCK_TXN_LOG Table (Doc ID 477816.1)

Last updated on NOVEMBER 27, 2019

Applies to:

Siebel Remote - Version 7.5.3.15 SIA [16279] and later
Information in this document applies to any platform.

Purpose

This document provides the troubleshooting steps to diagnose transaction backlog and growing number of records in the S_DOCK_TXN_LOG table.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 Symptom or Error Message
 Cause
 Diagnostic Steps and Solutions
 1. Verify That the Transaction Processor and Transaction Router Tasks Are Running
 2. Confirm That Transaction Processor Is Processing Transactions
 3. Verify There Are No Obsolete Transaction Processors
 4. Confirm Mobile Web Client Folders, Responsibilities, and Positions
 5. Check for Orphaned Transactions
 6. Verify That All Inactive Mobile Users Have an End Date Set
 7. Check the Performance of Transaction Router
 8. Check for Recent Changes to Position Hierarchy, Territory Realignments, or Large EIM Loads
 9. Siebel Remote Administration Reports
 10. If Further Assistance Is Required, Log a Service Request to Oracle Technical Support
  
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.