There is a 404 error when opening the report while other pages of eSight can work properly.
First, we checked the server memory – over 94%;
Then we checked the report files number under the directory /opt/eSight/AppBase/Unibi_Server/unibi_solutions/system/molap/store/AppBase/APORTLINK and ../IF. We found the number of load* file under this two directories is abnormally large number, about '' 2900 and 3300 directory " respectively, compared with the normal value – about 30. Actually, the directory is storing all report data, and eSight will get the data to display in the form of customized report. Under normal scenario, the data will be aggregated automatically by itself, so number of the files won’t be such large.
So we concluded something wrong happened during the process of report running, which causing the data cannot be aggregated by itself. Therefore, the mem is consumed quickly.
It is a known bug in V3R9SPC202 version and solved in SPC203 .
First, we did evaluation on how large amount of historical data would be lost then upgraded to SPC203 patch and manually aggregate the redundant load data. The report recovered.