Administrating database landscapes with the DBA Cockpit for SAP ASE
Today I would like to highlight a feature in the DBA Cockpit that many people are not aware of. At least I have noticed several times when talking about this feature that they did not know it is available. So let me talk about ‘Landscape Operations’. The idea is quite simple: usually you have a central system (e.g. your Solution Manager) that is connected to all database servers in your landscape and you can use the DBA Cockpit to monitor all that connected systems and analyze performance issues, change server configuration and do all the other tasks a DBA has to do. With landscape operations you can perform some kind of tasks on multiple database servers in parallel.
In the past the type of tasks available has been limited to a very small set but with the latest SAP_BASIS support packages the list of tasks has been extended a lot.
You will find the feature on the ‘System Landscape’ tab, not on the individual database tab. Currently the feature is only available for SAP Adaptive Server Enterprise (ASE), so it is named ‘Landscape Operations for SAP ASE’
When you open the screen you will get a list of all ASE servers connected to your DBA Cockpit and be able to directly see basic configuration parameters. E.g. you can directly see if the DBA Cockpit you are currently using is the ‘Owner’ of the remote system – meaning it is the one DBA Cockpit that defines how often performance data is collected and similar settings. In the most recent version you are also able to directly see if there are any issues with the data collector setup, if any resource limit violation happened in the last 48 hours or if the system utilization exceeded 90% for more than 15 minutes or if the SAP configuration check reported any issues.
However it is important to understand that the results shown on this screen are based on a background job that is run once a day. It is not intended to do high frequency system monitoring – that’s the job of SAP Solution Manager or SAP Focused Run.
In the above screen shot you can notice the column ‘Template’. And thisis the heart of the Landscape Operations feature: You can apply templates of settings to many systems. You just select multiple systems in the system list and chose ‘Apply Template’.
Here you select the template you want to apply and can also select that you want to take over the ownership of the remote system (meaning you are now able to specify data collection settings etc.). The number of parallel jobs is important when you want to apply a template to a large amount of systems and you cannot open connections to all of them in parallel.
With this feature you can easily apply monitoring settings to huge system landscapes, so if you have to deal with more than a handful of database servers give it a try. I have seen it working with huge numbers of systems – in fact it has been developed in close collaboration with my colleagues who run the business critical and ASE databases in the cloud here at SAP.