eG Help

The CMS uses the CMS system database to store SAP BusinessObjects Business Intelligence platform information, such as user, server, folder, document, configuration, and authentication details. It is sometimes referred to as the system repository.

The CMS is configured with the maximum number of connections it can establish with the CMS system database. For optimal performance, the CMS must establish all these connections. However, if all the established connections are used up, subsequent requests to the CMS that require access to the CMS system database will not be processed. The repercussions of this can range from a user being denied access to the SAP BOBI platform to a critical server configuration change not being updated in the database. Such failures can adversely impact SAP BOBI platform services. This is why, it would be good practice for administrators to run the Central Management Server System DB test at frequent intervals.

This test keeps track of the CMS system database connections established by the CMS and how these connections are utilized. In the process, the test promptly alerts administrators if almost all the established connections have been used up. This way, the test helps administrators understand which database parameters need to be tuned to ensure continuous database availability for servicing requests.

Measurement	Description	Measurement Unit	Interpretation
dbConnections	Indicates the number of connections the CMS was able to establish with the system database.	Number	The CMS tries to establish all of the requested system database connections as mentioned in its server properties. Default value for this is 14. If the number of established connections is lesser than the configured connections, the CMS may not be performing optimally. If the value of this measure is 0, it could mean that the CMS system database is unavailable - probably owing to a hardware or software failure or a network proble. In this case, the CMS goes into the “Waiting for resources” state. If the SAP BusinessObjects Business Intelligence platform deployment has multiple CMSs, then subsequent requests from other servers are forwarded to any CMSs in the cluster that have an active connection to the system database. While a CMS is in the “Waiting for resources” state, any current requests that do not require database access continue to be processed, but requests that require access to the CMS database will fail.
usedDBConnectionsPCT	Indicates the number of established system database connections that the CMS is currently using.	Number	If all the system database connections are typically in use, this suggests a bottleneck. In this case, the allowed number of connections can be increased in the server property to improve CMS performance.
pendingRequests	Indicates the number of requests for the CMS system database that are waiting for an available connection.	Number	Consistently high values for this measure suggest that the configured number of connections for the CMS is insufficient and should be increased to improve CMS performance. CMS system database tuning also improves CMS performance.
noOfObjectsInCMSCache	Indicates the current number of objects in the CMS system database cache.	Number	The default value for maximum objects in cache is 100000. While a large number of objects in cache can improve database performance, it can also cause excessive consumption of space in cache. If the cache is not sized right, then this can degrade database performance in the long run.
noOFObjectsInCMSDb	Indicates the current number of objects in the CMS system database.	Number	CMS DB size corresponds to the number of objects such as users or documents. 100 MB of disk space typically stores 30000 objects.