Hi all,
We are experiencing what’s becoming a critical issue for us in our company.
We have started experiencing performance issues in our Business Objects since two weeks. Last week we could still work with, and users run some reports, even if it took ages to open any webi; after webi was open, it run without problems. But since the last days it’s almost impossible to do anything, as BO hangs quite often.
We are working with our Basis team and they have restarted the BO server several times. As soon as they do it, BO works fine… during 5 - 10 minutes. After that, we have the same problem, and performance is so slow that it’s impossible to do anything and to work with.
We have webi reports, and Crystal Reports, and none are the issue as we have done several tests and verifications. We can also confirm that problem doesn’t come from interfaces, RFCs, or any kind of connection to other system, and there is no critical report that may cause this incident, specially because there are no users now running any reports.
First, what is your env ? repository type ? Oracle ? SQL Server ? other
your server ? Windows, Linux ? what is your RAM amount ? How many concurrent users do you have on your Platform during day and users configured ? do you have a lot of schedules / publication all along the day ? have you put traces (or maybe you have traces activated which can overload you server) I am also quite impresive regarding the 21 GB of disk space you free.
when you setup your BO env (quite recently I assume as the 4.1 SP is not too old), did you performed a sizing study ? with sap guys ? alone ?
Hi Bernard,
Thank you, probably it’s not the last time I write in this forum (so many BO issues … lol).
Here some useful information:
1- Operating System. (on the BO server)
–> Windows Server 2008 R2
2- Exact version of BusinessObjects (along with any SP or FP)
–> BO 4.1 SP3 Patch 7
3- Deployment (Clustered / Standalone)
–> Deployment: Standalone
4- CMS database (Oracle / MS SQL server…)
–> Deployment: Standalone
5- Web Application Server (Tomcat / WebLogic…)
–> Tomcat
6- Is the issue reproducible on the BO server machine itself? (http://localhost:8080/BOE/BI)
–> Yes, it’s reproducible on the BO Server
7- When the issue occurs, is it the same when accessing the Web Application Server home page (tomcat home page for example http://servername:8080)
–> No, the issue doesn’t occur
8- Is the issue related to the load on the system? (does it depend on the number of sessions created / number of users connected…)
–> No, it doesn’t depend on the number of sessions nor users connected.
9- Please indicate the CPU / RAM consumption when the issue occurs.
–> CPU: 25-30% RAM: 12Gb (Total 32Gb)
Regards
Have you looked at task manager to see if there are some processes that may be causing it? In our 3.1 SP7 environment we have a problem with Tomcat occasionally hogging 95% of CPU causing BO to come to a halt. I restart Tomcat, delete the Tomcat cache folder and it returns to normal.
First of all, thank you very much for your questions and suggestions. We were hard working till yesterday evening with an external consultant, and SAP was checking it as well as it was a Very High issue for us.
We could solve it, and today it’s working as usual. We applied the following 4 improvements:
1.Disabling logs:
-Go to CMC,navigate to the servers and then webi processing server.
-Right click and go to properties.
-Set log level as “None”
-Do the same for all webi processing server.
-Same step you have to follow for rest of the servers.
-For only CMS keep log level as “Unspecified”.
2.Delete logs:
-Go to Installing Directory of BusinessObjetcs\SAP BusinessObjects\SAPBusinessObjects Enterprise XI 4.0\logging directory.
-Delete all unwanted logs(.glf files).
3.Clear Cache:
-Go to Installing Directory of BusinessObjetcs\SAP BusinessObjects\SAPBusinessObjects Enterprise XI 4.0\Data directory.
-Take back up of all the content inside it and delete everything.
4.Clear Tomcat cache:
-Stop Tomcat.
-Go to Installing Directory of BusinessObjetcs\SAPBusinessObjects\Tomcat\work\Catalina\localhost.
-Take back up of all the content inside it and delete everything.
-Start Tomcat.
First thing was deleting logs, as I mentioned in my original post, we deleted 21Gb!! Then we applied the other 3 options, and we cannot ensure which one of those definitely solved the issue, but now it’s ok.
If your WebI and/or CMS logging settings were set to High, then that could have been causing your slowness. We have all of ours set to Low (so that any errors are captured), and it seems to be working well. We did have a problem when we first deployed BI4, in which very large reports were running slow. We found that one of our WebI processing servers have been left on “High”; setting it to Low resolved the issue for us.
Deleting the contents of the logging folder would only have helped if you were really low on disk space.
Deleting Tomcat’s work directory probably did not contribute to the improvement. It doesn’t hurt, but Tomcat will completely re-create it upon the next startup.
So, I think changing the logging settings is very likely what got you back in business.
We had a similar issue in BI 4.1 SP5. The issue for us was that the sessions were not stopping after the user closed the browser without logging off. We found that there were, at times, 10x’s the number of open sessions there normally were. The fix we found was to install SP6. Since the update, we have not had any issues. Hope that helps.
(BOB member since 2003-05-26)
(BOB member since 2002-08-29)
(BOB member since 2008-08-01)