How to narrow down slow performance of workmon component
(Doc ID 513771.1)
Last updated on AUGUST 28, 2018
Applies to:Siebel Workflow - Version 22.214.171.124 SIA  to 126.96.36.199 [IP2014] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise), V8 (Enterprise)
Version: 188.8.131.52  Fin Svcs, 8.x
Database: IBM DB2/UDB 7.2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: IBM AIX 5L 5.1
Checked for Relevance on 11/30/2010
This document was previously published as Siebel SR 38-1099449277.
***Checked for relevance on 18-Jul-2012***
We have a workflow that is performing slowly in production. It is the only one being executed by its own Action Agent. In version 6 it could process 5000 transactions in an hour. Currently it is still processing 7200 transactions from last night. It has only processed 2000 records since 10:30 am Central time. It is now 5:30 pm Central time. We have recycled the Siebel Server, and have had the DBA look at the database to see if there were any deadlock or any obvious problems. We shutdown and restarted the Workflow Process Manager as well.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|