Logreader does not release memory even if queries are deleted.
(Doc ID 1450744.1)
Last updated on FEBRUARY 06, 2019
Applies to:
Siebel CRM - Version 8.1.1.5 [21229] and laterInformation in this document applies to any platform.
Symptoms
According to Siebel System Monitoring and Diagnostics Guide, "The LFA saves the results of each query to memory or saves it to a text file". Therefore the command "delete query-name" on the logreader should release the same amount of memory used by the particular query.
Even "delete query-name" is processed and the output is no longer accessible, memory used by the logreader is only slightly decreased (few hundreds of KB.) If a customer runs many queries in different query names, memory usage by the logreader continues to increase until it reaches memory limit.
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 |
Cause |
Solution |
References |