Hi Abhinav,
As one of the issues has been raised as a bug which is resolved in BI 4.1 so you can upgrade to resolve this bug. Also if the CMS database size is large then CMS has to search for objects through huge number of rows hence that will affect overall performance. So you can try to reduce this size as per my previous upate.
Apart this you can try following steps
- Try to ping CMS DB server from BO servers and confirm the response is coming in 1 ms. Run tracert<DB servers name> from CMD and check the number of hops. If response time is not 1 ms or there are more number of hops then ask your network team to resolve network latency issue
- You can increase the "System database connections" for each CMS from server properties. It is set to 14 by default which means the CMS will establish 14 connections to CMS database at any time. You can increase this value, however please make sure that the system database allows more connections than default 14 from DB side. This needs to be confirmed from your DBA.
- Please add CMS cluster members in platformservices.properties file under Tomcat folder. Please refer following SAP KBA for steps to add the cluster members
http://service.sap.com/sap/support/notes/1668515
http://service.sap.com/sap/support/notes/1766935
4. Also please confirm number of users simultaneously login to system at peak time. Usually one CMS is capable of handling around 500 requests. So if you have more then 1000 users then add another new CMS on same nodes if there is enough free memory on the server
Regards,
Hrishikesh