saptools..SP_DBH_TABLES

[Former Member]

Hello everyone,

The last couple of day I've noticed that a process is filling up the saptools log in my production database. I've looked for ways to solve it but I haven't found anything yet. Backing up saptools+log didn't help either, setting the database to truncate on checkpoint was also useless.

Is there a way to kill this process? kill +psid didn't work. How can I stop this transaction from filling up my log?

Your help would be really appreciated.

Notes I've already looked up

2100175 - SYB: Increased space allocation of data collectors 'Tables' and 'Indexes'

1687320 - SYB: 'saptools' database running out of space (2)

1615695 - SYB: 'saptools' database running out of space

2077344 - SYB: Prevent DBA Cockpit from performing table scans

1839485 - SYB:Partition descriptor scavenges messages in ASE error log

[JanStallkamp]

Hi Ricardo.

To allow monitoring in the DBA Cockpit there are several data collectors scheduled that retreive data from MDA tables and system tables and store it in the saptools database. This data collection is done by stored procedures, usually named SP_DBH_<something>. To switch them off you can follow Seungyools Hong's advice but you need to be aware that you will lose much of the features of DBA Cockpit and SAP's Service and Support will have a hard time helping you in case of database issues. So I would not follow that route.

The nice thing about data collection in the saptools database is that the monitoring data is separated from your business data. This means: even if the saptools fills up completely your SAP system will continue running without issues.

So let's have a look what might cause your issues:
As Jeff said there might be a need to increase the size of both data and log of saptools. But according to your screenshot there is plenty of space available and 2GB of log seem quite a lot from my perspective. The data collector SP_DBH_TABLES is one of the most complex ones. This collector has two work modes, a small one that collects only some data and a full data mode that is only triggered at a lower frequency. And to reduce data space consumption only data of 'interesting' tables is stored for longer periods of time. That can cause quite long runtimes of the stored procedure. But in your case the runtime seems to be more than 10 hours, which is really a long time. So if the data collector does not finish at all you could try to unimplement it in DBA Cockpit and reimplement it afterwards.

Do not make manual changes to the stored procedures! The DBA Cockpit will report the data collector as inconsistent. And if automated updates are enabled your change will be overwritten on the next day anyway.

And please make sure you have the DBA Cockpit patch collection note for your release implemented in the most recent version. With that SAP Note you will get a lot of fixes and also performance improvements.

Regards,

Jan