Timeout When Searching Inside a Page And Its Subpages Slow Performance and High Consume of CPU Resources
(Doc ID 605037.1)
Last updated on JUNE 01, 2018
Applies to:Portal - Version 10.1.4.1 to 10.1.4.2 [Release 10gR2]
Information in this document applies to any platform.
Checked for relevance on 19-Sep-2013
|Symptom 1||Symptom 2||Symptom 3|
|When a search for a text string is performed specifying a page and checking 'include subpages', a timeout in the search portlet occurs.
When a search for that same text string is performed not specifying a page (thereby searching the entire page group), no timeout in the search portlet occurs, and the results are displayed correctly.
The problem occurs with both the custom and advanced search portlets.
The problem may also be seen when using a custom search portlet based on the API WWSRC_API.ITEM_SEARCH.
The following query is consuming high CPU resources frequently:
|After upgrading the Database Portal from 10.1.0.5 to 10.2.0.4, there are an ever increasing number of PORTAL_PUBLIC sessions experiencing high waits for cache buffers chains latches, cursor
spin on x, session allocation latch and direct path read waits. These waits are causing high cpu use on the host, keeping it at a constant 0% idle.
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