WebCache: Large PLSQL Cachable Objects are Showing Size N/A, 0, or -1 in Popular Requests
(Doc ID 1550245.1)
Last updated on SEPTEMBER 25, 2018
Applies to:Web Cache - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
This is a work in progress note and published to inform customers of an issue seen.
While no solution may be available at this time development has been made aware of the issue and is working on a fix.
If you need an update on this issue please create an SR and if there is information available you will be made aware.
This note will be updated as information is released on this issue.
When caching mod_plsql requests in webcache it has been see that large payloads (810KB in this case) do not report the size accurately in Popular Requests.
The request is reporting as N/A in Fusion Middleware Control or WebCache Manager.
When exported to the log it shows 0 or -1 depending on whether or not the object is cached in webcache.
The environment this was reproduced in is as follows:
User --http--> WebCache --http--> OHS --mod_plsql--> Database
Where do I find Popular Requests? There are two ways.
1) Through Enterprise Manager Fusion Middleware Control (FMWC)
FMWC -> WebTier -> WebCache (right click) -> Monitoring -> Popular Request
You can then export the entries to a file using the export button. An example of this exported file is below.
2) If FMWC is not used Popular Requests can be accessed though WebCache Manager.
If you do not know what port WebCache Manager is running on check opmnctl status -l
webcache1 | WebCache-admin | xxxx | Alive | xx | xxxxx | 1:06:30 | http_admin:<port>
The user for login will be ias_admin and the password will have been set at configuration or can be set using FMWC.
Once you are in WebCache Manager, one left under Monitoring click Popular Requests.
Use the Export to File button to write the entries to a file.
Here are two examples of what the exported file looks like:
When 100KB is the object limit size in webcache and the object is not cached because it is too large.
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