Large Number of Invalid Queries on S_RR_TABLE With SearchSpec Based on Business Component Name Cause Small Performance Impact
(Doc ID 2860566.1)
Last updated on MAY 19, 2022
Applies to:
Siebel CRM - Version 21.8 and laterInformation in this document applies to any platform.
Symptoms
Invalid queries on S_RR_TABLE are observed in log files of any object manager.
They do not cause errors, but are seen as a waste of resources that can cause slightly slower application response times.
The queries have an invalid searchspec where the table name is being compared against business component names.
Some examples follows:
The S_RR_TABLE table is expected to contain the runtime compiled definition of the repository tables.
The column "NAME" is expected to contain table names and not business component names.
There are no specific steps to replicate.
The queries are generated while users navigate the application.
No errors are observed but performance monitoring tools suggest a slight decrease in response time.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |