Resolving DB2 Performance issues for All View Service Request and Activity Searches
(Doc ID 2437898.1)
Last updated on SEPTEMBER 14, 2020
Applies to:Siebel CRM - Version 16.10 [IP2016] and later
For some implementations, commonly used objects such as Activities, Service Requests and others contain records that are left in Open, Not Started, etc. status permanently. Queries for Open or New records will gradually produce larger answer sets as more records qualify for the criteria as a result of records not being set to Closed, Done, Cancelled or some other final status. This causes more impact for All View searches than for My View searches due to the greater number of records that qualify for All Views. That said, the conceptual issue is the same.
During the early years of the deployment, performance will deteriorate slowly and not be really noticeable to users. Over time, the percentage of these records increases and the distribution of them physically gets more diffuse so the system has to look further and work harder to find the first 48 or however many rows are requested. Performance becomes erratic and deterioration in response time becomes tangible.
For large tables, eventually, sequential detection and sequential prefetch start to fail. Performance suffers and service requests are opened to find relief for the business people. In extreme situations, this can lead to I/O delays that affect the entire enterprise.
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