When running Discoverer Reports from the application server using the url for both Discoverer Viewer ( 18.104.22.168.0) and Discoverer Plus - some reports run okay but some larger reports fail with either the message
Query execution is unsuccessful.
- The server is running low on virtual memory. This can happen due to insufficient disk space or heap space on the server. Please contact your Discoverer manager for assistance.
Not all rows haven been retrieved. Data may be inaccurate. If you need to change the limit on the number of rows retrieved you can do so by clicking preferences
However, a person who has Discoverer Client installed on their PC can open and run the same queries without issue.
In Discoverer Viewer - for a user who sees the not all rows have been retrieved message ....select the Preferences option and uncheck any tick boxes to see if that resolves the issue.
When running Discoverer from a url and seeing the server is running low on Virtual Memory messsage, increase default settings in the pref.txt file to something appropriate for the server - the default options are usually 25, 1024000000,512000000. From Control Panel, Services stop Oracle Process Monitor.Then from the middle tier (weblogic) server, start and stop the Discoverer service, then restart Oracle Process Manager Service from Control Panel. Discoverer and Mapping were running on a separate server with this setup. However it only picked up the change of settings to the pref.txt file and reports when running applypreferences.bat in the ..\middleware\instance\fmds\util directory
Upped values to those below after checking how much memory was available.
CacheFlushPercentage = 50MaxVirtualDiskMem = 4096000000MaxVirtualHeapMem = 2048000000